LEGAL

Ask Vinny Sub-Processors List

Last updated: September 2026

LEGAL

Ask Vinny Sub-Processors List

Last updated: September 2026

What is a Sub-processor?

When Ask Vinny engages third party service providers in our capacity as a data processor for our customers’ personal data, the General Data Protection Regulation (“GDPR”) and a number of other global privacy frameworks call these third-party service providers sub-processors. Sub-processors are service providers who have, or potentially will have, access to or process personal data that Ask Vinny processes for, and on behalf of, our customers.


This page outlines the types of service providers, sub-processors and affiliates we use, where they are located, and a description of the work they carry out. The list below covers our core platform sub-processors.

Due Diligence

Before engaging any service provider (including sub-processors), we perform due diligence, including a vendor security assessment. Our service providers are subject to contract terms designed to ensure that they process personal data only for the purposes of providing services to Ask Vinny, and in accordance with our commitments to customers and applicable data protection laws.

AI Inference Routing

AI inference is routed via OpenRouter in-region EU routing (eu.openrouter.ai) with zero data retention and data collection denied. Underlying model providers (OpenAI, Anthropic, Google and others) are only invoked via EU-eligible models, so they are not listed separately for inference.

Name

Data

Purpose of Processing

Entity Country

Data

Tenant and prospect personal data, messages, documents, work orders, property/tenancy records, integration credentials, application logs, and file uploads.

Purpose of Processing

Cloud hosting and storage: PostgreSQL database (RDS), object storage (S3), secrets management, background job infrastructure, and SFTP file transfer.

Entity Country

United States (production data hosted in EU — Frankfurt, eu-central-1)

Data

Name, email address, authentication tokens, and login metadata.

Purpose of Processing

User authentication and SSO.

Entity Country

United States

Data

Client-side session events, error traces, performance metrics, and anonymised usage data.

Purpose of Processing

Application monitoring, real-user monitoring (RUM), and log aggregation.

Entity Country

European Union (EU cluster)

Data

Voice call audio, transcripts, phone numbers, and conversational metadata.

Purpose of Processing

Voice AI agents and telephony-based concierge interactions.

Entity Country

European Union (European Data Residency)

Name

Data

Property addresses and map coordinates.

Purpose of Processing

Geocoding and map display only (not used for LLM inference, which is routed via OpenRouter).

Entity Country

United States

Data

Job event payloads containing tenant/prospect data, sync records, messaging events, and workflow metadata.

Purpose of Processing

Background job orchestration, scheduled crons, and async workflow execution.

Entity Country

European Union (self-hosted)

Data

AI prompts, responses, traces, evaluation inputs/outputs, and conversation metadata.

Purpose of Processing

AI observability, tracing, and quality evaluation.

Entity Country

Netherlands

Data

Organisation and user context keys used for feature flag targeting.

Purpose of Processing

Feature flag management and gradual rollouts.

Entity Country

United States

Data

WhatsApp Business account setup data, business verification details, and channel onboarding metadata.

Purpose of Processing

WhatsApp Business embedded signup and Graph API channel provisioning.

Entity Country

United States

Data

Conversation text, tenant/property context, prompts, model responses, and tool-call payloads.

Purpose of Processing

Unified LLM inference gateway. Routes requests to EU-eligible models only (e.g. OpenAI, Anthropic and Google models via OpenRouter). Zero data retention and data collection denial enforced at account/request level.

Legal entity: OpenRouter, Inc. (United States). Prompts and completions are processed entirely within the EU under Business/Enterprise in-region routing. Workspace guardrail allowed_data_regions: europe rejects non-EU requests.

Entity Country

European Union (in-region routing via eu.openrouter.ai)

Data

Document text chunks, vector embeddings, and associated metadata.

Purpose of Processing

Semantic search and retrieval for the knowledge base and document Q&A.

Entity Country

Ireland

Name

Data

Support ticket content, customer contact details, and communication history.

Purpose of Processing

Customer support portal and ticket management.

Entity Country

United Kingdom

Name

Data

Organisation/user channel events and realtime notification payloads.

Purpose of Processing

Realtime websocket updates in the web application.

Entity Country

United Kingdom (EU cluster)

Name

Data

Identity verification documents and results; payment card/billing details for self-serve signup.

Purpose of Processing

Identity verification (AML/KYC) and subscription billing.

Entity Country

United States

Data

Phone numbers, WhatsApp message content, template metadata, and channel configuration data.

Purpose of Processing

WhatsApp Business API messaging (primary WhatsApp channel).

Entity Country

Germany

Data

Phone numbers, SMS/WhatsApp/voice message content, email addresses, email body, call metadata, and delivery status.

Purpose of Processing

SMS and voice messaging, WhatsApp (legacy path), transactional email (SendGrid), and delivery webhooks.

Entity Country

European Union (Irish/EU cluster)

Name

Data

Application request/response data, session tokens, API payloads, and uploaded files in transit/at rest on the hosting platform.

Purpose of Processing

Application hosting, serverless compute, and content delivery for the Vinny web application.

Entity Country

European Union