Before you choose an online ordering provider, ask for a written account of what happens to your order and guest records when the contract ends. You need to know what you can retrieve, how long you can retrieve it, what the provider keeps, and when each type of record is deleted.
A download before you leave is useful, but it does not answer the whole question. Records may also remain in backups, support systems, or services used by the provider. Compare those terms before signing or renewing, not after your account has closed.
Start with the records your restaurant needs
List the information that passes through your ordering setup and decide why you may need it later. Ask your manager, bookkeeper, marketing lead, and anyone who handles guest questions to identify the records they use. Your payment provider and ordering provider may hold different pieces of the same transaction.
For example, a manager may need an order history to answer a dispute about a missing item. A bookkeeper may need transaction summaries for reconciliation. A marketing lead may need a record of how a guest joined or left a mailing list. These are different needs, so a single promise to retain “customer data” is too vague.
| Record type | Possible business need | Question to ask |
|---|---|---|
| Orders and item details | Resolve an order question or reconcile sales | Can we retrieve item-level records after termination? |
| Guest contact details | Respond to a guest about an existing order | When is access removed, and when are copies deleted? |
| Marketing preferences | Understand a guest’s subscription or opt-out status | Are preferences and their dates included in a retrieval? |
| Payment and refund records | Match transactions and investigate refunds | Which records are held by the ordering provider versus the payment provider? |
| Support records and backups | Understand what remains outside the main account | How long are these copies retained, and who can access them? |
Use the table as a starting inventory, not a promise that every provider stores every field. Add delivery instructions, canceled orders, adjustment history, or other records your operation relies on. Ask each provider to identify which records it actually holds and which are held elsewhere.
Also separate information you need to keep from information you merely find convenient. Longer retention may help with an old question, but it can leave more guest information stored for longer. Your preferred terms should reflect both concerns.
Compare access, retrieval, and deletion timelines
Ask the provider to map the full sequence from notice of cancellation through account closure and deletion. The key dates may differ: your staff could lose dashboard access before the provider deletes the records, and a backup could remain after the main account is removed.
Request answers for each record type, including:
- What event starts the clock: cancellation notice, the end of the paid term, or account closure?
- What is the last date we can access the account or request records?
- How long does a retrieval request take, what format is available, and are there limits or charges?
- When are records deleted from active systems, backups, and support tools?
- Can any records be restored from a backup after account closure? If so, under what conditions?
- What written confirmation of deletion can we request, and what does it cover or exclude?
Ask about exceptions separately. A provider may describe circumstances in which it keeps some records longer. Find out which categories are affected, the stated reason, who can access them, and what happens when the exception ends. Do not assume that an account deletion confirmation covers every copy unless the provider says so in writing.
A hypothetical decision
Suppose a restaurant expects to need item-level order details for 60 days after its ordering contract ends. Provider A says the restaurant can access those details for 30 days after closure. Provider B offers 90 days of access. Both descriptions are assumptions for this example, not offers from actual vendors.
On the access period alone, B better fits the restaurant’s stated need. A could still be workable if it confirms a usable retrieval method before access ends and the restaurant accepts responsibility for storing the copy. Neither answer establishes when the providers delete their own copies. The owner should obtain those dates, including backup treatment, before making a decision.
Ask about costs in the same written response. A quote for retrieval is not necessarily the full cost of leaving: staff time, storage, and an unusual request may add work or charges. Request fixed charges, variable charges, and any exception fees separately; avoid comparing a basic retrieval quote with another provider’s broader exit total.
Review the terms and responsibilities before signing
Read the contract, data terms, and any linked policies together. Look for a clear match between the provider’s answers and the documents that govern the relationship. If a sales answer says access lasts longer than the contract says, resolve the difference in writing before relying on it.
Ask a qualified attorney about contractual and legal obligations that apply to your restaurant, including what records you must retain or delete and whether the proposed terms support those obligations. Your bookkeeper or other qualified adviser can help identify records needed for your accounting processes. Do not treat a vendor’s standard retention period as a substitute for that review.
Pay particular attention to responsibility at the handoff. If the provider deletes its copy but your restaurant has downloaded a file, your copy still needs an owner and a storage decision. If another service holds payment or delivery records, ending the ordering contract may not end that separate relationship.
Ask who the provider uses to process or store information, whether those parties receive deletion instructions, and how the provider handles records that cannot be deleted immediately. A useful answer names the categories and process; a broad assurance that “all data is secure” does not establish a timeline.
Check the proposed process without involving guests
Before committing to a procedure, ask the provider to walk through a simulated closed-account request using fictitious records. Have your team check whether the described file would include an order identifier, items, adjustments, and any other fields on your inventory. The simulation should not create a real payment, send a guest message, or dispatch a courier.
This is a check of the proposed workflow, not proof that every historical record will be available or that every copy has been deleted. If you later run a live service pilot, agree on its scope and permissions separately; do not use real guest transactions as a substitute for a safe practice scenario.
Put the exit process and questionnaire in writing
Keep the provider’s answers alongside the signed terms. Name a restaurant contact who can authorize a request and a backup person who can act if that employee leaves. Record the provider’s support contact, request method, response time, and any identity checks. Update the record when the contract or ordering setup changes.
Use these questions when requesting a written retention schedule:
- Inventory: Which order, guest, marketing, payment-related, and support records do you hold for our account? Which are held by other services?
- Access: What event ends our access, and can we request records afterward? Who is authorized to make that request?
- Retrieval: Which fields and formats are available, how long does a request take, and what fixed, variable, or exception charges apply?
- Deletion: When are each category and its copies deleted from active systems, backups, and support tools? Can we receive written confirmation specifying its scope?
- Exceptions: What might you retain longer, for what stated reason, and for how long? Who can access those records?
- Other parties: How do you handle deletion requests involving your service providers, and what records remain with our separate payment or delivery providers?
- Changes: Can retention terms change during our agreement, and how will we be notified?
Turn the answers into a short exit calendar: notice date, last access date, retrieval request deadline, expected delivery date, and deletion confirmation date. Assign each task to a person. Leave enough time to inspect what you receive and ask about missing fields before access closes.
If you are still comparing the broader purchase, use the online ordering buying guide to assess the rest of the setup. Consider how your restaurant website and any separate payment or delivery services fit into the record inventory.
Next step: Use the questionnaire to review your current agreement, then ask Fleksa about its restaurant online ordering setup, applicable retention terms, and verified US availability for your location.
Frequently asked questions
Does canceling an ordering account delete all guest records?
Do not assume it does. Ask when each category is deleted from active systems and backups, what exceptions apply, and whether other services hold separate copies.
Should I retrieve records before my contract ends?
Confirm your last access date and request process well in advance. Retrieve the records your business needs, check their contents, and decide who will manage any copy your restaurant keeps.
What should a deletion confirmation include?
Ask it to identify the account, record categories, systems or copies covered, completion date, and any exceptions. Have a qualified attorney review the terms if you need advice about your obligations.
