The documents your lawyer will ask us for.

Our privacy policy and terms, the providers that handle data for us, how to get our data processing agreement, and how accessible this website is today.

Here is each document, and what it covers.

These are the main providers that handle data for us.

The complete current list, with what each provider processes and where, is available on request. Ask for it before you sign.

These are the main providers that handle data for us.
ProviderWhat it handles
DigitalOceanHosting: our servers and database, in Frankfurt, Germany (EU).
OpenAIAI processing of conversations, to write Sarah’s replies.
AnthropicA second AI model that writes Sarah’s replies when the first is unavailable.
Meta (WhatsApp Business)WhatsApp messages between guests and the hotel.
TelegramTelegram messages between guests and the hotel, and your team’s alerts.
StripeCard payments, on your hotel’s own Stripe account.
VapiPhone calls with Sarah: the call, its transcript and its recording — with Deepgram (transcription), ElevenLabs and Microsoft Azure (voice) and OpenAI behind it.
MicrosoftRead-aloud: turns Sarah’s written replies into voice notes.
ResendThe e-mails we send for your hotel and to your team.
CloudflareNetwork and protection in front of our websites and dashboard; traffic passes through it.
SentryError reports from our software, with request contents and cookies removed.

Last updated: 16 October 2026

Ask for the complete list

Our data processing agreement is available on request.

Under our terms, your hotel is the controller of its guests’ data and Wizorks is its processor. Write to [email protected] to ask for the agreement.

This website aims at WCAG 2.2 level AA, and does not meet all of it yet.

This statement covers wizorks.com. It does not yet cover the chat window, the guest portal or the hotel dashboard.

What works today

  • A skip linkThe first press of Tab offers a jump past the menu, straight to the content.
  • A visible focus ringLinks, buttons and fields show a 2px ring when you reach them with the keyboard.
  • Measured contrastText is measured against 4.5:1, or 3:1 when it is large, in both the light and the dark theme.
  • Readable formsEvery field keeps its label above it and marks what is required, for the eye and for screen readers.
  • Arabic, right to leftThe Arabic pages declare their language and read right to left.
  • Reduced motionAnimations follow your device’s reduce-motion setting, the homepage’s opening scene included; with JavaScript off, the homepage still shows every step of its story.

What does not work yet

  • Form field edgesThe edges of form fields are lighter than the 3:1 contrast WCAG asks for; the label above each field and the focus ring carry them instead.

How we checked: on 13 October 2026 we ran an automated check (axe-core) over the site in English, French and Arabic, at desktop and phone widths, and walked the homepage with the keyboard. On 15 October 2026, after fixing what it found, we ran it again on the homepage and six other pages in English and Arabic, and walked the menu with the keyboard. The pages added that week — legal, security, “How Sarah behaves”, integrations, the channel pages and the press kit — were not part of either check.

Tell us

If something on this website does not work for you, write to [email protected]. A founder answers within one business day.

Email us