Last updated 2 November 2026
Privacy & data processing
How AI Rep handles your data, where it lives, and the companies we rely on. Written plainly — no surprises.
Where your data is
Your account, transcripts and call analyses are stored in the EU (Supabase, Frankfurt region). Voice processing and call recordings are with ElevenLabs in the United States, under the EU Standard Contractual Clauses.
Isolated per customer
Row-level security keeps each business’s data separate. We never sell your data.
GDPR-aligned
A Data Processing Agreement is available, and we honour data-subject requests.
Who controls the data
You — the business using AI Rep — are the data controller for the calls your AI handles and the people who call you. AI Rep is your data processor: we process that data on your instructions to run the service, and nothing else.
When you try the demo on our front page
Here the roles are reversed: for the demo on our front page AI Rep is the data controller, not the processor. We are the ones asking for your details, so we are the ones answerable for them.
What we ask for
Your email, your mobile number, and the website address you type in. We also keep a one-way hash of your IP address — never the address itself. If you talk to the demo, what you say in that call too.
Why
To send you the code in two halves, and so know a person is behind it. Every demo costs us real money, so the gate is there to keep robots out. The basis is our legitimate interest in not having the service abused.
Being contacted afterwards
We only contact you if you ticked the box yourself. That is a separate consent and you can withdraw it at any time — asking for a code is not a yes to hearing from us.
How long
The code lives for 10 minutes. An attempt you never finished is deleted after a day. If you did not tick the box, the whole record is deleted after 30 days. If you did, we keep it until you tell us to stop. The voice processor deletes the demo call itself after 30 days.
Who sees it
The email goes through Resend and the text through Twilio, Anthropic reads the website you enter to choose the right demo, and the call itself runs through ElevenLabs — all of them are in the table below. We do not pass your details to anyone else, and we do not sell them.
Visit statistics on airep.dk
We count where visitors to our website come from, so we can see what works. This happens without cookies and without storing or reading anything on your device.
What we record
When you open a page, we store the page's address and language, the domain of the site you came from (never the full address), any campaign tags in the link you clicked, your country, whether it was a phone or a computer, and when.
What we do not store
No IP address, no details of your browser, no cookie and no ID. So we cannot see who you are or link two visits together, and we do not ask for consent. If you are signed in, your visit is not counted.
Why
To see which searches, posts and campaigns bring visitors, and improve the site accordingly. The basis is our legitimate interest in measuring our own marketing.
Where and for how long
The records are kept in our database at Supabase in the EU (Frankfurt region) and deleted after 13 months. We do not pass them on.
Sub-processors
The third parties that help deliver AI Rep, what they do, and where they sit.
Data from Google
When you connect your Google account under Integrations, AI Rep gets access only to what you approve at Google, and uses it only for the features you have switched on.
What we access
Your Google account’s email address, so you can see which account is connected. Google Calendar: the list of your calendars, when they are busy, and the appointments that are created, found, moved or cancelled for a customer through AI Rep. Gmail: permission to send the emails you ask AI Rep to send from your own address. We do not read your inbox. Google Contacts, only if you switch them on: the names, phone numbers and birthdays of your contacts, read-only. We never change your contacts. Google Sheets, only if you switch the call log on: permission to create and write to the files in your Drive that AI Rep creates itself. We cannot see your other files. Google Drive documents, only if you switch them on: permission to read the files you choose yourself in Google's file picker. We cannot see your other files.
What we use it for
Finding free times while a customer is on the phone, booking, moving and cancelling appointments in the right calendar, finding a customer’s own appointments again, and sending confirmations and follow-ups from your address. Nothing else. With Google Contacts on: checking a caller against the contact saved under the number they call from, so that the date of birth on the contact is asked for before an appointment is moved or cancelled, and a booking gets the right name. With the call log on: writing one row per call to a sheet in your Drive (date, number, name, what happened, treatment, time, summary and duration). Never the conversation, the recording, dates of birth or personal identification numbers. With documents on: reading the files you choose, so your AI representatives can answer callers from them, and checking them for changes once a night.
How we store it
The access keys from Google are stored encrypted in our database in the EU. We do not copy your calendar events: we read when you are busy, and keep only what belongs to the task in AI Rep about an appointment (the time, the treatment and the customer’s details from the call). With Google Contacts on, we keep a one-way coded version of each phone number in your contacts and Google’s id for the contact, so a caller can be found in time. We do not store your contacts’ names or birthdays: they are read from Google during the call and not kept. The sheet is yours: it sits in your Drive and stays there, also if you switch the log off, disconnect Google or delete your account with us. We keep only the sheet’s id. With documents on, our voice processor (ElevenLabs) keeps a copy of the text in each file you choose, so your AI representatives can search it. We keep only the file's name, its id and a fingerprint to notice changes. Switching documents off, disconnecting Google or deleting your account deletes the copies. The files in your Drive are never changed or deleted.
How we protect it
Data from Google is always sent encrypted (HTTPS/TLS) between Google, our servers, our sub-processors and your browser. The access keys from Google are also encrypted in our database with AES-256-GCM, under a key kept apart from the database, and our database provider encrypts all stored data with AES-256. Only AI Rep’s servers can read the keys: they are never sent to your browser, and the database’s access rules (row-level security) close every other way to them and keep each business’s data apart. Phone numbers from Google Contacts are kept only as a one-way code made with a secret key (HMAC-SHA-256). We ask Google only for the access each feature needs, and we delete the keys when you disconnect.
Who we share it with
We do not sell any data from Google, and we do not use it for advertising or to develop or train AI models. Free times and the details of an appointment go only to the sub-processors above that need them to handle the call.
How to remove access
Click Disconnect next to Google under Integrations: we revoke the access at Google and delete the keys. You can also remove AI Rep under Security in your Google account. Switching Google Contacts off deletes the coded numbers at once. Switching documents off deletes the copies of your documents.
AI Rep’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Data from Microsoft
When you connect Outlook or Microsoft 365 under Integrations, AI Rep gets only the permissions you approve at Microsoft, and uses them only for the features you have switched on.
What we access
Your basic Microsoft profile, of which we keep only the email address, so you can see which mailbox is connected, and permission to send the emails you ask AI Rep to send from your own address. We do not read your inbox, your calendar, your contacts or your files.
What we use it for
Sending confirmations and follow-ups to your customers from your own address, so they are saved in your Sent Items and replies come back to you. Nothing else.
How we store it
The access keys from Microsoft are stored encrypted in our database in the EU. We copy nothing from your mailbox: the emails we send are the ones written for a task in AI Rep, and they are kept with that task.
Who we share it with
We do not sell any data from Microsoft, and we do not use it for advertising or to develop or train AI models. The details from your Microsoft account go to no one else.
How to remove access
Click Disconnect next to Outlook under Integrations, and we delete the keys straight away. Microsoft keeps your approval of AI Rep until you remove it there: for a personal account under account.live.com/consent/Manage, for a work or school account under myapps.microsoft.com.
What happens on a call
- 1
A call comes in
The number routes to your AI representative through Twilio.
- 2
The AI converses
Audio is processed in real time by ElevenLabs to transcribe and respond.
- 3
Results are stored
The transcript and call analysis are saved in the EU (Supabase). The audio recording stays with the voice processor (ElevenLabs, United States), which also keeps its own copy of the transcript; we store only a link to the recording. Both are deleted there after the period your business chooses.
- 4
Follow-ups, if any
Bookings, SMS, WhatsApp or email run only when the call calls for them — and only to the caller.
Voice processing & international transfers
Your account, transcripts and call analyses are stored in the EU. Live voice processing runs on ElevenLabs (United States), so call audio is transferred to the US during a call, and the recording and a copy of the transcript are kept there until the period you chose has passed. The AI language model behind the conversation (OpenAI, United States) is reached through ElevenLabs, and Resend stores the emails we send in the US. These transfers rely on the EU–US Data Privacy Framework where the provider is certified, and otherwise on the EU Standard Contractual Clauses. We’re transparent about this rather than hide it, and an EU-only voice path is on our roadmap.
Why we may use your data
- Your account and the service: to perform our contract with you (GDPR Art. 6(1)(b)).
- Invoices and bookkeeping: because tax and accounting law requires it (Art. 6(1)(c)).
- Security, error monitoring and stopping misuse: our legitimate interest in a safe service that works (Art. 6(1)(f)).
- Being contacted after the demo: only with your consent (Art. 6(1)(a)).
- Data about the people who call you: we process it on your behalf, so the legal basis is yours as the controller.
Your rights
- Access and export your data
- Correct or delete it
- Restrict or object to processing
- Withdraw consent at any time
- Complain to a data protection authority, for example in the country where you live. Our lead authority is the ULD in Schleswig-Holstein, Germany.
Retention
Recordings are deleted by the voice processor after the period your business chooses under Data & compliance: 30 days, 90 days (the default), 1 year or 2 years. Transcripts and call analyses are kept while your account is active, and you can delete a single call, with its recording, at any time. When you delete your account, we delete your data and have the voice processor delete its copies. Invoices are kept as long as bookkeeping law requires.
Questions, or need a signed DPA?
privacy@airep.dk
WIPE UG (haftungsbeschränkt) · VAT no. DE461583544 · Wester Allee 139, 24941 Flensburg, Deutschland
This page describes how AI Rep processes data and is provided for transparency. It isn’t a substitute for your own legal advice.