Compliance

Last updated 19 November 2026

A plain summary of how Ringabee meets the GDPR and the EU AI Act, for businesses deciding whether to use it. The binding terms are in our terms and privacy policy. This page is not legal advice.

At a glance

  • Your business is the data controller for your customers’ data. Ringabee is your processor.
  • Every account gets a data processing agreement under Article 28 of the GDPR. It is part of our terms, so it applies from sign-up with nothing extra to request or sign.
  • Our database and hosting are in Ireland. The AI that writes replies is in the United States; see where data goes.
  • Customers are always told they are talking to an AI, before the conversation starts, on calls and in chat. This cannot be turned off.
  • Calls are not recorded. Transcripts are deleted after 30 days by default.

What your customers are told

Every call starts with this greeting, before anything else is said:

“Hi, you've reached [your business]. I'm {{receptionist_name}}, an AI assistant. This call may be recorded or transcribed so I can help with your request. How can I help today?”

The chat widget shows an AI and privacy notice before the first message. It says the customer is chatting with an AI assistant for your business, asks them to share only their name, phone number, service and time, and asks them not to share health, payment or other sensitive details. It links to your own privacy policy when you add one in your settings.

EU AI Act

Ringabee is a limited-risk AI system: an assistant that talks with people. It is not a high-risk system, because it does not make decisions about people’s access to jobs, credit, education, essential services or anything similar. It does not use biometrics, voiceprints or emotion recognition, and it does none of the practices the Act bans.

The rule that applies to Ringabee is the transparency duty in Article 50: people must be told they are interacting with an AI. That rule has applied since 2 August 2026. Ringabee meets it with the greeting and notice above.

GDPR

  • Only what a booking needs. Ringabee asks for name, phone number, service and time. It never asks for email, address, payment or health details.
  • Your customers’ rights. You can export or delete a customer’s data yourself from your dashboard, by phone number or email. Deleting also removes the matching calendar event where it can.
  • Sub-processors are named. Every provider is listed, with what it does and where, in our privacy policy. We tell you before adding or replacing one, so you can object.
  • No AI training on your data. We do not allow any provider to use your customers’ data to train AI models.
  • Data protection officer. We have not appointed one, because the GDPR does not require one for the kind of processing Ringabee does. Questions go to our privacy contact below.

Where data goes

DataWhere it is processed
Bookings, transcripts, business detailsSupabase database, EU (Ireland)
Website and appVercel, EU (Dublin)
Call audio and speech-to-textTelnyx, in its EU voice region
Conversation text, to write each AI reply (chat and calls)Anthropic, United States, under standard contractual clauses
Emails to the business ownerResend, which may be outside the EU
The business owner’s plan payments (never customers’ data)Stripe Payments Europe (Ireland), with transfers to the United States
AppointmentsThe business’s own Google Calendar

On calls, Telnyx turns the audio into text, and only that text is sent to Anthropic to write each reply. Audio is not sent to Anthropic. Ringabee does not currently offer an EU-only AI option.

How long data is kept

DataKept for
Chat and call transcripts30 days by default (the business can choose less), then deleted automatically
Call recordingsNot made: recording is off
AppointmentsUntil the business deletes them, or deletes the customer by phone number or email
Usage counts (no conversation content)Up to 90 days
Security and access logs (no customer details)Up to 180 days

Security

  • Data is encrypted in transit (TLS) and at rest (AES-256).
  • Each business can see only its own data. The database enforces this itself, not just the app.
  • If a breach affects your data, we tell you within 48 hours of becoming aware of it, so you can meet your own 72-hour duty to the Data Protection Commission.
  • Ringabee itself does not hold SOC 2 or ISO 27001 certification. Our database and hosting providers, Supabase and Vercel, have SOC 2 Type 2 reports.

Health and other sensitive businesses

Ringabee is built for businesses such as barbers, salons and trades, where bookings involve no sensitive information. It is told never to ask for health details. If you run a clinic, a legal practice or another business where customers may share sensitive information, talk to us and take your own advice before using Ringabee.

Questions

For anything about compliance, or to ask for a copy of these details for your records, email us at legal@ringabee.com.