Privacy Policy

1. Who we are

Reelish (the “app”, the website at reelish.app, and related services, together the “Service”) is provided by [COMPANY LEGAL NAME], [ADDRESS] (“we”, “us”). For the purposes of the EU and UK General Data Protection Regulation (“GDPR”), we are the controller of the personal data described in this policy.

Questions or requests: [CONTACT EMAIL].

[If required: Our representative in the European Union is [EU REPRESENTATIVE NAME AND ADDRESS]. Our representative in the United Kingdom is [UK REPRESENTATIVE NAME AND ADDRESS].]

2. What we collect

Account information

• Anonymous account ID. When you first open the app we create a random identifier so your library works without sign-up.
• Sign in with Apple (optional). If you choose it, Apple gives us a stable user identifier and, if you allow it, your name and email address. If you pick “Hide My Email”, we receive an Apple relay address instead of your real one.

Your recipes and content

• Recipes in your library (imported or written by you), edits, personal notes, favorites, collections, grocery lists and settings such as preferred language, units and servings.
• The links you import and their status (for example “queued” or “ready”).

Purchases

• If you subscribe, Apple processes the payment. We and RevenueCat receive transaction details such as the product, price, currency, purchase and renewal dates, trial status and an anonymous app user ID. We never receive your payment card details.

Device, usage and diagnostic information

• Device model, iOS version, app version, language and region settings, and a push notification token if you allow notifications.
• In-app events such as “import started”, “recipe opened”, “paywall viewed” or “trial started”, linked to your anonymous account ID. We use these first-party events to understand and improve the app, not for advertising.
• Technical logs from our servers, including IP address, request times and error details, and crash reports. [CONFIRM: name your crash-reporting tool in section 6, or remove “crash reports”.]

Support communications

• If you email us, we keep your email address and the conversation so we can help you.

What we don’t collect

• We don’t use advertising identifiers (IDFA), don’t show the App Tracking Transparency prompt, and don’t include ad or data-broker SDKs.
• We don’t access your contacts, photos, camera, microphone or precise location.
• We don’t read anything in other apps. The share extension only receives the link you choose to share.

3. How we process video links

When you share or paste a link, the app sends us only the URL. Our servers then:

1. Resolve the link to identify the platform and the public video.
2. Read the publicly available caption, title and description.
3. Listen, if the recipe isn’t complete in the caption: we fetch a temporary copy of the audio track and transcribe it.
4. Watch, if it’s still incomplete: we sample a small number of still frames to read on-screen text.
5. Write a structured recipe and save it with a thumbnail image and a link back to the original post.

Temporary audio and frame files are deleted as soon as processing finishes, and in any case within [24 HOURS]. We do not store or redistribute the videos themselves. We only process content that is publicly accessible at the link; private posts cannot be imported.

Shared cache. If someone has already imported the same public video, we may reuse the recipe created for it so your import is instant. Cached recipes are tied to the public video, not to the person who imported it, and no user can see who else imported a video.

The captions, transcripts and frames we process can include information about the video’s creator (for example their public handle or voice). We use it only to create the recipe and credit the creator, and we link back to the original post.

4. How we use information, and our legal bases

We do not use your information for targeted advertising, and we do not make decisions that produce legal or similarly significant effects about you based solely on automated processing.

5. AI processing

Reelish uses third-party AI models to transcribe audio, read on-screen text and write recipes. For each import we send these providers the material needed for that step — the source link, caption text, transcript and/or sampled frames — and, where relevant, your preferred recipe language. We do not send your name, email address or Apple ID.

These providers act as our processors (service providers). Under our agreements with them they may use the data only to provide their service to us and [CONFIRM: are not permitted to use it to train their models / retain it for no longer than [X] days for abuse monitoring]. We do not use your personal library to train AI models.

AI output can be wrong. Always check recipes, especially quantities, cooking temperatures and allergens. Nutrition figures are estimates.

6. Who we share information with

We share information only with service providers who help us run Reelish, under contracts that require them to protect it and use it only on our instructions:

We may also disclose information if required by law, to protect the rights, safety or property of our users or others, or as part of a merger, acquisition or sale of assets (in which case this policy will continue to apply to your information, or you’ll be notified).

We do not sell your personal information, and we do not “share” it for cross-context behavioral advertising as those terms are defined under California law.

To fetch public video information we send requests to the platform that hosts the video (for example TikTok, Instagram, YouTube, Facebook or Pinterest). These requests come from our servers, not from your device, and do not include your identity.

7. International transfers

We are based in [COUNTRY] and our providers may process data in the United States and other countries. When we transfer personal data out of the EU, EEA, UK or Switzerland, we rely on adequacy decisions (including the EU–US Data Privacy Framework where the recipient is certified) or the European Commission’s Standard Contractual Clauses and the UK Addendum, together with appropriate safeguards. Contact us for a copy of the relevant safeguards.

8. How long we keep information

9. Your rights and choices

Everyone

• Notifications: turn them off any time in iOS Settings → Notifications → Reelish.
• Edit or delete content: edit or delete any recipe, note or list in the app.
• Delete your account: see section 10.
• Get a copy of your data: email us and we’ll send an export of your account data.

EU, EEA, UK and Swiss residents

You have the right to access, correct, delete, restrict or port your personal data, to object to processing based on legitimate interests, and to withdraw consent at any time (without affecting processing before withdrawal). You also have the right to lodge a complaint with your local data protection authority. We’ll respond within one month.

US state privacy rights (including California)

Depending on where you live, you may have the right to know what personal information we collect and how we use it, to access, correct and delete it, and to opt out of its sale, sharing for targeted advertising, or profiling. We don’t sell or share personal information for targeted advertising and don’t use it for profiling with legal effects, so there is nothing to opt out of. We will not discriminate against you for exercising your rights. You may use an authorized agent; we may need to verify your request. If we deny a request, you can appeal by replying to our decision.

To make any request, email [CONTACT EMAIL] from the address linked to your account, or include your in-app account ID (Settings → Account) [CONFIRM: path in app].

10. Deleting your account

In the app, open Settings → Account → Delete Account [CONFIRM: path in app]. This permanently deletes your account, library, notes, collections, grocery lists and settings from our active systems right away, and from backups within [35 DAYS]. Purchase records we must keep for legal reasons are retained as described above. Deleting your account does not cancel an Apple subscription — cancel it in iOS Settings first. If you used Sign in with Apple, you can also stop using Apple ID with Reelish in iOS Settings → [your name] → Sign-In & Security → Sign in with Apple.

11. Shared recipe links

If you use “Share recipe”, we create a web page at a link you can send to others. The page shows the recipe (title, ingredients, steps, photo) and credits the original creator with a link to their post. It doesn’t show your name or email. Anyone with the link can view it. [CONFIRM: Deleting the recipe from your library removes its shared page.]

12. Children

Reelish is not directed to children under 13 (or the minimum age of digital consent in your country, such as 16 in parts of the EU), and we don’t knowingly collect their personal information. If you believe a child has given us personal information, contact us and we’ll delete it.

13. Security

We encrypt data in transit (HTTPS/TLS) and at rest, restrict access to people who need it, and use providers with recognized security practices. No system is perfectly secure; if a breach affects your personal information, we will notify you and the authorities as required by law.

14. Changes to this policy

We may update this policy as Reelish changes. We’ll update the effective date above, and for material changes we’ll tell you in the app or by email before they take effect.

15. Contact us

[COMPANY LEGAL NAME]
[ADDRESS]
Email: [CONTACT EMAIL]