Sub-processors
Last updated 17 October 2026
These are the service providers that process personal data for Restado AI. Transfers to the United States rely on the EU–US Data Privacy Framework where the provider is certified, otherwise on Standard Contractual Clauses.
| Provider | What for | Data | Location |
|---|---|---|---|
| Supabase | Database, sign-in, file storage (call recordings, logos) | All data at rest | European Union |
| Amazon Web Services | Application servers, secrets, logs | Data in transit; logs carry ids, not call content | European Union or United States (region set at launch) |
| Vapi | Telephony and the live voice pipeline | Call audio, live transcript, call details, the context of the call (never access codes) | United States |
| Deepgram (via Vapi) | Speech-to-text | Call audio | United States |
| ElevenLabs (via Vapi) | Text-to-speech | The assistant's spoken replies | United States / European Union |
| Phone carrier (via Vapi): Twilio, Telnyx, Vonage or a SIP carrier, per number | Phone numbers and call routing | Phone numbers, call routing | United States / European Union (by carrier) |
| OpenAI and/or Groq | The voice model during calls; summaries, follow-ups, translation after calls | Transcripts and summaries | United States |
| Anthropic | Sambo, the team assistant in the dashboard | Team members' questions and the operational data they ask about | United States |
| Resend | Emails to the team (alerts, invitations, the morning digest), and the PIN email to guests when the booking has a real email address | Recipient email and the message (for guests: email, first name, PIN) | United States |
| Twilio | SMS and WhatsApp messages with guests, when the client turns them on | Guest phone number and message text | United States |
| Vonage | The PIN by text message, when a booking has no email and no booking-system message thread | Guest phone number, first name, PIN | United States / European Union |
| Telegram | The team assistant and alerts in the chats a client's team links | Team members' messages; issue titles in alerts (no guest contact details) | United Kingdom / United Arab Emirates (Telegram's data centres vary) |
| Stripe | Subscription payments and invoices | The paying client's billing contact and payment details (card data never reaches us) | United States / European Union |
| Seam | Smart-lock codes for each stay, when the client connects its locks | Lock identifiers, the stay's code and validity window (no guest names) | United States |
| Error tracking (Sentry-compatible; provider confirmed at launch) | Reports of software errors | Error type, scrubbed message and technical context — no names, contact details, codes or message text | European Union where available |
Also connected, at the client's choice and under the client's own agreements with them: Hostaway, Guesty (booking systems), and the client's own systems it connects through the API or webhooks. Restado reads bookings from them and, only when the client allows it, sends guest replies through them.
We give clients 30 days' notice before adding or replacing a sub-processor.