Last updated November 14, 2026
ClickDish privacy policy
ClickDish turns videos, sites, photos and text into recipes. This policy explains what the app and its pages on clickdish.net collect, why, who processes it for us and how to delete it.
In short
- Your recipe book is private. Other people see your recipes and collections only if you share them, and at RIOLD LLC only the person who runs ClickDish can open them.
- To make a recipe, we send what you share to AI services: Claude by Anthropic and Gemini by Google. OpenRouter transcribes the speech in videos. When you tap Enhance cover, OpenRouter passes the cover to OpenAI’s image model, which redraws it in the style you pick.
- Allergens and nutrition targets are optional. We use them only to highlight ingredients, filter recipes and plan your week.
- ClickDish has no ads. To see which of our ads work, the app sends Google and Meta events such as installing it and your first payment, and Adapty, which handles our purchases, sends them your payments and refunds. In the European Economic Area, the United Kingdom and Switzerland, it asks you first. On iPhone, Google and Meta get your advertising identifier only if you allow tracking. On Android, they get it from the start elsewhere and, in those regions, only after you allow sharing.
- You can delete your account and its data in the app: Account › Delete account.
Who we are
RIOLD LLC, 1800 Cold Stream Ct. Apt. 205, Asheville, NC 28803, United States, company ID 2020-000944139, makes ClickDish and is responsible for your data. Contact: [email protected].
This policy covers ClickDish only. Our other apps follow the general privacy policy.
What we collect
We collect what the app needs to work and to see which of our ads bring people to it. ClickDish shows no ads.
- Account. When you sign in with Apple or Google, we get your email address and name. Google also passes your profile photo. If you choose Hide My Email, Apple gives us a forwarding address instead. We never see your password. We use your email to open the same account whether you sign in with Apple or Google. Account shows the first word of your name until you change it, and people see that name when you share a collection with them or give them a gift.
- Your recipe book. The recipes you save or write, with your edits, notes, ratings and favorites; your collections and the ones you follow or joined, your grocery list, meal plan and Want to cook queue; and settings such as language and units. We store them so ClickDish works offline and looks the same on all your devices. Only the person at RIOLD LLC who runs ClickDish can open your account, recipes and collections in our admin tool, to understand how ClickDish is used, to help when you write to support and to check reports.
- What you send for a recipe. Links, text you paste, pages you share from your browser and photos of recipes. For a link, our server fetches the post or page, reads it and deletes any downloaded video when the recipe is ready. We keep the cover and the step frames. Photos you send stay on our server while the recipe is being made, and the first one becomes its cover. We also keep a record of each save: the link or text, the source, whether it worked, how long it took and what it cost us.
- Your own covers. A photo you choose as the cover of a recipe or a collection is stored on our server. Enhance cover sends the recipe’s cover through OpenRouter to OpenAI’s image model, which draws a new one. We keep both, so Restore original brings the old cover back.
- Smart plan. Your answers: how many people you cook for and how many of them are children under 12, meals a day, kitchen equipment, preferences and requests for the week, and what you have at home. When you scan a receipt on iPhone, the phone reads it and sends us only the text. Photos of your fridge or shelf, and of a receipt on Android, are read by Gemini and not kept.
- Allergens and nutrition targets. See the next section.
- Purchases. Apple on iPhone and Google Play on Android take the payment for Premium, cookies (the app’s credits for AI features), Ultimate and gifts, and we never see your card. Adapty, which runs our purchases, receives your account ID, the product, price, transaction ID and subscription status, and device information such as model, iOS or Android version and IP address, and tells our server about purchases, renewals, cancellations and refunds. We keep a record of your free imports and saves, the cookies you get and spend, and the gifts you give and accept.
- Notifications. Your device gets an ID from Firebase Cloud Messaging so we can tell you when a recipe or a plan is ready or new cookies arrive; on iPhone, only if you allow notifications. While a recipe is being saved, we show its progress on your Lock Screen: on iPhone, the app gives us an Apple token for that, and on Android the progress comes through the same Firebase ID.
- Usage and ad data. What you do in ClickDish, including what you search for in Discover, and which ad or post brought you to it. Usage and ad measurement explains what goes where.
- Reports. When you report a collection or a recipe, we record your account ID, the collection or recipe with its title, its author’s account ID and the time. ClickDish then no longer shows you anything from that author. Only the person who runs ClickDish sees reports, in our admin tool.
- Messages to support. Your email address, what you write, and the details the app adds when you tap Contact us: app version, iOS or Android version, device model, language and your account ID. You can delete them before sending.
- Connection data. Cloudflare and Firebase receive your IP address and basic device information when the app connects. They use them to deliver the service and protect it from abuse. Our server keeps the last IP address your account connected from, with the country and city that MaxMind’s GeoLite2 database on our server finds for it, and no earlier addresses. Before you sign in, it keeps only that country and city, without the address. Only the person who runs ClickDish sees them, in our admin tool, to help you, to spot abuse and to see where ClickDish is used.
- Diagnostics. The Firebase, Meta and Adapty SDKs in ClickDish send Google, Meta and Adapty data about their own work, such as crashes and errors in their code.
Allergens and nutrition targets
In Account, you can mark allergens (lactose, gluten, nuts, seafood, pork, eggs, soy, mushrooms or your own words) and set nutrition targets: calories, protein, fat and carbs a day. Both are optional. They can reveal something about your health, and avoiding a food such as pork can reflect your beliefs, so we treat them as sensitive data.
We use them only to:
- highlight ingredients with your allergens in recipes and in cooking mode;
- filter Discover with Allergen-free;
- build your Smart plan. Our server leaves out dishes with your allergens. When Use targets in meal plans is on, your daily targets go to Google’s Gemini with the plan request, so it can choose dishes that fit them.
Your allergen marks stay with us and are never sent to AI services. We never use allergens or targets for ads, never sell them and never share them for any other purpose. Our own analytics records only that you changed them or used Allergen-free in Discover, never what they are.
In the European Economic Area, the United Kingdom and Switzerland, our legal basis is your explicit consent, which you give by entering them. To withdraw it, clear your allergens. Turning targets off stops their use, but the values stay saved so you can turn them back on. To erase them, delete your account or write to us.
Our consumer health data policy describes the same data under Washington’s My Health My Data Act and similar state laws.
Who processes your data
These companies process data for ClickDish. Each receives only what its task needs and must protect it at least as well as this policy does.
| Service | What it does | Policy |
|---|---|---|
| Google Firebase | Sign-in with Apple and Google (Firebase Authentication), your recipe book and settings in Cloud Firestore in Frankfurt, Germany, and notifications (Firebase Cloud Messaging). | firebase.google.com |
| Google Analytics for Firebase | Records how ClickDish is used and, with Google Ads, measures which of our Google ads bring people to the app. | policies.google.com |
| Meta | The Meta SDK measures which of our Meta ads bring people to the app. | facebook.com |
| Hetzner | Hosts our server in Germany. It saves recipes, builds plans, searches your book, shows recipe, collection and gift pages, stores covers, step frames and your photos, and keeps our own analytics. | hetzner.com |
| Cloudflare | Connects the app and clickdish.net to our server. | cloudflare.com |
| Anthropic | Claude reads recipes from videos, sites, text and photos. It receives a video’s frames and transcript, or the text and photos you send. It also translates a shared recipe into the language of whoever opens it. | anthropic.com |
| Google Gemini API | Gemini reads YouTube videos, photo posts and handwritten recipes, picks covers, estimates nutrition, marks allergens in ingredients, sorts grocery items by store aisle, searches your book by description, reads photos of your fridge, shelf or, on Android, a receipt, and builds Smart plan. It also makes a recipe when Claude can’t. | policies.google.com |
| OpenRouter | Transcribes the speech in videos and passes a cover you enhance to OpenAI. It receives the video’s sound or that cover. | openrouter.ai |
| OpenAI | Its image model redraws a cover you enhance in the style you pick. It receives the cover through OpenRouter. | openai.com |
| Apple | Sign in with Apple, App Store payments, notifications, the saving progress on your Lock Screen and Apple Ads attribution. | apple.com |
| Google Play | On Android: payments through Google Play Billing, the country of your Google Play account, and the install referrer, which tells the app which clickdish.net page or which of our Google or Meta ads sent you to install it. | policies.google.com |
| Adapty | Runs Premium, cookie packs, Ultimate and gifts: shows the offers, checks purchases with Apple and Google Play and tells our server about purchases, renewals, cancellations and refunds. It sends your payments and refunds to Google Analytics, and your renewals and refunds to Meta, as described in Usage and ad measurement. It also gets Apple Ads attribution. | adapty.io |
Usage and ad measurement
ClickDish shows no ads. We advertise it on Google, Meta and Apple Ads and in bloggers’ posts. To see how ClickDish is used and which ads and posts bring people who keep using it and pay, the app sends what you do in it to our server and a few of those steps to Google and Meta, and, on iPhone, our server and Adapty ask Apple which Apple Ads ad you came from.
- Our own analytics. Our server records what you do in ClickDish: the welcome screens, signing in and signing out; the Premium and cookie offers you see and what you tap; what you do with recipes, from opening, saving and editing them to cooking mode, and whether each new recipe worked; Discover’s search and filters; your collections, meal plan, Smart plan, scans and grocery list; gifts, sharing, reports, the notifications you open and the clickdish.net links you open or paste; what each action costs in cookies; and the payments, renewals, cancellations and refunds that Adapty reports, with their product and amount. When you change your profile or settings, such as allergens or units, it records only that you changed them, never what you entered. Every record about a recipe includes its type (video, photo, site, text or written by you) and the platform it came from, such as TikTok, and opening a recipe also records which one. We keep it all with a random install ID, your account ID once you sign in, app and iOS or Android versions, device model, your languages, time zone, App Store or Google Play country and the country and city of your last IP address, but without recipe titles, the links you save recipes from, allergens, nutrition targets or email. What you search for in Discover goes only into daily totals by App Store or Google Play country, with no account or install ID: the search text, how many times it was searched that day and whether anything was found. On Android, the app also reads the Google Play install referrer once, after you install it, and our server records where you came from: the clickdish.net page, Google Ads, or the Meta ad with its campaign, ad set and ad. It keeps nothing else from the referrer. If that page, or a link you open or paste on your first day with ClickDish, comes from a blogger’s post, we count your install for that post. We don’t share this analytics with anyone, so it runs without the consent window below.
- Google Analytics for Firebase receives these steps: installing ClickDish, your sessions and how long they last, signing in and how, your first recipe and where it came from, and your first payment with its product and price. They come with your device model, iOS or Android version, language, time zone, App Store or Google Play country and the region found from your IP address, under a random app ID and, on iPhone, the ID iOS gives our apps on your device (IDFV). On Android, Google Analytics also learns from Google Play which link you installed ClickDish from, if any. Adapty then sends Google Analytics each payment, renewals included, and each refund, with its product, amount and currency, under the same app ID. The app gives Adapty that ID only while it may share with Google, as described below. Google Ads uses all of this to measure our Google ads, and, on iPhone, Google Analytics sets the value that Apple’s SKAdNetwork reports to ad networks without saying who you are. To check on your iPhone whether one of our Google ads brought you, Google uses de-identified, temporary data such as your IP address and the time of an event, never your email.
- Meta SDK sends Meta these steps: installing and opening ClickDish, creating an account and how, your first recipe and where it came from, and your first payment with its product and price. They come with Meta’s anonymous ID, your device model, iOS or Android version, language, time zone and screen size, your IP address and the link that opened ClickDish, if any, so Meta can tell whether you came from its ad. Adapty then sends Meta your renewals and refunds, with their product and amount, under Meta’s anonymous ID, which the app gives Adapty only while the Meta SDK runs. Meta never gets your email or phone number, and the SDK records no other steps on its own. On iPhone, without tracking permission, Meta measures our ads in aggregate, through its Aggregated Event Measurement.
- Apple Ads. If you installed ClickDish on iPhone after tapping an Apple Ads ad, iOS gives the app a token. After you sign in, our server uses it to get from Apple the ad, its campaign, ad group and keyword, your country and the date of the tap, and keeps them with your account. Adapty receives the same token and gets the same answer from Apple. This needs no tracking permission.
If your App Store or Google Play country is in the European Economic Area, the United Kingdom or Switzerland, or the store doesn’t say which it is, ClickDish asks after you sign in whether to share how you use it with Google and Meta, and sends them nothing until you answer. If you don’t allow it, Google Analytics gets these steps without any identifier, Meta gets nothing, and Adapty sends neither of them anything. You can change your answer at any time in Account › Share with Google and Meta. In other countries, the app sends these steps from the start.
Google and Meta never receive your recipes, allergens, nutrition targets or email.
On iPhone, right after you sign in, iOS asks whether ClickDish may track you; in the European Economic Area, the United Kingdom and Switzerland, it asks only if you allowed sharing with Google and Meta. Your device’s advertising identifier (IDFA) reaches Google and Meta only if you allow tracking. You can change your answer in Settings › Privacy & Security › Tracking.
On Android, there is no such question. In the European Economic Area, the United Kingdom, Switzerland, or where Google Play doesn’t say your country, Google Analytics and the Meta SDK read your device’s advertising ID only after you allow sharing with Google and Meta; everywhere else, from the start. ClickDish itself never reads it. You can reset or delete it in Android’s settings, under Ads.
Links you share
When you share a recipe, anyone with the link can open its page on clickdish.net. The page shows the recipe’s title, cover, ingredients, steps and nutrition, and the original’s author and link. It doesn’t show your name, email, notes or rating, and it tells search engines not to index it. The page sets no cookies and has no ads. When it is opened from a blogger’s post link, our server counts the visit and any tap on its App Store or Google Play button for that post.
When you share a collection, anyone with its link sees the collection, its recipes and your name from Account. People who follow a public collection see your changes as you make them, but not your notes or ratings. In a collection with shared access, members add their own recipes, and everyone in it sees each recipe with the note and rating of the person who added it, but not who that person is or whether they marked it as a favorite. Nobody sees who follows a collection or who joined it.
A gift link shows your name from Account to whoever opens it.
Stop sharing closes a link for everyone at once, and your collections also stop being shared when your Premium ends. Copies people already saved to their own books stay there, covers included, and recipes members added stay in the collection. A recipe you added to someone else’s collection stays there after you leave, until you delete it from your book.
Where your data is kept
Your recipe book is stored in Frankfurt, and our server is in Germany. The other services above may process data in the United States and other countries. Transfers out of the European Economic Area, the United Kingdom and Switzerland rely on an adequacy decision or on standard contractual clauses.
How long we keep data
| Data | How long |
|---|---|
| Account, recipe book, settings, allergens and targets | Until you delete your account. Recipes, collections and plan entries you delete disappear from your devices; our copy stays marked as deleted until you delete your account. |
| Smart plan answers | With that week’s plan, until you delete your account. |
| Videos downloaded for a recipe | Deleted when the recipe is ready or the save fails. |
| Photos you send for a recipe | Deleted when the save ends. The first one stays as the recipe’s cover. |
| Photos of your fridge or shelf, and of receipts on Android | Not kept after they are read. |
| Records of your free imports and saves, cookies and gifts | Until you delete your account. |
| Our analytics events | 90 days. |
| Our analytics: where you came from, your first steps and your payments | Until you delete your account. |
| Your last IP address, with its country and city | Until you delete your account. |
| Our analytics for an install that never signed in, with the country and city of its last IP | 180 days after its last event. |
| Which days you opened ClickDish and how many times, and daily totals of our analytics with no IDs, including what people searched for in Discover | 14 months. |
| Reports by you or about your collections and recipes, and the authors whose content you hid | Until you delete your account. |
| Recipes made from public links | Kept with no link to you, so the next person who saves the same link gets the recipe at once. They stay after you delete your account. |
| Usage data in Google Analytics | Up to 14 months. |
| Purchase records | As long as tax and accounting law requires. |
| Support emails | Up to two years after the conversation ends. |
The services above keep the data they receive under their own policies.
Delete your account
In ClickDish, open Account, tap Delete account and confirm. We immediately erase your account, recipe book, photos, profile, plans, shared links, reports, cookies, gifted Premium, records of your saves, your last IP address and our analytics about you from our server and from Firebase; our analytics keeps only daily totals with no IDs. Our own backups keep a copy for about a week, and copies in Google’s backup systems are deleted on the schedule described in Firebase’s privacy information. Recipes that other people saved from your links stay in their books, covers included.
We also delete your profile at Adapty. The purchase history it held stays there with no link to your account, and moves to the next account that buys or restores with the same Apple ID or Google account. Deletion doesn’t reach usage data in Google Analytics, which expires within 14 months, events the Meta SDK and Adapty sent to Meta, or purchase records at Apple and Google Play. To have the Google Analytics records deleted sooner, write to us.
Deleting your account doesn’t cancel a subscription with Apple or Google Play. If you have one, ClickDish warns you before deleting and offers Manage subscription; you can also cancel it on iPhone in Settings › your name › Subscriptions, or on Android in Google Play › your profile icon › Payments & subscriptions › Subscriptions.
If you can’t open the app, email [email protected] from your account’s email address and say whether you sign in with Apple or Google.
Why we can use your data
- To run ClickDish for you: your account, recipe book, recipes, plans, sharing, purchases and gifts. Legal basis: our contract with you, the Terms of use.
- To use your allergens and nutrition targets. Legal basis: your explicit consent.
- To send notifications. Legal basis: your consent where your phone asks for it, otherwise our legitimate interest. You can turn them off at any time in your phone’s settings.
- To see how ClickDish is used and which of our ads work, with our own analytics, the Google Play install referrer, Google Analytics, the Meta SDK and Apple Ads attribution. Legal basis: for Google and Meta, your consent in the European Economic Area, the United Kingdom and Switzerland and our legitimate interest elsewhere; for our own analytics, the install referrer and Apple Ads attribution, our legitimate interest.
- To fix errors, keep ClickDish safe and secure, handle reports, control its costs and answer your messages. Legal basis: our legitimate interest.
- To keep purchase records required by tax law. Legal basis: legal obligation.
Your rights
Depending on where you live, including under the GDPR, the UK GDPR and California law, you can ask us to give you a copy of your data, correct it, delete it, restrict or object to its use, or send it to you in a portable format. You can withdraw your consent at any time.
Write to [email protected]. We answer within 30 days and don’t treat you differently for using these rights. In the European Economic Area or the United Kingdom, you can also complain to your data protection authority.
Children
ClickDish isn’t directed at children under 13, or under 16 in the European Economic Area, and we don’t knowingly collect their data. If you believe a child has given us data, write to [email protected] and we’ll delete it.
Changes
When this policy changes, we update the date at the top of this page.
Contact
RIOLD LLC, 1800 Cold Stream Ct. Apt. 205, Asheville, NC 28803, United States. Email: [email protected].