Reels to RecipesYour personal cookbook

Privacy & your recipes

For Reels to Recipes support, privacy questions, or help with data-deletion requests, email onlinesalesaz1@gmail.com. Our support team monitors this address.

Waiting for an email reply? Check your Spam or Junk folder if the email isn't in your inbox.

Native inbox and online kitchen

Links and text saved to the native share inbox are stored on your device. The online kitchen is a separate collection. Opening the website does not make your collection public.

The online kitchen stores recipe text, source links, categories, shopping lists, and meal plans in Cloudflare D1, and uploaded screenshots, photos, and videos in Cloudflare R2. Your browser also stores a local copy in IndexedDB. The offline app cache holds app files, not cloud API responses. A signed-in or temporary guest identifier associates the cloud collection with its user.

Browser trials

The seven-day website trial requires no account or card. A secure cookie identifies the browser session for up to 30 days. Clearing cookies, changing browser, or letting the browser session expire can prevent access to that collection. Creating a new account in the same browser keeps its recipes, attachments and original trial deadline. Signing in to an existing account keeps collections separate; export a trial backup first and restore it in your account. Export a backup of recipes you want to keep. Session expiry ends access; it does not itself establish deletion of stored records.

Usage limits

The service stores daily counts of import and audio-extraction requests associated with a derived collection identifier, together with aggregate daily counters. These records enforce usage limits and protect service capacity.

Imports and optional processing

Website imports contact the source website. Loading a source image or video player may disclose your IP address and ordinary request information to that source, which applies its own privacy policy. Screenshot text recognition runs on the device using recognition software downloaded from a third-party content-delivery service.

With your permission, optional audio extraction sends the selected video/audio and supplied caption to OpenAI for transcription and recipe organization. You can withdraw that permission through Account & privacy. Do not upload sensitive personal information unnecessary for a recipe. When you share or export text, the receiving app or person receives the information you select.

Website purchases

Website checkout, when enabled, uses Stripe. We retain an account-linked checkout reference, payment status, and payment-event identifiers to verify website access and process refunds or disputes. Card details are handled by Stripe and are not stored in the recipe database. Sandbox purchases do not grant live paid access. Payment records remain separate from cookbook deletion so purchases can be reconciled; contact support for payment-record requests.

Website access records also include your trial start time and, if redeemed, a hash of your family code, its redemption time, and the associated account identifier. These records prevent repeated trials and reuse of a family code across accounts. They remain separate from cookbook deletion; contact support for access-record requests.

Apple purchases

The native app uses Apple's purchase and restoration services to determine Trial or Permanent Unlock access. Apple handles billing information; Reels to Recipes does not ask you to enter payment-card details. In version 1.0.2, the app can send an Apple-verified transaction reference to the signed-in website. The server verifies it with Apple and stores its original transaction identifier, account identifier, product, purchase date, environment and verification status to determine access. A purchase already linked to one account cannot silently be reassigned to another. Sandbox receipts are stored separately by environment and do not grant permanent production access. Purchase and access records remain separate from cookbook deletion; contact support for related requests.

Email sign-in

Signing in sends your email address and a one-time code to the first-party account service. The service keeps account identifiers, hashed code and session records, expiration times and security usage counters. Email delivery uses the configured sending provider. Website session cookies are Secure and HttpOnly. Check your Spam or Junk folder if the email isn't in your inbox. The expected code sender is signin@reelstorecipes.com.

Providers and security

The online kitchen uses ChatGPT Sites hosting with Cloudflare-backed storage. A specific storage country or US-only processing is not guaranteed. Access checks separate collections and attachments by user identity. People who can use your unlocked browser or device may access its local data.

Retention and deletion

Use Account & privacy to export your cookbook, withdraw audio-processing permission, or delete the current cloud collection and uploaded attachments. Continue until deletion is reported complete. A minimal empty collection and revision record is retained to stop older devices from recreating deleted recipes.

Collection deletion clears that collection's audio-extraction quota records. It does not currently also clear guest-import quota or guest-session records. Older daily usage rows are cleaned up when a later successful audio-extraction quota check runs; there is no guaranteed cleanup interval. Provider operational records and backups follow the applicable providers' retention rules; a configured duration and immediate erasure from every log or backup have not been verified.

Cookbook deletion does not delete an external ChatGPT account, exported backups, or other devices' copies. Native inbox items have separate deletion controls. See deletion instructions, or contact the address above if you cannot access the original collection. Do not send passwords or tokens.

Updated November 19, 2026 for the version 1.0.2 account and kitchen flow.