Data processing
Who’s who
Section titled “Who’s who”Under UK GDPR and the Data (Use and Access) Act 2025:
- You, the restaurant, are the controller of your diners’ personal data. You decide why it’s collected and how it’s used: taking and fulfilling orders, receipts, your loyalty scheme, your marketing.
- direct.eat is your processor. We handle that data only on your instructions, to run your ordering site, kitchen tools and marketing features.
- direct.eat is a controller for its own data: your merchant account, billing, support records, platform security logs and fraud signals. If a diner creates a direct.eat sign-in that works across restaurants, we’re the controller of that login too.
- Stripe processes card payments for you as an independent controller under its own terms with you.
What we process for you
Section titled “What we process for you”| Whose data | Your diners, and your staff who use direct.eat |
| What data | Name, email, phone, delivery address, order history, order notes, allergy notes the diner chooses to give you, marketing consent records, loyalty and gift card balances, feedback and reviews, IP address and device data |
| Why | Taking and fulfilling orders, order updates and receipts, customer accounts, loyalty and gift cards, reviews and feedback, and marketing that you approve and send |
| How long | For the length of your subscription, then as set out under Retention |
Allergy notes can reveal health information. They’re shown to your kitchen to keep diners safe, and never sent to AI features.
Our commitments to you
Section titled “Our commitments to you”As your processor we:
- process diner data only on your documented instructions;
- make sure our staff are bound by confidentiality;
- keep it secure (see Security);
- use sub-processors only as listed below, give you 30 days’ notice of changes and let you object;
- help you answer data subject requests, carry out impact assessments and handle breaches;
- tell you about a personal data breach affecting your data without undue delay, and within 24 hours of confirming it;
- let you take all your data out at any time (the export pack), and delete it after you leave;
- never use one restaurant’s diner data to market another restaurant, for direct.eat’s own marketing, or to train AI models.
Sub-processors
Section titled “Sub-processors”| Sub-processor | What for | Where |
|---|---|---|
| Supabase | Database, sign-in and file storage | London, UK (eu-west-2) |
| Cloudflare | Hosting your storefront and dashboard, custom domains, security | Global edge network |
| Resend | Sending emails | See the sub-processor list |
| Twilio | Text messages and missed-order phone calls | See the sub-processor list |
| Anthropic | AI features: menu import, summaries and the assistant | See the sub-processor list |
Our system of record is in the UK. Where a sub-processor handles data outside the UK, the transfer is covered by the UK–US data bridge where the provider is certified, or otherwise by the UK International Data Transfer Agreement or Addendum. The full, current list (including where each provider processes data and the transfer mechanism) is published with our merchant terms, and owners are emailed 30 days before any change.
Stripe is not on this list because it acts as an independent controller for payments under its own agreement with you.
Retention
Section titled “Retention”Retention is automatic: a job runs every hour and anonymises or deletes data when its time is up. The same schedule is shown in Settings → Privacy and data protection and in the privacy notice on your storefront.
| Data | Kept for | Then |
|---|---|---|
| Diner name, email, phone, order note, delivery address and messages on orders | 24 months after the order | Anonymised; amounts, VAT, items and dates kept |
| Device and browser details captured at checkout | 90 days | Removed |
| Allergy notes on orders | 3 years | Note removed |
| Tip recipient detail | 3 years | Recipient removed; the tip amount stays |
| Orders, items, payments and refunds (financial records) | 7 years (HMRC: 6 years after the financial year) | Archived at 3 years, then deleted |
| Customer accounts with no activity | 24 months after the last order or activity | Anonymised; opt-outs kept as hashes |
| Marketing permission records after an opt-out | 24 months | Deleted; a hashed do-not-contact entry is kept |
| Marketing send and click records | 25 months | Deleted |
| Marketing attribution (which flyer or link brought an order) | 13 months | Deleted |
| Personal content of sent emails | 30 days | Removed; delivery status kept |
| Email delivery log | 13 months | Deleted |
| SMS, call and push text previews | 90 days | Text removed; cost and status kept |
| API request logs, including IP address | 90 days | Deleted |
| Webhook request and response bodies, printed ticket content | 30 days | Removed |
| Activity (audit) log | 24 months; refund, price, allergen, billing and privacy events 6 years | Deleted |
| First names given at table ordering | 90 days | Removed |
| Copies of data released to a requester | 7 days | Link expires, copy deleted |
| Privacy request and complaint records | 6 years after closing | Kept as evidence |
| Your merchant account and billing | Billing 6 years after your contract ends | Personal account data anonymised 90 days after closure |
| Backups | Rolling | Expire; erasures are re-applied if a backup is ever restored |
Deleting financial records at 7 years is done by our team, not automatically.
After you leave: once your plan ends, your account is closed and your data is kept for 90 days, then deleted, apart from the billing records we must keep. Download the export pack before you go, and keep your own copy of your VAT records for 6 years. See Data export and cancelling.
Requests from diners
Section titled “Requests from diners”Diners can ask to see, correct, move or delete their data, or object to how it’s used. Because you’re the controller, these requests are yours to answer, and the dashboard does the work:
- Every storefront footer links to Your data and privacy (
/privacy-request), where a diner makes a request and confirms it by email. Signed-in diners can also ask from their account. - Privacy requests in your dashboard shows each request with its deadline (one month), finds the person’s data across all your shops, and lets you download or send a copy and erase their personal data in a few clicks. See Privacy requests and complaints.
- Diners can delete their own storefront account themselves. Their order records are kept for tax, with personal details removed.
- If a request about your diners reaches us, we acknowledge it within 2 working days and pass it to you within 1 working day. We answer directly only for data we control.
Cookies
Section titled “Cookies”Storefronts set no non-essential cookies and no third-party trackers. Which flyer or link brought a diner is kept in that browser tab’s temporary storage and saved only with their order. Visit counts are cookie-free, and diners can opt out with Don’t count my visit in the footer.
Your duties as controller
Section titled “Your duties as controller”- Have a privacy notice on your storefront and keep your legal details up to date (see Storefront settings).
- Only send marketing to diners who agreed, or who you can contact under the soft opt-in. direct.eat records consent for you. See Campaigns and consent.
- Register with the Information Commission and pay the data protection fee if you need to.
- Keep your team’s logins to themselves and remove leavers promptly.
Related
Section titled “Related”Was this page helpful?