Key takeaways
- Set retention by the question each record answers later: a disputed order, a tax return, an injury claim, a returning guest's allergy.
- A card security code captured on a recording must be made unrecoverable once authorization is complete, even if the file is encrypted[2].
- Online order history is dispute evidence: Visa's compelling-evidence route looks back 365 days for earlier undisputed orders[1].
- Privacy guidance pushes the other way: keep only what you need, only as long as you need it, under a written policy[3].
- A complaint about an injury or allergic reaction puts its recording on hold; the schedule stops until your insurer or lawyer releases it[4].
Every record answers a question later
Most restaurant phone systems that record calls have a retention setting nobody has touched since installation. Some keep everything indefinitely, which turns a coaching tool into a growing pile of guests' voices, phone numbers and the occasional card number. Others delete after 30 days and quietly take the recording of last month's disputed catering order with them. Neither is a policy.
A workable schedule starts with a different question: what will someone need this record to prove, and when? A recording of a guest asking about parking proves nothing after the shift. A recording of a guest agreeing to a 40-person buffet with a nonrefundable deposit may be the only evidence you have three months later. The reservation note that says “severe shellfish allergy, seat away from the raw bar” protects that guest every time they return. Each of these deserves a different keep-until date.
Four kinds of clock set the floors for guest-facing records: card disputes, tax records, claims that might end up in court, and privacy rules that limit how long you hold personal data. Card security codes are the one item with a ceiling of zero. This guide covers the phone and guest side only; payroll, I-9s and food-safety logs are in restaurant recordkeeping: what to keep and how long.
The records in scope
- Call recordings: the audio of reservation, order, catering and complaint calls, wherever your phone system or answering service stores it.
- Transcripts and call summaries: text versions of the same calls, often copied into email inboxes and shared drives without anyone noticing.
- Voicemails: audio files and their transcriptions, frequently forwarded to a manager's personal email.
- Reservation notes: party size, occasions, seating preferences and dietary or allergy notes in the reservation system.
- Order history: online and phone-link orders, delivery addresses, the device and account details your ordering system logs.
- Catering and event files: inquiries, quotes, signed contracts, deposits, banquet event orders and final invoices.
- Card data: any card number, expiry date or security code that was spoken, written on a pad or captured on tape.
Recording itself has its own consent rules, which vary by state; see restaurant call recording laws by state before you change what you record. Everything below assumes the recordings were made lawfully, with a notice at the start of the call.
The clocks that set the minimum
At authorization
A card security code on a recording must be made unrecoverable once the payment is authorized[2]
60 days
Window for a cardholder's billing-error notice, counted from the first statement showing the charge[5]
365 days
Visa's lookback for earlier undisputed orders used as compelling evidence[1]
3 years
IRS general period for records that support a tax return[6]
Floors, not targets. Your acquirer, insurer, state law or a pending claim can set a longer period.
Card disputes come first because they are the most common reason a restaurant goes looking for an old call. Under Regulation Z a cardholder's billing-error notice must reach the card issuer within 60 days after the first statement that shows the charge, and the errors it covers include goods or services not delivered as agreed[5]. A catering client who says the order arrived an hour late and half-empty is describing exactly that. Card networks run their own dispute timelines on top, so treat 60 days as the floor for any recording or file tied to a charge, not the whole window.
Order history matters for a different reason. For card-not-present orders, Visa's merchant dispute guide describes compelling evidence built from at least two earlier undisputed transactions on the same card, processed within the 365 days before the disputed one and matched by identifiers such as device ID or IP address plus account or delivery details[1]. That defense only exists if your ordering system kept a year of history. Visa also tells merchants to link receipts, invoices and correspondence by a consistent reference such as an order number[1], which is the habit that makes a call summary findable when the dispute arrives.
Taxes set the longest routine floor. Sales records, catering invoices and deposit records support your return, and the IRS's general rule is three years, stretching to six if more than 25% of gross income went unreported and seven for a bad-debt deduction[6]. That matters for catering: a client who never paid the balance becomes a bad debt, and the contract, the invoice and the call where they agreed to the terms belong in the same file for seven years.
Card numbers on tape: the one zero-day rule
Phone orders and deposits create the one record you must not keep. PCI guidance says the card security code may not be stored after authorization, even encrypted, and if a call recording captures it, the merchant has to securely delete it or render it unrecoverable once authorization is complete[2]. The same guidance says the card number itself should be stored only as the business genuinely needs, under a data-retention policy that keeps storage to a minimum and deletes data as soon as it is no longer needed[2].
Most restaurants have no way to edit three digits out of a recording, which leaves two practical options: keep card numbers off recorded lines entirely, or use a system that pauses recording while the card is read. The first is simpler. Send a payment link, take the deposit through your booking or catering software, or call the guest back on an unrecorded line from the office. The FTC's long-standing advice to businesses is the same in plainer words: don't keep customer credit card information unless you have a business need for it[3]. The full set of rules for phone payments is in taking card payments over the phone.
Host script for a guest who starts reading their card number on a recorded line: “Please stop there for me. We don't take card details on this line. I'll text you a secure payment link right now, or our manager can call you back to take it.” Then note the call so the manager can check whether any digits were captured.
Paper counts too. A card number written on a host pad, a catering intake sheet or the back of a ticket is stored card data. Shred it the same day the charge goes through.
A retention schedule you can adapt
| Record | Example keep-until | Why | How it goes |
|---|---|---|---|
| Routine call recordings (hours, directions, simple bookings) | 30 to 90 days | Coaching and catching mistakes while they are fresh | Automatic deletion in the phone system |
| Recordings tied to a charge (orders, deposits, catering) | At least 120 days after the charge, longer if disputed | Covers the 60-day billing-error window with room for network timelines | Tag at the time of the call; delete in a monthly sweep |
| Complaint, injury or allergic-reaction calls | Until released by your insurer or lawyer | Possible claim; a hold overrides the schedule | Export to the incident file; never auto-delete |
| Transcripts and call summaries | Same as the recording they came from | A transcript says what the audio says | Delete both together, including inbox copies |
| Reservation and allergy notes | While the guest is active, then 24 months after the last visit | Service and safety for returning guests | Annual purge of inactive profiles |
| Online order history | At least 13 months | Compelling-evidence lookback for card disputes | Ordering platform setting or export |
| Catering contracts, deposits and invoices | 3 years after the event; 7 if written off as bad debt | IRS record periods | Archive by event date |
| Card security codes, anywhere | Not kept after authorization | PCI rule for sensitive authentication data | Keep off recorded lines; shred paper the same day |
Two rules make the table work. First, a transcript or summary inherits the schedule of its recording; deleting the audio while a word-for-word transcript sits in three inboxes is not deletion. Second, every record tied to money gets tagged when it is created, not reconstructed later. A host who marks a call “deposit taken” takes two seconds. Finding that call in four months' worth of recordings without the tag takes an afternoon.
Reservation notes deserve more care than they usually get. An allergy note is exactly the kind of detail that keeps a returning guest safe, and handling it on the phone is covered in allergy questions over the phone. It is also health information about a named person. Keep it while the guest is active, purge it when they are not, and limit who can export the guest list. The fine-dining example shows a reservationist copying confirmed bookings and their notes into the reservation system, which is the moment to decide where that note will live and for how long.
Privacy rules push the other way
Every floor above has a counterweight. The FTC's guide for businesses boils data protection down to five principles, and two of them are about retention: keep only what you need for your business, and properly dispose of what you no longer need. It also tells businesses to keep information only as long as necessary and to write the retention policy down[3]. A recording you no longer need cannot help you, and it can still be lost, stolen or subpoenaed.
Breach rules make the cost concrete. Every state, the District of Columbia, Puerto Rico and the Virgin Islands have laws requiring notification of security breaches involving personal information[7]. Three years of recordings in a cloud account with a shared password is three years of guests you may have to notify. Larger operators in California also answer to the CCPA, which applies above $26.625 million in annual revenue or when a business buys, sells or shares the personal information of 100,000 or more California residents or households[8], and it limits retention to what is reasonably necessary and proportionate to the purpose[8]. Whether that reaches your group is covered in does the CCPA apply to your restaurant.
Holds: when the schedule stops
Some calls stop the clock. A guest who calls to say they had an allergic reaction after dinner, a delivery customer who says they found glass in the food, a caller who slipped on the front steps, a former employee's lawyer asking about a shift: any of these can turn into a claim. Federal court rules address electronically stored information that should have been preserved in anticipation of litigation and was lost because a party did not take reasonable steps to keep it[4]. A recording that auto-deletes on day 30, a week after the complaint, is the kind of loss that rule is about.
Tag it during the shift
The manager on duty marks the call as an incident in the phone system and the manager log, with the guest's name and the time of the call.
Export a copy the same day
Download the recording, transcript, summary and any related order or reservation record into one incident folder with restricted access.
Switch off deletion for it
Exclude the call and related records from automatic deletion, and tell any vendor that stores them to preserve them.
Tell your insurer
Report the incident as your policy requires and ask how long to hold the file. Their answer, or your lawyer's, replaces the schedule.
Release in writing
Delete the hold only when the insurer or lawyer confirms in writing that the matter is closed, then let the normal schedule apply.
Ordinary complaints do not need a hold. A cold entrée or a long wait is settled under your refund and remake policy, and the recording follows the charge-linked line of the schedule.
Make deletion actually happen
- Caller
- Your team
- System
01Caller
Call recorded with notice
Office lunch for 40, deposit discussed, no card read on the line.
02Your team
Summary tagged “catering”
Order number added so the call links to the invoice.
03System
Kept with the charge
Held at least 120 days after the final payment.
04Your team
Dispute or no dispute
If disputed, copied to the dispute file; if not, left to the sweep.
05System
Deleted with its copies
Audio, transcript and inbox copies removed in the monthly sweep.
Example lifecycle. The contract and invoice stay in the catering archive on the tax schedule; the recording does not need to.
Write down every place a call record ends up: the phone system, the answering service, the voicemail inbox, the manager's email, the shared drive where someone saved the catering call. Each one needs its own deletion setting or its own monthly sweep. If an SI Employee answers part of your calls, each call leaves a recording, a transcript and a summary in your AssistCall account, and a summary email in the inbox of whoever you chose to notify. Put both on the schedule as separate lines, and ask how deletion works in each before you write a number of days. If you send summaries on to another system by webhook (integrations), that system goes on the schedule as well.
Then test it once a quarter. Pick a routine call from four months ago and confirm it is gone everywhere, including inboxes. Pick a tagged incident call and confirm it is still there. If you are choosing a system now, retention controls belong on the list of questions in call recording software for restaurants.
Frequently asked questions
Is there a law that says how long a restaurant must keep call recordings?
There is no single federal period for restaurant call recordings. The length comes from what the recording proves: card disputes (a 60-day billing-error window under Regulation Z[5]), tax records for calls tied to catering contracts[6], and holds for possible claims[4].
Can we keep recordings forever, just in case?
You can, but it works against you. The FTC advises keeping personal information only as long as necessary under a written retention policy[3], and every state has breach-notification laws[7], so old recordings add risk without adding value.
A guest read their card number on a recorded call. What now?
The security code must not be kept after authorization, even encrypted; if it was captured, the recording has to be deleted or made unrecoverable once authorization is complete[2]. Process the payment, then delete or edit that recording and fix the process so cards are not read on recorded lines.
How long should we keep online order history?
At least 13 months is a sensible floor, because Visa's compelling-evidence route for disputed card-not-present orders relies on earlier undisputed orders from the 365 days before the disputed one[1]. Keep longer only if a clear business purpose needs it.
Do call transcripts and summaries need their own schedule?
They should follow the recording they came from. A transcript holds the same personal information as the audio, so deleting one and keeping the other defeats the purpose of the schedule.
References
Visa (2026). Visa Dispute Management Guide for Merchants (October 2026) (opens in a new tab) ↑
PCI Security Standards Council (2018). Information Supplement: Protecting Telephone-Based Payment Card Data (v3.0) (opens in a new tab) ↑
Federal Trade Commission (2016). Protecting Personal Information: A Guide for Business (opens in a new tab) ↑
Legal Information Institute (Cornell Law School) (2026). Federal Rules of Civil Procedure, Rule 37(e): Failure to preserve electronically stored information (opens in a new tab) ↑
Legal Information Institute (Cornell Law School), eCFR text of CFPB rule (2026). 12 CFR 1026.13 Billing error resolution (Regulation Z) (opens in a new tab) ↑
Internal Revenue Service (2026). How long should I keep records? (opens in a new tab) ↑
Federal Trade Commission (2026). Data Breach Response: A Guide for Business (opens in a new tab) ↑
California Privacy Protection Agency (2025). Frequently Asked Questions (CCPA) (opens in a new tab) ↑