This is the version effective October 11, 2026, kept unchanged for reference. The version in force is always at dindin.recipes/privacy.
DinDin Privacy Policy
T. Krajewski, trading as DinDin, 77 Lower Camden Street, Saint Kevin’s, Dublin, D02 XE80 (“DinDin”, “we”) is the data controller for the personal data described here. This policy explains what we collect when you use the DinDin app and dindin.recipes, why, where it is stored, who sees it and what your rights are. Questions: privacy@dindin.recipes.
1. What we collect and why
| Data | Where it comes from | Why we use it | Legal basis (GDPR) |
|---|---|---|---|
| Account: email address, Google or Apple account identifier, sign-in times, the name your sign-in provider shares (or that you type during onboarding) | You, when you sign in with Google or Apple | To create and secure your account and to address you by name; your name is shown only to you | Contract (Art. 6(1)(b)) |
| Profile: username, avatar choice | You | Shown to other signed-in users (search, followers, the people you cook with) | Contract |
| Home cuisine, dietary needs and the goals you pick during onboarding | You | Personalise your map, suggestions and the onboarding tour; visible only to you | Contract |
| Activity: quiz answers, dishes you save, plan or cook, ratings and comments, shopping lists, kitchens you belong to and their names, who you follow, kudos you give, who you credit as a cook on a photo | You, as you use the app | To run the features you use and compute your progress and achievements | Contract |
| Photos of dishes you cooked | You (camera or photo library, only when you choose to upload) | Shown on your profile and in feeds to other signed-in users, and on the profile of anyone you credit as a cook | Contract |
| Dares: who you dare, the mode, date, dish and the short note you write; friend and dare invite links you create | You | To run dares and invites; the note is shown to the person or kitchen you dare | Contract |
| Blocks you make, and reports you file (what you reported, the reason, any details) | You | To hide blocked people from you (and you from them) and to review reported content | Contract; legitimate interest in keeping the Service safe (Art. 6(1)(f)) |
| Reports about your content: the reporter’s reason and a snapshot of the content at the time, plus our decision and note | Other users, and our team | To act on abuse within 24 hours and to recognise repeat behaviour; the reporter is not shown to you | Legitimate interest in keeping the Service safe, and our legal obligations |
| Onboarding activity: which steps you went through, how long they took, what you tapped in the tour | Your device, during onboarding only | To find where new cooks get stuck and improve the tour | Legitimate interest in improving the Service |
| Usage analytics: which screens and features you use (for example finishing a quiz, saving or cooking a dish, opening the paywall), with dish and dare ids, your account identifier, a random identifier for the app install, device type and app version. Never your name, email, username, photos or anything you type. See section 4 | Your device, only after you agree | To understand which features work and where people get stuck, and to measure subscriptions and retention | Consent (Art. 6(1)(a)); you can withdraw it at any time |
| Subscription status and purchase events (product, dates, an anonymised App Store transaction reference) | Apple, via RevenueCat | To unlock the app and keep purchase records; if you agreed to usage analytics, also to measure subscriptions alongside it | Contract; legal obligation for accounting records; consent for the analytics use |
| Crash and error reports: what went wrong, where in the app, the steps just before it, device model, operating system and app version, and your account identifier | Your device automatically, when the app crashes or hits an error | To find and fix bugs | Legitimate interest in a working Service (Art. 6(1)(f)) |
| Spam limits: how many photos, invite links and kitchen members you added in the last 24 hours | You, as you use the app | To limit spam from new accounts | Legitimate interest in keeping the Service safe |
| Technical data: device type, app version, IP address in server logs | Your device automatically | To keep the service running and secure | Legitimate interest (Art. 6(1)(f)) |
| Notifications you receive in the app | Generated by us | To tell you about follows, kudos, kitchen changes, dares, cook credits and events | Contract; you can mute in settings |
We do not collect your location (neither precise nor approximate, and we do not work it out from your IP address), contacts, health data or advertising identifiers, we do not track you across other companies’ apps or websites, and we do not sell personal data. Your food choices may hint at religion or health; we do not infer or process such categories, and we ask you not to add them to free-text fields such as comments, kitchen names or dare notes.
2. Where your data is stored
Your data is stored in the European Union (Amazon Web Services, Ireland) by our hosting provider Supabase. Photos are stored in the same region and are only reachable through short-lived links generated for signed-in users. If you use DinDin from outside the EU, your data still lives in the EU. Some of the providers in section 3 handle part of it outside the EU; section 3 says which and how it is protected.
3. Who we share it with
We share personal data only with processors that help us run the Service, each under a data-processing agreement:
- Supabase, Inc. — database, authentication, file storage and serverless functions (EU hosting).
- Apple Inc. — App Store purchases and subscription management, and Sign in with Apple; Apple’s own privacy policy applies to your Apple ID.
- Google LLC — sign-in with Google (we receive your email, your name and a stable account identifier; we do not receive your Google password or contacts).
- RevenueCat, Inc. — subscription status processing between Apple and our servers, and, if you agreed to usage analytics, passing purchase events on to PostHog.
- PostHog, Inc. — usage analytics, only if you agreed (EU hosting, Frankfurt).
- Functional Software, Inc. (Sentry) — crash and error reports (EU hosting).
- Cloudflare, Inc. — hosting and protection for dindin.recipes, and routing of our support and privacy mailboxes.
Other signed-in users see your username and avatar, your cooked-dish photos with their rating comment, your follower and following lists, the names of kitchens you share with them and the notes on dares you send them. They do not see your email, your name or your home cuisine. Blocking someone hides all of this from them, and theirs from you. We disclose data to authorities only when legally required.
Some of these providers are based in the United States and handle the data they need there: RevenueCat (your account identifier and subscription events), Cloudflare (requests to dindin.recipes and emails to our mailboxes) and, for sign-in, Apple and Google. Where personal data is transferred outside the European Economic Area, it is protected by the EU–US Data Privacy Framework where the provider is certified under it, and otherwise by the European Commission’s Standard Contractual Clauses. You can ask privacy@dindin.recipes for a copy of the safeguards that apply.
4. Analytics and marketing
DinDin uses PostHog for usage analytics, and only with your consent. Until you agree in the app, nothing is sent; if you decline, nothing is sent ever. You can change your mind at any time in the app or by emailing privacy@dindin.recipes, and from then on nothing more is sent.
- What is sent: the events described in the table in section 1, linked to your account identifier so that we can follow one person’s path through the app. We do not send names, emails, usernames, photos, comments, notes or anything else you type.
- Where: PostHog’s EU servers in Frankfurt. Your IP address is not stored with these events, and it is not used to work out your location.
- Purchases: if you agreed, RevenueCat also sends your trial, purchase, renewal and cancellation events to PostHog, so that we can see which features lead to a subscription.
- No recordings: we do not record your screen or sessions.
The onboarding activity in the table above is recorded by us, on our own servers, whether or not you agree to analytics. Crash and error reports (Sentry) are about faults in the app, not about how you use it, and are sent without consent under our legitimate interest in a working app. They do not include your IP address or location.
DinDin has no advertising, uses no advertising SDKs and does not share data with advertisers or data brokers.
5. How long we keep data
- Account, profile and activity data (including photos, dares and onboarding activity): for as long as your account exists.
- Blocks: until you unblock the person or delete your account.
- Content reports: until a person on our team has decided them, then 12 months, so that repeat behaviour can be recognised. A report you filed is deleted with your account; a report about your content is kept, without your account details, for the same 12 months.
- Friend and dare invite links: valid for 7 days, deleted a month after they expire.
- Notifications: 90 days, then deleted.
- Quiz searches: 12 months, then deleted.
- Usage analytics (PostHog): up to 12 months, and deleted with your account.
- Crash and error reports (Sentry): 90 days.
- Spam-limit counters: only the last 24 hours count; older ones are cleared.
- Server and security logs: up to 30 days.
- Purchase records: 7 years after the transaction, in pseudonymised form, to meet accounting obligations.
When you delete your account, your account, profile and activity data (including your photos), your blocks, the reports you filed and your invite links are deleted immediately; reports about your content are kept for 12 months without your account details, as described above; kitchens you created are handed to another member or deleted if you were the only one. A photo you posted that other people are credited with cooking is handed to one of them, with your rating and comment removed, so they keep the dish on their record; photos only you cooked are deleted. Cook credits and kudos you gave to other people’s dishes are removed with your account. Your analytics profile and its events at PostHog are deleted at the same time. We keep one anonymous line saying that an account was deleted, with how many days it existed, whether it ever had a subscription and whether one was still active, whether onboarding was finished, how many dishes it cooked, whether it was deleted by its owner, by our team or by an automated process, and the hour of deletion. It contains no identifier, name or email and cannot be linked back to you.
6. Your rights
Under the GDPR (and similar laws elsewhere) you can:
- Access and export your data: in the app, Settings → Profile → Export my data produces a readable JSON file with everything we hold about you, straight away. You can also email privacy@dindin.recipes from the address on your account and we will send it within 30 days, free of charge; ask in the same email if you also want your usage analytics events from PostHog.
- Correct it: edit your username, avatar, home cuisine and dietary needs in the app.
- Delete it: Settings → Profile → Delete account removes your account and data as described above.
- Object to or restrict processing based on legitimate interest, and withdraw your consent to usage analytics at any time (section 4); withdrawing does not affect what was sent before.
- Complain to a supervisory authority; in the EU that is the data-protection authority of your country.
For anything the app cannot do, email privacy@dindin.recipes; we answer within 30 days.
7. Security
All traffic is encrypted in transit; data is encrypted at rest by our hosting provider. Access to your rows in our database is enforced per user at the database level (row-level security), and only a small number of administrators can access production systems, with multi-factor authentication. Administrators see reported content only through the report queue. If a breach affects your data we will inform you and the supervisory authority as the law requires.
8. Children
DinDin is not directed at children under 16 and we do not knowingly collect their data. If you believe a child has created an account, contact privacy@dindin.recipes and we will delete it.
9. Changes
We will post changes here and, for material changes, notify you in the app. The effective date at the top tells you which version applies; every version, with a summary of what changed, is listed under Version history.
10. Contact
T. Krajewski, trading as DinDin, 77 Lower Camden Street, Saint Kevin’s, Dublin, D02 XE80 — privacy@dindin.recipes