How long can call data be stored under the GDPR?
There is no statutory uniform retention period for call data. Article 5(1)(e) GDPR allows storage only for as long as the purpose requires; after that the data has to be erased (Article 17), unless a statutory retention obligation applies. In practice: set a period per type of data, justify it, document it and enforce it technically.
This article is orientation, not legal advice. For your specific situation the topic belongs with your data protection adviser.
Why "how long can we keep it?" is the wrong question
Anyone searching for the permitted retention period expects a number — "30 days" or "6 months". The GDPR names none. It ties retention to purpose: personal data may be kept in a form that permits identification for no longer than is necessary for the purposes for which it is processed (Article 5(1)(e) GDPR, storage limitation). Once it is no longer necessary for them, you have to erase it without undue delay (Article 17(1)(a)), unless an exception under Article 17(3) applies, such as a statutory retention obligation (point (b)). A period that fits every business does not follow from that: an emergency service that wants to be able to prove its callouts has different purposes from a hair salon taking appointment requests. So the right question is: "what do I need which piece of data for, and for how long?" The answer also belongs in your privacy notice: Article 13(2)(a) GDPR requires you to state the retention period or, where that is not possible, the criteria used to determine it.
Define a retention period for each type of data
An AI phone assistant produces several different types of data, and they deserve different retention periods:
- Transcripts: the most detailed material. The purpose is handling the request and settling follow-up questions about that one call. Our suggestion, not a legal rule: set this period by how long follow-up questions and complaints about a single call realistically arise in your business, and keep it shorter than the period for summaries. scoco.ai sets 21 days by default and gives exactly that reason in its data processing agreement.
- Summaries: condensed, but still personal data. If you want to keep them longer, for a case history for example, you should be able to name the purpose.
- Contact details (name, callback number): these can pass into the customer file — at which point the period you set for the customer file applies, not the call log's.
- Metadata (time, duration, the caller's number): personal data too, insofar as they can be linked to a person. Whether you need them for longer than the content, for billing or for an analysis without call content for example, depends on the purpose.
Statutory retention obligations can come on top and postpone erasure (Article 17(3)(b) GDPR). Under German commercial law, merchants have to keep received business letters and copies of sent business letters for six years, and accounting vouchers for eight years (§ 257(1) and (4) HGB; for credit institutions, insurers and investment firms it stays at ten under commercial law). German tax law sets the same periods for business letters and accounting vouchers in § 147(1) and (3) AO, plus six years for other documents insofar as they are relevant for taxation. The eight years for accounting vouchers have applied since 1 January 2025; before that it was ten (the Fourth Bureaucracy Relief Act; for commercial law Article 95 HGBEG).
Whether a call transcript can be a business letter or a tax-relevant document, the statutes do not say expressly. Under § 257(2) HGB, business letters are only documents that concern a commercial transaction („nur Schriftstücke, die ein Handelsgeschäft betreffen"); a transcript is a written record of a phone call, not a letter sent or received. Whether it falls under the rule has not been decided — clarify it for your case with your tax adviser or your data protection adviser. Where an obligation applies, it covers the document it captures, such as the order confirmation or the invoice, not automatically every call transcript that goes with it.
The deletion route has to work, not just exist
Defined periods are half the job; the other half is carrying them out. Three requirements to put to the provider:
- Automatic deletion once the period expires: where deletion follows fixed rules, the technical systems should be able to carry it out automatically, recommends the Standard Data Protection Model of the German data protection conference (SDM module 60 "Löschen und Vernichten", deletion and destruction).
- Deletion in the individual case: if a caller demands erasure and one of the grounds in Article 17(1) GDPR applies, you have to be able to find the record and remove it, and you have to respond within one month (Article 12(3)). The processor has to assist you (Article 28(3)(e)). Self-service in the dashboard is the fastest way to do it.
- Documentation: the periods belong in the provider's data processing agreement, in your record of processing activities where Article 30 GDPR obliges you to keep one (Article 30(1)(f): "where possible, the envisaged time limits for erasure"), and in your privacy notice — and specifically the periods actually configured, not the ones theoretically possible.
Ask plainly while you are still choosing: "where do I set the retention periods, and how do I delete a single record?" And: "how do I get out all the data on one person?" You need that when a caller asks for access under Article 15 GDPR.
Honestly: backups lag behind
Backups are part of the security of processing: Article 32(1)(c) GDPR requires the ability to restore the availability of and access to personal data in a timely manner after an incident. Deleted data can therefore linger in backups until they expire on their normal rotation. The German data protection conference's SDM says this about it (module 60): the duty to delete covers backups in principle, but it does not have to be carried out there at the same moment as in the live data; if immediate deletion that preserves the backup's integrity would take too much effort, it can coincide with the scheduled overwrite. In every case, data that reappears after a restore has to be deleted again at once. For data with a high protection need, such as health details, the module sets stricter requirements, up to unscheduled correction runs in the backups.
So ask the provider three things: how long are backups kept? Are they read in normal operation? What happens to deleted data when a backup is restored? If a provider claims that deletions take effect immediately in every backup too, ask how that is done technically.
How to recognise a good deletion policy
As a checklist: defined periods per type of data instead of one blanket period · periods configurable and documented · automatic deletion once they expire · single-record deletion as self-service · backup lag named rather than kept quiet · restored data deleted again · all of it written down in the data processing agreement.
At scoco.ai you choose the periods yourself under Settings > Data & privacy: scoco.ai deletes transcripts after 7, 14, 21, 30, 60 or 90 days (21 by default), and calls and summaries after 12, 18, 24 or 36 months (12 by default). The minimum is 12 months because scoco.ai produces the monthly invoice from the call data; owners and admins can still delete a single call in the inbox at any time, immediately and with its transcript, summary and history. Deletion runs automatically every night. Transcript excerpts that Ask scoco quoted in an answer follow the second period (data processing agreement, Annex 1). scoco.ai provides the complete export of all data on request, and exports the data on a single person on your instruction (data processing agreement § 7, which provides for reimbursement of reasonable effort for help beyond the self-service). Encrypted backups expire after six months at the latest and are never used to restore anything deleted; if a backup is restored, scoco.ai deletes again without delay whatever had been deleted in the meantime. The data processing agreement does not provide for unscheduled correction runs in the backups (§ 10(4)). No call recordings come into existence, only transcripts and summaries — so the deletion question concerns searchable text instead of audio archives. The details are in the help centre under "Data retention".
Frequently asked questions
Is there a statutory maximum period for transcripts?
No. The GDPR names no number, only the principle of storage limitation: as long as the purpose requires (Article 5(1)(e)). You as the controller set the actual period, justify it, state it in your privacy notice (Article 13(2)(a)) and enforce it technically.
Do I have to delete data if a caller demands it?
Yes, if one of the grounds in Article 17(1) GDPR applies, for instance because you no longer need the data for the purpose or because the caller has objected under Article 21 and there are no overriding grounds, and if no exception under Article 17(3) applies, such as a statutory retention obligation (point (b)) or the establishment, exercise or defence of legal claims (point (e)). You have to respond within one month (Article 12(3)). The right is exercised against you as the controller; the processor has to assist you (Article 28(3)(e)).
What happens to the data when the contract ends?
Under Article 28(3)(g) GDPR the processor deletes the data or returns it, at your choice, unless an obligation to store it applies; the EDPB recommends that it confirms the deletion to you (Guidelines 07/2020, para. 141). At scoco.ai the data stays available for export for 30 days after the contract ends, the deletion is announced at least 14 days ahead, and proof of it is available on request (data processing agreement § 10). Export beforehand whatever you have to keep or want to keep.
Do the call's metadata count as personal data too?
Yes, insofar as they can be linked to a natural person: Article 4(1) GDPR covers data through which a person is identifiable directly or indirectly, expressly including by an identifier. A phone number with a timestamp can do exactly that. Metadata therefore need a retention period as well; whether they are needed for longer than the content, for billing for example, depends on the purpose.
Status & sources
As of 2026-11-15.
- Not legal advice. Regulation (EU) 2016/679 (GDPR): Article 4(1), Article 5(1)(e), Article 12(3), Article 13(2)(a), Article 15, Article 17(1) and (3), Article 21, Article 28(3)(e) and (g), Article 30(1)(f), Article 32(1)(c)
- § 257 HGB (German Commercial Code: retention of documents; paragraph 2: business letters, paragraph 4: periods) and Article 95 HGBEG (application of the version in force from 1 January 2025)
- § 147 AO (German Fiscal Code: rules on the retention of documents; paragraphs 1 and 3)
- Fourth Bureaucracy Relief Act (Viertes Bürokratieentlastungsgesetz) of 23 October 2024, BGBl. 2024 I No. 323
- German data protection conference (Datenschutzkonferenz, DSK): Standard Data Protection Model, module 60 "Löschen und Vernichten" (deletion and destruction), version 1.0a, valid since 2 September 2020 (section 2; M60.S09, M60.S10)
- European Data Protection Board (EDPB): Guidelines 07/2020 on the concepts of controller and processor in the GDPR, version 2.1, adopted 7 July 2021 (para. 141)
- scoco.ai: help centre "Data retention" (verified 2026-11-15) and data processing agreement (German), as of 15 November 2026 (§ 7, § 10, Annex 1 no. 7)
- Product details for scoco.ai: as of 2026-11-15