Privacy Policy

Last updated: May 27, 2026

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 content returned from the extraction service, such as titles, ingredients, steps, and timing.
• Recipes, edits, and personal notes you choose to save locally on your device for later viewing.
• 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 and subscription status returned by RevenueCat, Apple App Store, or Google Play, such as whether a LinkDish Plus or Family entitlement is active.
• If you sign in for 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.

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.
• Personal saved recipes are stored on your device so you can reopen them later inside the app.
• 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.
• 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 in-app purchase offerings, purchases, restores, and entitlement checks. Purchases are processed by Apple App Store or Google Play through RevenueCat. 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 to import and save recipes on one device.
• Sign in is required only for Family household sharing.
• LinkDish does not sell your personal information.
• LinkDish does not include third-party advertising in the current app.

Data storage

Personal recipes you save in the app are stored locally on your device. 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. Account sessions are stored on your device in secure storage. Server-side account, session, external sign-in identity, invite, household, and shared recipe records are stored by LinkDish's backend. iOS notification list records are stored by LinkDish's backend.

Your choices

You can stop using the extraction service at any time by not submitting links, 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, cancel, or restore subscriptions through the App Store or Google Play account used to make the purchase. Restoring purchases asks RevenueCat to check that store account for active LinkDish paid plan access.

If you create a LinkDish account, you can delete it from Account in the app. Account deletion removes server-side account, household, and shared Family recipe records that belong to the account, but it does not cancel App Store or Google Play 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 robertgordon761@gmail.com.

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.