Data processing addendum
The processor terms that apply whenever we handle personal data on your behalf: what we do with it, how it is secured, who else touches it, and what happens when you leave.
Dernière mise à jour : November 2, 2026S'applique à robofono.com et à l'application Robofono
Cette page est disponible en anglais
Nos documents juridiques sont publiés uniquement en anglais, jusqu'à ce qu'un juriste ait vérifié chaque traduction. Le texte anglais ci-dessous est la version qui fait foi.
Sur cette page
Scope and roles
This addendum applies whenever Robofono, operated by Marketing Released B.V. in the Netherlands, processes personal data on your behalf, and it forms part of our terms of service. It is written to satisfy Article 28 of the GDPR and the equivalent UK provisions. No signature is needed: it is in force for every customer from the moment the account is created.
- You are the controller of the personal data about your callers, your own customers and your team inside your workspaces, including every call, its transcript, summary and recording, and the activity history. You decide how your calls are handled, what is added, who can see it, and what happens to it.
- We are the processor of that data, acting on your instructions.
- We are a controller in our own right for your account, billing and security data. That part is covered by our privacy policy, not by this addendum.
- If you are an agency or a whitelabel reseller, you are the processor for your clients and we are your sub-processor. This addendum flows down to them unchanged.
Subject matter, duration, nature and purpose
| Subject matter | Answering the inbound calls to your phone numbers with an AI phone agent, and the call records, workspaces, team access, billing and support that go with it. |
|---|---|
| Duration | For as long as your account is open, plus the deletion window in the retention section. |
| Nature of the processing | Receiving and connecting calls, speech recognition, conversation by an AI model, speech synthesis, transcription, summarizing and extracting details, recording where you chose to, booking and transferring, storage, retrieval and erasure. |
| Purpose | Answering your calls on your behalf as you configured the agent, giving you the record of each call, and providing the other features you switched on, including the in-app assistant answering your questions over your own data and proposing changes you confirm. |
| Types of personal data | For callers: phone numbers, the voice audio of the call, transcripts, summaries and outcomes, the details the agent collects (such as name, email address, reason for calling, messages and appointments), recording consent choices, and recordings where you record calls. For your team: names, email addresses and roles, with the records of who did what. Also the questions you ask the assistant and its answers, and support ticket messages and attachments. |
| Categories of data subject | People who call your phone numbers, your own team members, and anyone whose details you add. |
| Special category data | Not requested and not required. A caller may still share it on a call, for example a health detail, and content you add may contain it because you chose to add it. It is then held under the same terms as everything else. If your callers are likely to share it, set the agent and the retention of your transcripts and recordings accordingly, or turn recording off. |
Processing on your instructions
We process personal data only on your documented instructions. Your instructions are: this addendum, the terms of service, the settings you configure in the app, and the requests you make through the API.
If a law we are subject to requires us to process data beyond your instructions, we will tell you before we do it unless that law forbids telling you. If we believe an instruction breaks data protection law, we will say so and may pause that instruction until it is resolved.
We will not sell your data, use it for our own marketing, or use it to train machine learning models.
Caller notices and consent
Telling your callers that they are speaking with an AI and that the call is recorded, getting consent to recording where the law requires it, and giving your callers your own privacy notice are your obligations as controller. We give you the settings to meet them: an opening line that says both, on by default, and a recording consent mode preset for your country. The wording we suggest for what callers hear is a suggestion, not legal advice; only the texts you adopt are spoken.
Turning a notice off, adopting caller texts, or choosing a consent mode that asks less than your country’s preset are your instructions, and each one asks you to accept responsibility for informing your callers and for complying with privacy and recording laws where your business operates. We keep a record of who accepted, when, from which IP address and browser, and the exact words, as proof of what was agreed. That record is kept after the account is deleted.
Confidentiality
Everyone with access to your data is bound by a written confidentiality obligation that survives their engagement with us. Access is granted on a need-to-know basis, is checked quarterly, and is removed the day somebody leaves.
Security measures
We keep the following technical and organizational measures in place, and we do not weaken them during the term:
- Encryption. TLS 1.2 or better in transit, encryption at rest, and a second application-level encryption layer for credentials you add.
- Access control. Two-factor authentication on every administrative account, role-based permissions in the product, and least privilege for production access.
- Tenant isolation. Every query is scoped to a workspace at the data layer, so one customer’s session cannot read another customer’s rows.
- Resilience. Managed, replicated storage with a daily backup of our databases, each backup kept for 28 days. Call recordings are never backed up, and call data from the European Union is backed up only in the European Union.
- Logging. Request and administrative action logs retained for 90 days, with alerting on anomalous access.
- Secure development. A second pair of eyes on every change, dependency scanning, and separate environments for development and production.
- Vendor management. Every sub-processor is assessed before it is used and re-assessed annually.
Sub-processors
You give general authorization for the sub-processors below. The current list is always the one published here; our privacy policy describes the same list by role.
| Sub-processor | Purpose | Where |
|---|---|---|
| ElevenLabs (voice AI provider) | Runs every call: speech to text, the conversation with the AI model, and the agent’s voice. Receives the audio and text of every call, sends us the transcript and the recording after the call, and keeps its own copy of the conversation | United States, for every call, including calls to businesses in the European Union |
| Twilio (telephony carrier) | Phone numbers, connecting and routing calls, transfers, and the address and registration checks some countries require before they issue a number | United States |
| OpenAI | Language models, when an agent on a call, or the in-app assistant and help bot, runs on one of its models. On calls it is reached through the voice AI provider | United States |
| Anthropic | Language models, when an agent on a call, or the in-app assistant and help bot, runs on one of its models. On calls it is reached through the voice AI provider | United States |
| Google (Gemini) | Language models, when an agent on a call, or the in-app assistant and help bot, runs on one of its models. On calls it is reached through the voice AI provider | United States |
| Cloudflare | Hosting, runtime, databases, object storage (including call recordings), DNS and edge protection. Call data is stored in the European Union or the United States, by the business’s country | EU and US |
| Stripe | Payments, subscriptions and invoicing for plans bought from us | EU and US |
| Resend | Email delivery: call alerts with the call’s summary, credit alerts, invitations and receipts | EU and US |
The privacy policy describes this same list by role, and both are kept in step. We update it whenever it changes, including the AI model providers. We give you 30 days’ notice by email before a new sub-processor starts processing your data. If you object on reasonable data protection grounds within those 30 days, we work with you on an alternative. If there is none, you can terminate the affected part of the service and receive a refund of the unused prepaid period.
Each sub-processor is engaged under a written contract imposing obligations no weaker than these. We remain fully liable to you for their performance.
Helping you meet your own obligations
We will help you answer requests from the people whose data we hold for you.
Where a request cannot be handled in the app, we will help you within 5 working days at no extra charge. If a data subject contacts us directly about data we hold for you, we will not answer on your behalf. We will tell them to contact you and let you know it happened.
We will also give you the information you reasonably need for a data protection impact assessment or a prior consultation with a supervisory authority.
Personal data breaches
If we become aware of a personal data breach affecting your data, we will notify you without undue delay and in any case within 48 hours. The notice will describe what happened, the categories and approximate number of records involved, the likely consequences and what we are doing about it, as far as we know at the time, with updates as we learn more. We will not make a public statement identifying you without your agreement, unless the law requires it.
Retention, return and deletion
- Call recordings are kept only when you record calls, for the number of days you set per location, from 0 to 30 (30 if you set none).
- Call transcripts are kept for the number of days you set per location, from 0 to 730 (90 if you set none).
- Call summaries, outcomes, collected details, messages and bookings are kept while the location exists and deleted with it.
- Activity history is held for 24 months.
- Credentials you add are held until you remove them or the account closes.
- Request and security logs are held for 90 days.
- Assistant conversations are deleted 30 days from the start.
- Support tickets, including attached images and any conversation you attach, are kept while your account exists and deleted with the account. Images you upload but never send on a ticket are deleted after 24 hours.
- When your account or a location closes, we release its phone numbers and delete all personal data processed on your behalf within 30 days, except the records of accepted caller notice and consent settings. Each backup is kept for 28 days, so the deleted data is gone from backups by day 30.
- Before deletion you can export everything through the app or the API. Ask within the 30 day window and we will produce the export for you.
- We keep data beyond these periods only where a law requires it, and only for as long as it requires.
Audits and information
On request we will provide the information needed to demonstrate compliance with this addendum, including our security documentation and the reports of our infrastructure providers. That is once a year at most, unless a supervisory authority or a breach makes more necessary. Where that is not enough, you or an independent auditor bound by confidentiality may audit us, on 30 days’ notice, during business hours, without disrupting the service and without access to other customers’ data.
International transfers
Account data is hosted in western Europe. Call data is stored in the region of the location that took the call: in the European Union for a business in the European Economic Area, the United Kingdom or Switzerland, and in the United States for everyone else, set once from the business’s country. The voice AI provider and the AI model providers process every call in the United States while it runs, including calls to businesses in the European Union, so Robofono is not hosted only in the EU. Where personal data is processed outside the EEA or the UK, by those sub-processors, by the telephony carrier or by Cloudflare’s network in transit, the transfer runs on the European Commission’s Standard Contractual Clauses with the UK International Data Transfer Addendum where relevant, supported by a transfer risk assessment we keep on file. By agreeing to this addendum you appoint us to enter into those clauses with sub-processors on your behalf, as controller to processor or processor to processor as the case requires.
Order of precedence and how to accept
If this addendum conflicts with the terms of service, this addendum wins for anything about the processing of personal data. If it conflicts with the Standard Contractual Clauses, the clauses win.
This addendum is in force for every account and needs no signature. If your procurement process requires a countersigned copy, write to privacy@robofono.com with the legal entity name and address and we will return one within 5 working days.