Privacy policy
What we collect from you, why we have it, who else touches it, how long it stays, and how to make it go away.
Last updated November 2, 2026Applies to robofono.com and the Robofono app
This page is available in English
Our legal documents are published in English only until a lawyer has checked each translation. The English text below is the version that applies.
On this page
Who we are and what this covers
Robofono is a AI phone agent service. It is operated by Marketing Released B.V., a private limited company established in the Netherlands. The full company details are on our company information page. This policy explains what we do with personal data when you visit robofono.com, when you use the app, when we answer calls for a business that uses Robofono, and when we handle data on your behalf.
For your own account data, such as your name, your email address and your billing history, Marketing Released B.V. is the data controller. For data about your own customers that you keep in Robofono, you are the controller and we act as your processor. That split matters, because it decides who a person writes to about their data. The processor side is governed by our data processing addendum.
If you called a business that uses Robofono, you are that business’s caller, not our customer. The business decides how its calls are handled and is the controller of your call data; we answer and process the call for it, as its processor. Questions and requests about a call go to the business first. If you write to us, we pass your request on and help the business complete it.
Questions about anything here go to privacy@robofono.com.
What we collect
Calls we answer for a business
When a business’s agent answers a call, we process, on the business’s behalf: the caller’s phone number and the number called; the time and length of the call; the caller’s voice, as audio, while the call runs; a transcript; a summary and the outcome; the details the agent collects, such as a name, an email address, the reason for calling, a message or an appointment; how the caller answered a recording consent question; and, only if the business records its calls, the recording. Callers can say anything on a call, so a call can contain more than this, including sensitive details a caller chooses to share.
Phone numbers and the documents behind them
Some countries only issue a phone number after the business proves its address and sometimes its registration. The documents a business sends for that are passed to our telephony carrier for its check and are not stored by us.
Account and workspace data
Your name, email address, password hash, the locations you create, the people you invite and the role you gave each of them. If you enable two-factor authentication we store the secret and your recovery codes.
Signing in with Google, Microsoft or Facebook
If you sign in with one of these, we ask only for the basic sign-in permissions (for Google: openid, email and profile) and receive your name, your email address and the account identifier the provider gives our app. We store the identifier and the email address so we can recognize you next time. We do not store an access token from the provider, we do not call it again on your behalf, and we do not post anything on your behalf. Robofono’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.
Credentials you add
API keys you create, and the addresses and secrets of the tools you connect, such as an outgoing webhook, a Slack incoming webhook or a calendar. They are encrypted at rest and are never shown back to you or to anyone else in your workspace after you save them.
Support tickets
The messages and images you send to support, and any assistant conversation you choose to attach to a ticket.
Usage and technical data
Log records of requests to the app and the API, including IP address, browser user agent, the action taken and the time. Sign-in records. Error reports. Aggregate counts we use for capacity planning and for the usage figures shown on your billing page.
Payment data
Your plan, your billing cycle, invoices and the last 4 digits and brand of your card. Full card numbers go straight to Stripe and never touch our servers.
Why we process it, and on what basis
| What we do | Legal basis |
|---|---|
| Run the service you signed up for | Performance of a contract |
| Charge you, send receipts, and keep the records tax law requires | Contract and legal obligation |
| Send service email such as credit alerts, invitations and trial notices | Contract |
| Keep the service secure, prevent abuse and duplicate trials, and debug failures | Legitimate interests |
| Send product news and marketing email | Consent, withdrawable in 1 click |
| Handle data about your own customers inside your workspace | On your documented instructions, as your processor |
| Answer, transcribe, summarize and, where the business chose to, record calls for a business | On the business’s documented instructions, as its processor. The business needs its own legal basis |
| Keep the record of who accepted responsibility for the caller notices and consent settings of a location | Legitimate interests: proof of what was agreed |
Where we rely on legitimate interests, we have weighed them against your rights. You can object at any time using the contact address below.
How the AI features handle data
On calls
Every call is handled by our voice AI provider. It turns the caller’s speech into text, runs the conversation with a language model, and speaks the agent’s answers. The audio and the text of every call pass through it, and it processes them in the United States, for every business, including businesses in the European Union. Its language models come from a small set of AI model providers, also in the United States. The voice AI provider also keeps its own copy of the conversation under its data processing terms with us. Each of these companies is named, with what it does and where, in the sub-processor list of our data processing addendum.
A business can turn recording off for a location. We then keep no audio of its calls; the transcript and the summary are kept as the business set them.
The in-app assistant
The in-app assistant, in its Copilot tab, its Help tab, and the read-only assistant in the agency staff console, only reads what the signed-in person may already see; the Help tab reads the help articles instead. Only your question and the text of the records it looks up are sent to the AI models, shortened where long; images, avatars, attachments and links are never sent. It proposes a change on a card, and nothing happens until you confirm it; an unconfirmed card expires after 10 minutes. We store your questions, its answers and the names of the tools it used, never the records it looked up. A conversation is deleted within 30 days of starting. Only you can read your own conversations; our staff do not, except for what you choose to send to support.
- The AI models come from a small set of sub-processors. Each is bound by contract to process the content only to return our result. The table in the next section says what they receive and where they run.
- We update that table whenever it changes, and before a new sub-processor starts handling data.
- We do not opt in to any program that trains AI models on your data.
- We do not send them your credentials, your card details or the contents of your team list.
Who else processes it
We use a small set of sub-processors. Each one is under a written contract with confidentiality and security terms, and each is used only for the purpose named here. The sub-processor list of our data processing addendum names each company.
| Processor | What it does | Where |
|---|---|---|
| Cloudflare | Hosting, application runtime, database and object storage, plus DNS and protection against attacks | EU and US |
| Stripe | Card payments, subscriptions, invoices and tax calculation 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 |
| Voice AI provider | Runs every call: speech to text, the conversation and the agent’s voice. Receives the call’s audio and text, and keeps its own copy of the conversation | US |
| Telephony carrier | Phone numbers, connecting and routing calls, transfers, and the address checks some countries require for a number | US |
| AI model providers | Language models: on calls, through the voice AI provider, and for the in-app assistant and help bot, which send your question and the text of the records it looks up | US |
The current list always lives on this page and in the data processing addendum. We publish changes there before a new processor starts handling data, and customers can object as set out in that document.
Other recipients, when they apply. If you reached us through an agency, that agency sees the locations it runs for you, because running them is the service you bought from it, and if it bills you, it does so through its own Stripe account. If you set up an outgoing webhook or use the API, the data goes to the address you chose. If a business connects a calendar, the bookings its agent makes, with the caller’s name and number, are written to that calendar, and a call the agent transfers goes to the number the business chose.
Beyond this list, we share data only when the law requires it, and only after checking that the request is valid and no broader than it has to be. We do not sell personal data, and we do not share it for advertising.
International transfers
Some of the processors above operate in the United States. Where personal data leaves the European Economic Area or the United Kingdom, the transfer runs on the European Commission’s Standard Contractual Clauses together with the UK addendum, backed by a transfer risk assessment we keep on file and check annually.
Account data is stored in western Europe. Call data, meaning transcripts, summaries, recordings and the details collected on calls, is stored in the region of the business 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. The region is set once, from the business’s country.
Some processing happens outside those regions whatever the business’s country. Our 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 we do not describe Robofono as hosted in the EU. Requests also pass through Cloudflare’s global network on their way in. Transfers outside the EEA run on Standard Contractual Clauses.
How long we keep it
- Call recordings: only kept when the business records its calls, and then for the number of days the business set, from 0 to 30. 30 if it set none.
- Call transcripts: for the number of days the business set, from 0 to 730. 90 if it set none.
- Call summaries, outcomes, collected details, messages and bookings: while the business’s location exists, and deleted with it.
- Records of accepted caller notice and consent settings: who accepted, when, from which IP address and browser, and the exact words. Kept after the account is deleted, as proof of what was agreed.
- Activity history: 24 months. Who did what in a location, and when.
- Credentials you add: until you remove them or the account closes. Whichever comes first.
- Account and workspace records: for as long as the account is open, then 30 days.
- Invoices and payment records: 7 years, because tax law says so.
- Request and security logs: 90 days. Records of successful sign-ins: 180 days.
- Email delivery records: 12 months.
- Assistant conversations: 30 days from the start.
- Support tickets, including attached images and any conversation you attach: while your account exists, deleted with the account (images you upload but never send: 24 hours).
- Backups: a daily copy of our databases, each kept for 28 days, so every copy is gone by day 30. Call recordings are never in a backup. A deletion reaches the backups as they expire, and a backup is never restored to undo one.
Deleting your data
You have 2 ways to get data out of our systems, and neither needs an email to support:
- Delete your account from Settings, Danger zone. We email you a link, you press it, and the deletion starts after 24 hours. Until then you can cancel from the email we send. Your phone numbers are released, and your data, including every call, transcript and recording, is deleted within 30 days, apart from invoices we are required to keep and the records of accepted settings described above. Each backup is kept for 28 days, so the deleted data is gone from backups by day 30.
- Remove a social sign-in. Removing Robofono in your Google, Microsoft or Facebook settings stops that provider sharing new data with us. To delete what we already hold, delete your account or follow our data deletion page.
If a business that uses Robofono holds your details, for example because you called it, and you want them removed, write to the business or to privacy@robofono.com. We will pass the request to the customer whose workspace holds it and, where we are permitted to act directly, delete it ourselves within 30 days.
Your rights
If the GDPR, the UK GDPR or a comparable law applies to you, you have the right to ask for a copy of your data, to correct it and to have it deleted. You can also restrict or object to processing, receive your data in a portable format, and withdraw consent where consent was the basis.
Write to privacy@robofono.com and we will answer within 1 month. We do not charge for this, and we will not make the service worse for you because you asked.
If you are not satisfied with our answer you can complain to your local data protection authority. We would rather you told us first, so we get the chance to fix it.
How we protect it
- Everything is encrypted in transit with TLS, and encrypted at rest. Credentials you add get a second layer of application-level encryption.
- Passwords are hashed with a memory-hard algorithm and are never recoverable, by us or by anyone else.
- Access to production data is limited to the engineers who need it, is authenticated with two factors, and is logged.
- Workspaces are isolated at the query layer, so one customer’s data cannot be read from another customer’s session.
- If a breach affects your personal data we will tell the supervisory authority within 72 hours and tell you without undue delay, with what happened and what we did about it.
Children
Robofono is a business tool and is not directed at children. We do not knowingly collect data from anyone under 16 as a user.
Changes to this policy
When we change something that affects you, we update the date at the top of this page and email account owners at least 30 days before it takes effect. Changes that only clarify wording go live when they are published. Previous versions are available on request.
How to contact us
Privacy questions, requests and complaints: privacy@robofono.com
Anything else: hello@robofono.com
Marketing Released B.V., Pauwenkamp 142, 3607 GK Maarssen, the Netherlands, the Netherlands. Chamber of Commerce number 62865668. The full entry is on our company information page.
Our lead supervisory authority is the Autoriteit Persoonsgegevens in the Netherlands. You can complain there or to the authority where you live.