Reelish

Privacy Policy

Last updated: July 17, 2026

Reelish imports Instagram reels and posts that you choose to share to the app so it can extract recipe details, create recipe cards, and build grocery lists.

Data Processed By Reelish

• Instagram source URLs and shared text or captions that you send to Reelish.
• Public reel/post metadata returned by the provider, such as captions, thumbnail URLs, media URLs when available, and transcript text when available.
• Recipe text generated from those shares, including ingredients, steps, parser confidence, and warnings.
• Anonymous Firebase authentication identifiers used to call the recipe parser.
• Signed-in Firebase account identifiers and email addresses if you create or sign in to an account for sync.
• Purchase and entitlement status processed by Google Play Billing and RevenueCat.
• Basic technical logs needed to operate and secure the Firebase parser.
• When parser-improvement diagnostics are enabled, failed or partial parses may retain the normalized public Instagram URL and structured outcome details such as parser version, route, confidence, reason codes, and ingredient or step counts. These review records do not contain your Firebase user ID, email address, captions, transcripts, recipe text, raw model responses, or media files and are scheduled to expire after 30 days.
• Meta App Events advertising and attribution data, including app installs, app activations, app sessions, purchase events, device/app information, and the Android advertising identifier when available. Reelish does not send recipe text, social source URLs, captions, grocery text, email addresses, or payment-card details to Meta.
• TikTok App Events advertising and attribution data, including app installs, app launches, second-day retention, device/app information, and the Android advertising identifier when available. TikTok purchase auto-tracking is disabled. Reelish does not send recipe text, social source URLs, captions, grocery text, email addresses, or payment-card details to TikTok.

Data Stored On Device

Saved recipes, selected recipes, grocery lists, scan records, and widget content are stored locally on your device. Reelish disables Android cloud backup for this local app data. Signed-in accounts use a memory-only Firestore cache. When an account is removed from the device, Reelish also clears account-derived local records, sync metadata, pending scan work and images, image caches, and grocery widget content.

Optional Account Sync

Guest mode remains local-first. If you create an account, you can add the current guest workspace to it. If you sign in to an existing account while guest data is present, Reelish asks whether to add the device data, use the account's cloud data instead, or cancel. Sync does not begin until you choose. Signed-in sync copies saved recipes, scan records, selected recipes, and grocery checked state to Firebase so your app data can sync across your devices.

Data Sent To Service Providers

• Firebase receives parser requests and authentication identifiers.
• Firebase stores account sync data for signed-in users, including saved recipes, scan records, selected recipes, and grocery checked state.
• Firebase may temporarily store the limited parser-review records described above so Reelish can reproduce failures and improve extraction quality.
• Apify may receive Instagram source URLs to retrieve public reel or post evidence.
• OpenAI may receive recipe evidence text, provider thumbnails, and provider media/audio when available so Reelish can transcribe and extract structured recipe details.
• RevenueCat and Google Play process purchase and subscription status.
• Meta receives limited app event and device information to measure ad-driven installs, prevent ad fraud, and improve advertising delivery.
• TikTok receives limited app event and device information to measure ad-driven installs, prevent ad fraud, and improve advertising delivery.

User Controls

Guest users can clear local app data in Reelish settings. Normal signed-in sign-out first syncs completed changes, then removes account data, caches, pending work, and widget content from that device and switches billing to guest. The cloud copy remains available. If the final sync fails, including while offline, Reelish keeps the account signed in and clears nothing. A separately confirmed sign-out without syncing may lose unsynced local changes, but does not delete the existing cloud copy.

Signed-in users can delete their Reelish account and synced cloud data from Settings, then Manage account, then Delete account and data. After backend deletion succeeds, Reelish performs the same complete device purge. Guest parser requests may create anonymous Firebase and quota identifiers for app functionality and abuse prevention; these do not expose an in-app account deletion control because they are not email-backed accounts. Backend parser logs and anonymous parser identifiers are handled through operational retention and support-assisted deletion where verification is possible. For support and backend-associated deletion requests, use the support contact published with the Google Play listing or the support instructions at Reelish support.

Reelish is not affiliated with Instagram, TikTok, Meta, or ByteDance.