LinkDish helps you turn recipe links into a clean, readable recipe format. This page explains what information the app handles and how it is used.
Information LinkDish handles
- Recipe links that you paste into the app so the service can extract recipe information.
- Recipe photos or camera captures you choose to submit for image-based recipe scanning.
- Recipe content returned from the extraction service, such as titles, ingredients, steps, and timing.
- Recipes, edits, and personal notes you choose to save. Free includes up to 15 personal saved recipes; paid plans include unlimited personal saves.
- Recipes, edits, and personal notes you choose to add to a shared Family recipe book, including the account email shown as the recipe owner.
- Source page text, metadata, and video transcript details needed to extract recipe information, including when LinkDish uses configured fallback processing for difficult links.
- An app-generated RevenueCat app user ID used to load purchase options, restore purchases, and verify LinkDish paid plan entitlement status.
- Purchase, subscription, and lifetime-access status returned by RevenueCat, Apple App Store, Google Play, or RevenueCat Web Billing, such as whether a LinkDish Plus, Family, or Founding entitlement is active.
- If you sign in for plan access or Family household sharing, your account email, login code/session records or social sign-in identity details, household membership, and household invite records.
- If you join the iOS notification list, the email address you submit and basic request details needed to prevent abuse.
- First-party analytics events such as page or screen views, app opens, feature actions, extraction outcomes, source hostnames, app version, session identifiers, and sanitized error summaries.
- In the Android app, crash and error reports sent to Sentry when the app crashes or stops responding: the error and where in the app code it happened, recent app events, the app version, and the device model and operating system version. LinkDish does not attach your account details to these reports, leaves out console logs, and removes query strings from web addresses in them.
- On the linkdish.ca website only, page-view statistics collected by Plausible Analytics: the page visited, the referring site, browser, operating system, device type, and country. Plausible does not set cookies and, according to its data policy, does not store IP addresses.
How the information is used
- Submitted links are sent to LinkDish's backend service to fetch and extract recipe details.
- Difficult links may be processed by LinkDish's configured extraction providers to recover missing recipe details. This is used only to provide recipe extraction, not for advertising.
- Submitted recipe images may be processed by LinkDish's backend and configured extraction providers to turn paper recipes, recipe cards, or cookbook pages into structured recipe details.
- Personal saved recipes are stored on your device so you can reopen them later inside the app. When you're signed in, your cookbook (saved recipes with your notes, favorites, tags, ratings, collections, and cook log) is also stored by LinkDish's backend with your account so it stays in sync on every device where you sign in. Photos you scanned to import a recipe stay on the device. Free accounts can keep up to 15 personal recipes on a device; paid plans remove that save limit.
- Shared Family recipes are stored by LinkDish's backend so active household members can view them, duplicate them, and see who added them.
- The app-generated purchase ID is sent to RevenueCat and to LinkDish's backend service so LinkDish can check entitlement status and apply the correct import and extraction limits.
- Basic server-side operational logs may be used to monitor reliability, prevent abuse, and debug failures.
- Analytics are used to understand whether LinkDish is working across the website, web app, Android app, and backend, including extraction success rates, source hostnames, performance problems, and errors.
- Account and household records are used only to sign you in, manage Family household membership, send login or invite emails through LinkDish's email provider, verify Google/Apple sign-in through LinkDish's configured authentication provider, and apply the shared Family quota.
- iOS notification list emails are used only to send LinkDish iOS availability updates and maintain the list.
Purchases
LinkDish uses RevenueCat to manage purchase offerings, purchases, restores, customer-portal access, and entitlement checks. Mobile purchases are processed by Apple App Store or Google Play through RevenueCat. Web subscriptions and the one-time Founding offer are processed through RevenueCat Web Billing and its payment processor. LinkDish does not receive your full payment card number or payment account credentials.
Authentication providers
LinkDish may use Clerk to support Google and Apple sign-in. When that sign-in option is enabled, Clerk handles the authentication flow and provides LinkDish with a verified account identifier and email address so LinkDish can connect the sign-in to a LinkDish account. LinkDish keeps its own account ID for saved recipes, Family households, quotas, and account deletion.
What LinkDish does not do
- No account is required for the first 3 free recipe imports.
- Sign in is required to buy or restore a plan and for Family household sharing.
- LinkDish does not sell your personal information.
- LinkDish does not include third-party advertising in the current app.
- LinkDish analytics do not store full recipe URLs, recipe titles, ingredients, instructions, uploaded recipe images, raw page text, or LLM prompts.
Data storage
Personal recipes you save are stored locally on your device and, when you're signed in, with your account on LinkDish's backend so they sync between your devices. Shared Family recipes and their notes are stored by LinkDish's backend for household access. Extracted recipe data may also pass through LinkDish's backend service in order to produce results and keep the service running reliably. The RevenueCat app user ID is stored on your device and may be stored by LinkDish's backend for quota checks and by RevenueCat for purchase and entitlement management. Mobile session tokens use operating-system-backed secure storage; the web app uses browser storage needed to keep you signed in. Server-side account, session, external sign-in identity, synced cookbook, invite, household, and shared recipe records are stored by LinkDish's backend. iOS notification list records are stored by LinkDish's backend. First-party analytics records are stored by LinkDish's backend using anonymous or hashed identifiers. Android crash reports are processed and stored by Sentry. Website page-view statistics are processed and stored in aggregate by Plausible Analytics.
Your choices
You can stop using the extraction service at any time by not submitting links or recipe images, and you can remove personal saved recipes from inside the app whenever you want. You can unshare recipes you added to a Family recipe book from the shared recipe controls.
You can manage or restore access from LinkDish's Plans screen. Store subscriptions are managed through the App Store or Google Play account used to make the purchase; web subscriptions are managed through the RevenueCat customer portal opened from LinkDish. Founding access is a one-time purchase and does not renew.
If you create a LinkDish account, you can delete it from Account in the app. Account deletion removes server-side account, synced cookbook, household, and shared Family recipe records that belong to the account, and the analytics records linked to the account, but it does not cancel App Store, Google Play, or web subscriptions. Local saved recipes remain on your device.
If you joined the iOS notification list and want to be removed, or if you cannot access the app and need help with deletion of data retained by LinkDish, email support@linkdish.ca.
Questions
If you have questions about privacy or support, use the support contact listed on the app's store listing or visit the LinkDish support page.