Privacy Policy
Last updated October 9, 2026
This policy explains what personal data DinnerDiary collects when you use our website and our iOS and Android apps, why, who we share it with, how long we keep it, and the choices and rights you have.
Who we are
DinnerDiary (“we”, “us”) is run by the operator of the DinnerDiary service, who decides how and why your personal data is used and is the “controller” of that data under data protection law. For anything about your data, email privacy@dinnerdiary.app.
Information we collect
- Account details: email address, name, username, password (stored only as a salted hash), sign-in method (password, email link or code, Google, Apple), two-factor settings, and when you agreed to AI features.
- Profile and social data: optional bio, home city, avatar, Instagram and TikTok handles, friends, follows, blocks, comments, community ratings, and list invitations.
- Lists and places: places you save, ratings, notes, visits, tags, favorites, rankings, and photos you upload.
- Location: only if you allow it. On the web we ask only when you tap “Near me” in search or the locate button on a map; the apps ask before showing places around you. We use it to centre the map and bias search results. Your home city and its coordinates are stored if you set them.
- Billing: your plan, subscription status and renewal date. Card details are handled by Polar, Apple or Google, never by us.
- Device and push data: push notification tokens for the browser or device you enabled notifications on, tied to the signed-in session.
- Reports and support: content reports you send (what you reported, the reason and any note) and emails you send us.
- Technical data: IP address, browser or app version and request logs, which our hosting providers process to run the service, limit abuse and fix errors.
- Analytics: cookieless page views on the website and, only if you opt in, session recordings of our public pages (see Analytics).
How we use it, and our legal bases
Where the EU or UK GDPR applies, each use rests on one of these legal bases:
| Purpose | Data | Legal basis |
|---|---|---|
| Create your account, sign you in, store and sync your lists, photos and settings | Account, lists and places, photos, device data | Contract (providing the service you asked for) |
| Social features: friends, shared and public lists, comments, invitations, notifications | Profile and social data, push tokens | Contract |
| Billing, plan limits and subscription management | Account, billing data | Contract; legal obligation (tax and accounting records) |
| Maps, place search and nearby results | Search text, location if you allow it | Contract; location only with your permission |
| AI features: vibe search, AI answers, recommendations, imports from links and screenshots | See AI processing | Consent (you can withdraw it any time) |
| Security emails, sign-in links and codes, account notices | Email address | Contract; legitimate interest in keeping accounts safe |
| Moderation: handling reports, removing content, blocking and suspending accounts | Reports, the reported content, account data | Legitimate interest in a safe community; legal obligation where the law requires us to act on notices |
| Preventing abuse, fraud and spam; rate limiting | Technical data, account data | Legitimate interest in protecting the service and users |
| Counting page views to improve the website | Cookieless analytics | Legitimate interest (no cookies, no profiles) |
| Session recordings of our public pages | Clicks, scrolls and page layout, with typing masked | Consent (off unless you turn it on) |
We don’t sell your personal data, use it for advertising, or share it with advertisers or data brokers.
AI processing
AI features run through Vercel AI Gateway with models from OpenAI, Anthropic, DeepSeek and Alibaba Cloud (Qwen). The gateway sends each request either to the company that made the model or to a cloud inference provider that hosts the same model; Vercel names the providers it uses in its sub-processor list. We ask for your permission on the website and in the apps before the first AI request, store that choice with your account, and you can withdraw it any time (Settings › Privacy on the web, Settings in the apps); AI features then stop working until you allow them again. Providers process the data only to return a result and don’t use it for advertising. What is sent depends on the feature:
- Vibe search, AI answers and recommendations: what you typed, plus the names, cities, cuisines, list names, your ratings and been/want-to-try status of the saved places relevant to it. Place descriptions are also turned into search vectors by OpenAI.
- Link import: the Instagram or TikTok link, and the caption and location tag our server reads from that public post.
- Screenshot import: in the apps, the text read from the screenshot on your device and, only when that text isn’t enough, the image itself. On the website the browser can’t read text from images, so the screenshot image itself is uploaded and sent to the AI provider. Screenshots are processed in memory and never stored.
- Place tags: public place details (name, address, cuisine) are tagged by AI with no personal data attached.
Service providers
These companies process personal data for us, under contracts that limit them to providing their service:
| Provider | What for | Data involved |
|---|---|---|
| Railway | Hosting the API, database and cache | All account and app data |
| Vercel | Hosting and delivering the website | Technical data, requests passing to the API |
| Amazon Web Services (S3 and CloudFront) | Storing and delivering photos and avatars | Photos and avatars you upload |
| Plunk | Sending email: sign-in links and codes, verification, security notices, moderation alerts | Email address, email content |
| Mapbox | Maps and map images on the website and in the apps; on the website, turning your location into a country for search | IP address, the map area you view, coordinates when you use “Near me” |
| Place search and details (Google Places), Sign in with Google, Android push (Firebase Cloud Messaging), Google Play billing | Search text and your location if you allow it, Google account email and name if you use it, push tokens and notification text, purchase records | |
| Apple | Sign in with Apple, iOS push (APNs), App Store billing; on iOS, Apple Maps and location services (showing the map when Mapbox isn’t available, and turning your location into a country for search) | Apple ID email (or relay address) and name if you use it, push tokens and notification text, purchase records; on iOS, the map area you view and your coordinates if you allow location |
| RevenueCat | Validating in-app purchases and syncing Plus access | Your DinnerDiary user ID, purchase receipts |
| Polar | Web subscriptions, as Merchant of Record (see Payments) | Name, email, billing details |
| Vercel AI Gateway with OpenAI, Anthropic, DeepSeek and Alibaba Cloud (Qwen), and the cloud inference providers that host their models (see Vercel’s sub-processor list) | AI features, only with your consent | See AI processing |
| Browser push services (Google, Mozilla, Apple, Microsoft) | Delivering web push notifications you turned on | An encrypted notification for your browser |
When you import a link, our server fetches that public post from Instagram or TikTok. They see a request from our server for that link, not who you are. Our analytics server (Umami, at umami.elshazly.dev) is run by us, not by an analytics company.
Analytics
- Page views: on the website we count page views with a self-hosted Umami server. It sets no cookies, drops query strings and anything after “#”, records private share links only as “/shared/[token]”, and sends nothing when your browser has Do Not Track or Global Privacy Control turned on, or when you have turned off usage analytics in Settings.
- Product events: when you’re signed in, on the website and in the iOS and Android apps, our API records a small set of events about how the product is used: for example signing up, creating a list, adding or rating a place, accepting a friend, following a list, importing from Google Maps, finishing onboarding, seeing the upgrade screen, opening a shared list, and starting, renewing or cancelling a subscription. Each event carries only a few plain properties (like the platform, or whether a place was marked been). It never includes your name, email, list titles, place names, notes or share links. Events go from our server to the same self-hosted Umami server, keyed by a one-way hash of your account id rather than the id itself, with no cookies or device identifiers. You can turn this off at any time in Settings → Privacy → Usage analytics; from then on nothing is recorded for your account, on any device. We use these counts in aggregate, on the basis of our legitimate interest in improving the product.
- Session recordings: off unless you turn them on in “Privacy choices” at the bottom of our pages. When on, we record clicks, scrolling and page layout on our public pages (home, FAQ and comparisons) while you’re signed out, with typing masked. Signed-in pages are never recorded. Turning it off stops recording immediately.
International transfers
Several providers above are based in, or process data in, the United States and other countries outside your own. Where the EU or UK GDPR applies, we transfer data only on a recognised basis: an adequacy decision (including the EU-U.S. Data Privacy Framework and its UK extension for certified providers) or the European Commission’s Standard Contractual Clauses (with the UK addendum), plus the provider’s own safeguards. Email us for a copy of the relevant safeguards.
Public content and discoverability
Public lists, comments on public lists, community ratings and public profiles are visible to anyone and may be indexed by search engines. Profiles are friends-only and new lists private until you change them. List owners can remove comments on their own lists.
Payments
Web payments are processed by Polar as Merchant of Record, which keeps its own billing and tax records under its privacy policy. Purchases in the iOS and Android apps are processed by Apple or Google under their policies. We never see or store full card details.
Cookies and local storage
We use a first-party session cookie to keep you signed in and protect your account. Your browser’s local storage keeps preferences such as theme, your last search country, dismissed prompts and your privacy choices. We don’t use advertising or third-party tracking cookies.
How long we keep data
| Data | Kept |
|---|---|
| Account, lists, places, notes, ratings, comments, photos | Until you delete them or your account. Deleting your account removes them straight away; photos and avatars are then deleted from storage (failed deletions are retried every hour). |
| Places you added to someone else’s list | Stay on that list after you delete your account, without your name (shown as “Former member”); your own ratings and notes on them are deleted. |
| Sign-in sessions | Until you sign out, or 7 days after you last used them. |
| Push notification tokens | Until you sign out, turn notifications off, or the push service reports the token expired. |
| Sign-in links, codes and verification links | Until used, or until they expire (within an hour). |
| Content reports | As long as needed to handle the report and deal with repeat abuse. Reports you filed are deleted with your account. |
| AI requests and screenshots | Not stored by us beyond answering the request; screenshots are never stored. |
| Backups | Database backups expire on a rolling schedule, so deleted data leaves them within weeks. |
| Billing records | Kept by Polar, Apple or Google as tax and accounting law requires. We delete your Polar customer record when you delete your account. |
| Server logs | Kept by our hosting providers for a short period. |
Your rights
Wherever you live, you can:
- see and correct your data in the app, and download a copy from Settings (export);
- delete your account and data (see how to delete your account);
- withdraw consent for AI features or session recordings at any time, without affecting what happened before.
EU, EEA and UK: you also have the right to access, rectify, erase, restrict or object to our use of your data, to data portability, and to lodge a complaint with your local data protection authority. We answer requests within one month.
California and other U.S. states: in the last 12 months we collected identifiers (email, username, IP address), customer records, commercial information (plan and purchases), internet activity (usage of the service), geolocation (only when you allow it), and the content and photos you add, for the purposes listed above, and disclosed them only to the service providers listed above. We do not sell or “share” personal information for cross-context behavioral advertising, and we don’t use sensitive personal information to infer characteristics about you. You may ask to know, correct or delete your personal information, and we will not treat you differently for doing so. An authorized agent may make a request on your behalf; we will verify the request with you.
To use any right, email privacy@dinnerdiary.app from your account’s email address.
Children
DinnerDiary is not directed to children under 13, or under the higher age of digital consent in your country (up to 16 in some EEA countries), and they may not create an account. If you believe a child has given us personal data, email us and we will delete the account.
Security
Data is encrypted in transit, passwords are stored only as hashes, and you can turn on two-factor authentication in Settings. No service is perfectly secure; if a breach affects you, we will tell you and the authorities as the law requires.
Deleting your account and subscriptions
You can delete your account in Settings on the website or in the apps; this page explains what is removed and what is kept. Deleting your account cancels a web (Polar) subscription. App Store and Google Play subscriptions can only be cancelled by you in your Apple Account or Google Play settings, so cancel them before deleting your account.
Changes to this policy
We may update this policy. Material changes are posted here with a new date.
Contact
Questions or requests? Email privacy@dinnerdiary.app.