Aveexia · legal information
Subprocessors
Last updated: November 8, 2026 · v2026-11-08
Subprocessors
These providers process personal data on Aveexia’s behalf where Aveexia acts as processor. Voice and AI providers are used only in the channels and features the customer has enabled.
| Provider | Purpose | Data | Location | Transfer basis |
|---|---|---|---|---|
| Render | Application servers and background jobs | All data in transit and during processing | Frankfurt, Germany | EU. SCCs for access from outside the EU/EEA |
| Supabase | Database and sign-in | Account data and Customer Data at rest | Zurich, Switzerland | EU adequacy decision for Switzerland |
| Redis Cloud (Redis Ltd.) | Cache, queues and rate limiting | Temporary session and queue data | Paris, France | EU |
| Vercel | Hosting of website and dashboard | Request metadata, such as IP address | Global edge network | SCCs / Data Privacy Framework |
| OpenAI | Language model for answers, memory and transcription (Whisper) | Messages, knowledge excerpts, voice audio in the voice channel | Per provider agreement, may be outside the EU/EEA | SCCs / Data Privacy Framework |
| ElevenLabs | Speech synthesis (text to speech) in the voice channel | Reply text to be read aloud | Per provider agreement, may be outside the EU/EEA | SCCs / Data Privacy Framework |
| 46elks | Telephony and SMS (telecom operator, itself responsible for traffic data under LEK) | Phone numbers, call metadata, SMS content | Sweden | EU |
| Sentry | Error monitoring | Technical error reports, may contain transient identifiers | EU | EU |
| Stripe | Payments and invoicing | Invoice details, payment identifiers | EU and USA | SCCs / Data Privacy Framework |
| Zoho Mail (EU) | Sending email, such as replies and notifications | Recipient address and email content | EU | EU |
| Firecrawl | Fetches and reads the customer’s own public web pages when the customer uses web import for knowledge sources | Web addresses the customer provides and public page content | USA | No specific transfer mechanism documented. Public content only |
| Meta (WhatsApp Business Platform) | Delivery of WhatsApp messages. Used only if the customer enables the WhatsApp channel | Phone numbers and message content in the WhatsApp channel | Per provider terms, may be outside the EU/EEA | Per provider terms |
Tools where Aveexia is the controller
These tools are used on aveexia.com only after consent and do not involve Customer Data: Google Analytics, Microsoft Clarity, PostHog (EU region), and Vercel Analytics and Speed Insights. See the cookie policy.
In addition, Aveexia uses PostHog (EU region) server-side for pseudonymous product events, such as an account having been created. No message content is sent there. Demo bookings are placed in Aveexia’s own Google calendar with Google Meet, where Aveexia is the controller.
Customer’s own integrations
When the customer connects a calendar, CRM, booking system or messaging channel (for example Google, Microsoft or Muntra), it is done with the customer’s own account and agreement with that provider. They are not Aveexia’s subprocessors. WhatsApp is the exception: the channel runs through Aveexia’s shared Meta app, so Meta is listed as a subprocessor above when the customer enables it.
Changes
We notify customers by email at least 30 days before a new subprocessor is used, and the customer may object under the DPA. Questions: privacy@aveexia.com. Version 2026-11-08.