Privacy Policy

Effective Date: October 29, 2025 | Last Updated: October 4, 2026

Stitched Strategy LLC ("Company," "we," "us," or "our") operates the Cookie mobile application for iOS and Android (the "App"). This Privacy Policy explains what information we collect, how we use it, how we share it, and the choices available to you.

1. Information We Collect

1.1 Audio and Voice Transcriptions

iOS: When you use voice commands, audio is processed through Apple's speech recognition services and returned to the App as text.

Android: Cookie listens for its wake word, "Hey Cookie", using a detection model that runs on your phone, while you are on the cooking screen. The audio used to detect the wake word is processed on your phone and is not sent to us or to anyone else. The detection software briefly saves a short audio clip around each detection in the App's private storage on your phone; the App deletes these clips automatically within seconds. After the wake word, the audio of your command is processed by Android's speech recognition service, which is provided by Google and, depending on your device and settings, may process audio on the device or send it to Google's servers (see Section 3.1). For a short time after Cookie speaks a response, it may listen for a follow-up command without needing the wake word again.

On both platforms, we do not store raw voice audio on our own servers. Voice transcriptions are processed in the App and, for AI features, the text of your question (not your voice) may be sent to Google's Gemini service as described in Section 3.

1.2 Usage Data and Diagnostics

We use Firebase Analytics and Firebase Crashlytics to collect usage and diagnostics data such as feature interactions, session events, crash signals, and performance metrics. For users without an account, this data is associated with device and app identifiers. For users with an account, analytics and crash reports are linked to your Firebase user ID. Crash reports also include technical details such as your device model and operating system version. On Android, the App does not use the Android advertising ID.

1.3 Account Information (Optional)

If you create an account, we collect:

  • Email address: Used for passwordless sign-in via magic link
  • Authentication credentials/tokens: Managed by Firebase Authentication to keep you signed in
  • User ID: Assigned by Firebase to associate your app data with your account

Before you create an account, the App automatically assigns an anonymous Firebase session identifier to your device. This identifier is used only to associate your local data with app sessions and is replaced with your account-linked user ID when you sign in.

If you subscribe to Premium, or have been given Premium access (for example through a partner or a gift), we also store your subscription status in your account profile: whether Premium is active, the plan, the expiry date, the source of access, and the time of your last purchase. We may check your email address against our records of partner and gifted access to determine whether you have Premium.

Account creation is optional. You can use core app functionality without creating an account.

1.4 User Content

If you import recipe URLs, the App processes recipe-related content such as titles, ingredients, instructions, and images. For users without an account, this data is stored locally on the device. For users with an account, recipe data is synced to Firebase Firestore for backup and multi-device access.

Photos you take or choose in the App are stored locally on your device unless and until cloud sync for those photos is explicitly offered and enabled. If you import a recipe from a photo, the photo is sent to Google's Gemini service to read the recipe text (see Section 3.6). Recipe photos are deleted from your device when you delete the recipe or your data.

1.5 Device and App Data

We use standard iOS and Android APIs and local storage for app preferences, cached files, and operational metadata (such as file timestamps used for cache management). On Android, the App asks for permission to use the microphone (voice control), the camera (recipe photos) and notifications (timer alerts). Timer alerts are scheduled on your device; we do not send push notifications from our servers.

1.6 Feedback Submissions

If you submit in-app feedback, we collect your feedback text along with technical context: device model, operating system version (iOS or Android), app version and build number, premium subscription status, and approximate recipe count. You may optionally provide your email address to receive a reply. This data is stored in Firebase Firestore and is accessible only to the Company.

2. How We Use Information

We use information to:

  • Provide and maintain app functionality, including voice control and recipe management
  • Authenticate users and manage account access
  • Sync and back up account-linked recipe data across devices
  • Measure reliability and improve product features
  • Provide AI-assisted features (available with Premium and, within the free-tier allowance, to free users) and, where enabled, cloud text-to-speech
  • Verify purchases and subscriptions and give you the access you have paid for
  • Send you the sign-in email you request, and marketing email only if you opt in
  • Detect, investigate, and address security or technical issues

3. Third-Party Services and Processing

3.1 Speech Recognition

iOS: Voice input uses Apple's speech recognition framework and related Apple processing infrastructure. Apple may process audio according to Apple's terms and privacy disclosures.

Android: Voice commands are processed by Android's speech recognition service, which is provided by Google. Depending on your phone and its settings, audio may be processed on the device or sent to Google. Privacy information: https://policies.google.com/privacy. The "Hey Cookie" wake word is detected on your phone by an on-device model from a third-party software library (DaVoice); audio used for wake-word detection stays on your phone.

3.2 Firebase Authentication (Google)

We use Firebase Authentication for sign-in and session management. For account users, email and authentication metadata are processed by Google. Privacy information: https://policies.google.com/privacy.

3.3 Firebase Firestore (Google Cloud)

For account users, recipe and account-linked app data are stored in Firebase Firestore. We also use Firebase Cloud Functions to send sign-in emails, check gifted access, and verify purchases. Data may be processed in the United States and other jurisdictions where Google or its subprocessors operate.

3.4 Firebase Analytics (Google)

We use Firebase Analytics for product usage and performance insights. Privacy information: https://policies.google.com/privacy.

3.5 Third-Party Recipe Websites

When you import a recipe URL, the App requests content from the source website. Your use of those websites is subject to their own terms and privacy policies.

3.6 Google Gemini API

Google's Gemini API is used in these ways: (1) as a fallback when on-device recipe extraction fails, in which case recipe page text may be sent to Gemini for any user, including those without a Premium subscription; (2) to read recipes from photos, pasted text or social-media posts you import, in which case the photo or text you provide is sent to Gemini; and (3) for AI cooking features, where recipe content and your questions are sent to Gemini to generate cooking guidance, scaling calculations, and similar responses. AI features are available with Premium and, within the free-tier allowance, to free users. The titles of recipes in your library may also be sent to Gemini to generate the recipe suggestions shown on the Home screen. Raw voice audio is not sent to Gemini by us; only the text of your question is.

3.7 Google Cloud Text-to-Speech (Premium)

Where Premium cloud voice is enabled, output text is sent to Google Cloud Text-to-Speech to generate audio. Otherwise, spoken responses use your device's built-in text-to-speech (Apple's on iOS, the phone's own text-to-speech engine on Android), and the text stays on your device.

3.8 Brevo (Email Marketing)

We use Brevo (formerly Sendinblue) to send email. When you ask to sign in, your email address and your one-time sign-in link are sent through Brevo to deliver that email. If you also opt in to marketing communications during sign-up, your email address is added to our Brevo marketing list solely to send you product updates and announcements. We do not add your email address to the marketing list unless you explicitly opt in. You can unsubscribe at any time via any marketing email or by contacting us. Privacy information: https://www.brevo.com/legal/privacypolicy/.

3.9 Recipe Search

When you search for recipes within the App, your search query is sent to a search provider to retrieve results: Google's Custom Search API on iOS (https://policies.google.com/privacy) and Brave Search on Android (https://brave.com/privacy/).

3.10 Purchases and Subscriptions

Premium subscriptions are sold and billed by Apple on iOS and by Google Play on Android; we do not receive your payment card details. On Android, after a purchase the App sends the purchase token to our server, which checks it with the Google Play Developer API to confirm your subscription, and Google Play sends us notifications about renewals, cancellations and refunds. Your subscription status is stored in your account profile (see Section 1.3). Privacy information: https://policies.google.com/privacy.

3.11 Firebase App Check and Google Play Integrity (Android)

On Android, we use Firebase App Check with Google Play Integrity to help confirm that requests to our services come from a genuine, unmodified copy of the App on a genuine device. This involves Google processing device and app integrity signals. Privacy information: https://policies.google.com/privacy.

4. Data Storage and Retention

4.1 Local Storage

Recipe data, preferences, and caches are stored on your device. Voice audio is processed for recognition and is not stored by us as raw recordings on our servers. On Android, short clips saved by the wake-word detection software are deleted from your phone automatically within seconds.

4.2 Cloud Storage (Account Users)

If you create an account, account-linked data is stored in Firebase services. We retain this data while your account remains active and as needed for legitimate business and legal purposes.

4.3 Account and Data Deletion (Delete Your Account)

This section explains how to delete your Cookie account and data. It applies to the Cookie app (Stitched Strategy LLC) on iOS and Android.

Delete it yourself, in the App:

  • Android: open the More tab and tap Delete Account & Data (if you are not signed in, the button reads Delete Data and removes the recipes stored on your phone). For security, you may be asked to sign in again before deleting.
  • iOS: go to Settings > Privacy > Delete Account & Data (if available in your build).

Or ask us to do it: email chef@cookievoicerecipes.com with the subject "Delete my Cookie account", from the email address you use to sign in to Cookie. We may need to verify your request before acting on it.

What is deleted: your account and sign-in, your recipes and your account profile (including subscription status information) in our cloud, and the recipes and recipe photos stored on your device. We begin deletion promptly and aim to complete it within 30 days, subject to technical constraints, legal obligations, and limited backup retention cycles.

What may be kept: feedback you submitted, anonymous or aggregated analytics, and crash reports, which are retained under Firebase and Google platform settings (see Section 4.4); and records we are required to keep for legal, tax or fraud-prevention reasons.

Subscriptions: deleting your account does not cancel a subscription. Cancel Premium in Google Play (Android) or in your Apple ID subscription settings (iOS), or you may continue to be billed.

4.4 Analytics Retention

Analytics retention is managed within Firebase configuration and Google platform controls.

5. How We Share Information

We do not sell personal information for money. We may share information:

  • With service providers: Including Google and Apple services described in Section 3
  • For legal reasons: To comply with law, legal process, or enforceable governmental requests
  • For safety and rights protection: To protect users, the public, and our rights or property
  • Business transfers: In connection with a merger, acquisition, financing, or asset sale (subject to applicable confidentiality and notice requirements)

6. International Data Transfers

Your information may be processed in the United States and other countries where our service providers operate. Data protection laws may differ by jurisdiction.

7. Your Rights and Choices

Depending on where you live, you may have rights to access, correct, delete, or request a portable copy of your personal information, and to object to or restrict certain processing.

  • Access and correction: You can review and update certain data in the App
  • Data portability: To request a copy of your account data, contact us at chef@cookievoicerecipes.com
  • Deletion: Use in-app deletion tools or contact us to request deletion, as described in Section 4.3
  • Marketing opt-out: You can unsubscribe from marketing emails at any time via any marketing email or by contacting us
  • Local data control: Removing the App deletes local app data from the device (subject to OS behavior and backups)
  • Analytics controls: You may have in-app and/or device-level controls; device controls may not fully disable all analytics collection used for core diagnostics
  • Premium AI features: If you cancel Premium, future use of those Premium AI features is disabled. Cancel in Google Play (Android) or your Apple ID subscription settings (iOS)
  • Device permissions: You can turn off microphone, camera and notification access for the App in your device settings; the features that need them will stop working

To exercise privacy rights, contact us at chef@cookievoicerecipes.com. We may need to verify your request before processing it.

8. U.S. State Privacy Notice

If you are a resident of certain U.S. states (such as California, Colorado, Connecticut, Utah, or Virginia), you may have additional rights under applicable law, including rights to know, access, delete, and correct personal information, and to appeal certain privacy decisions where required.

We do not sell personal information for monetary consideration and do not knowingly share personal information for cross-context behavioral advertising.

9. EEA/UK Privacy Notice

If you are in the EEA or UK, our legal bases may include performance of a contract, legitimate interests, consent, and compliance with legal obligations, depending on the processing activity.

You may also have the right to lodge a complaint with your local data protection authority.

10. Children's Privacy

The App is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided personal information, contact us so we can investigate and take appropriate action.

11. Security

We use reasonable administrative, technical, and organizational safeguards designed to protect information. No security method is guaranteed to be completely secure.

12. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. When we do, we will update the "Last Updated" date. If required by law, we will provide additional notice of material changes.

13. Contact Information

For questions or privacy requests, contact:

Stitched Strategy LLC
Email: chef@cookievoicerecipes.com