What we store and for how long

Calls, recordings, transcripts, account records and logs: what is kept, where, how long it stays, and who else touches it.

Last updated November 2, 2026

2 different relationships run side by side here, and they decide who answers a question about a piece of data.

Your own account records, your name, your email address and your billing history, are ours to look after as the controller. Your calls, and any data about your own customers that you keep in Robofono, are yours: you are the controller and Robofono handles them on your instructions. Someone who called you is your caller, so a question from them about their call goes to you first.

What is stored

Calls. For each call your agent answers: the caller's number and the number they called, the time and length, a transcript, a summary and the outcome, the details the agent collected (such as a name, an email address, a message or a booking), and how the caller answered a recording consent question. The recording only when Record calls is on.

Account and location records. Your name, email address, password hash, the locations you create, the people you invite and the role each was given. 2FA secrets and recovery codes where you enabled them.

Credentials you add. API keys, and the keys and addresses of the tools you connect, such as a Slack webhook or a calendar. They are encrypted at rest, on top of the encryption everything else gets, and are never shown back to you or to anyone in your location after you save them.

Usage and technical records. Request logs for the app and the API, including IP address, browser user agent, action and time. Error reports. The aggregate counts behind your usage figures.

Payment records. Your plan, billing cycle, invoices, and the brand and last 4 digits of the card. Full card numbers go straight to the payment processor and never touch our servers.

Documents you send to get a phone number, such as proof of address, are passed to the telephony carrier for its check. We do not store them.

How long each of them stays

Suggested image Screenshot of the How long we keep it section on the privacy policy page, showing the bullet points from call recordings and transcripts through to backups, with the last updated date visible at the top of the page.
  • Call recordings: the days you set on Call privacy, from 0 to 30. 30 if you leave it empty.
  • Call transcripts: the days you set, from 0 to 730. 90 if you leave it empty.
  • Call summaries, outcomes, messages and bookings: while the location exists. They are deleted with it.
  • The record of a notice or consent change you accepted: your name, the time, your IP address and browser, and the exact words. It stays after the account is deleted, as proof of what was agreed.
  • Activity history: 24 months. Who did what in a location, and when, is kept so the record of what was done can be checked later.
  • Credentials you add: until you remove them, or the account closes, whichever comes first.
  • Account and location records: for as long as the account is open, then 30 days.
  • Invoices and payment records: 7 years, because tax law requires it.
  • Request and security logs: 90 days.
  • Email delivery records: 12 months.
  • 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.

Where it is stored

Account records are stored in western Europe. Call data is stored by your location's business country: in the European Union for a business in the EEA, the United Kingdom or Switzerland, and in the United States for everyone else. The region is set once, when you first choose the country.

Every call also runs through our voice AI provider, which processes it in the United States, for every location, including locations in the European Union.

Who else touches it

A small set of sub-processors, each under a written contract and each used for one purpose:

Suggested image Screenshot of the Sub-processors table on the data processing addendum page, with every row visible and the 3 columns Sub-processor, Purpose and Where.
  • The voice AI provider runs every call: speech to text, the conversation and the agent's voice. It keeps its own copy of the conversation.
  • The telephony carrier provides the phone numbers and connects and routes the calls.
  • The AI model providers run the language models, on calls and for the in-app assistant.
  • Cloudflare runs the hosting, the application, the databases and the storage, including recordings, plus DNS and protection against attacks.
  • Stripe handles cards, subscriptions, invoices and tax.
  • Resend sends email: call alerts, credit alerts, invitations and receipts.

The data processing addendum names every one of them, with what it does and where. That list is updated there before a new sub-processor starts handling anything. If you need a copy of the data processing terms, or a question answered about a specific record, write to support@robofono.com.

Was this helpful?

Still stuck? Send us the profile and the comment you are looking at and we will answer with the fix rather than a link back here.

Contact Robofono support