CookCache Privacy Policy

This policy describes the current CookCache app behavior observed in the source and the intended purchase integration.

Summary

CookCache is a local-first recipe organizer. In the current app build, recipe and household data is stored on the user's device using local storage. CookCache does not currently operate an app account system, backend server, remote recipe catalog, advertising network, or remote analytics pipeline.

CookCache does include a RevenueCat SDK integration for future in-app subscription management. RevenueCat public keys are currently blank, so the live SDK purchase flow is not configured yet. When configured, RevenueCat and Apple/App Store payment systems will process purchase/subscription/customer identifiers needed to provide and restore subscription access.

Data the app stores locally on the device

The app may store the following in local AsyncStorage keys such as cookcache.recipes.v1, cookcache.settings.v1, cookcache.household.v1, and cookcache.analytics.v1:

• Recipes and recipe drafts: title, ingredients, steps, tags, prep/cook metadata, notes, source type, user-provided recipe text, optional source URL, optional local image URI, created/updated timestamps, and whether a recipe is marked as household-shared in the local mock workflow.
• Settings: onboarding/paywall state and local mock entitlement state used by the MVP build.
• Mock household data: household name/code, local members/activity, and mock invite email address or phone number entered by the user. These mock invites are stored locally only; the current app does not send SMS, email, push invites, or backend invitations.
• Local analytics/event records: event name, timestamp, platform, and small event properties used to inspect app flow. These records are currently stored locally and are not sent to a remote analytics service.

Because the current app has no CookCache backend, this locally stored data is not transmitted to a CookCache server.

Recipe import, URLs, and creator content

CookCache imports recipes only from user-initiated actions such as pasted text, a user-entered source link, or a user-selected photo/screenshot. A source URL is stored as attribution/context only in the current app. The app does not fetch, crawl, scrape, host, or redistribute creator recipe pages.

Users are responsible for making sure they have the right to save and use any recipe text or image they add to their private cookbook.

Photos and OCR

Photo import is user-initiated through the device photo picker. The current implementation requests photo-library permission only when the user chooses photo import.

Photo text extraction is a gated pre-launch test path and must pass native device QA before it is described in public App Store listing claims. CookCache does not intentionally upload recipe photos to a CookCache server because no backend exists.

Purchases and subscriptions

CookCache is intended to offer auto-renewable subscriptions: a primary annual plan with a 7-day free trial, then $29.99/year, and a secondary monthly plan at $5.99/month. Final App Store purchase sheets and product metadata control the exact offer shown to users.

Payments are processed by Apple through the App Store. CookCache does not receive full payment-card details from Apple. When RevenueCat is configured, RevenueCat may collect and process purchase/subscription/customer identifiers and receipt/subscription status so the app can provide premium access and restore purchases.

Analytics, advertising, and tracking

The current app stores local in-app event records only. These local analytics events are not currently sent to remote analytics providers.

CookCache does not currently serve third-party ads and does not track users across apps or websites owned by other companies for advertising or data-broker purposes.

Accounts and deletion

The current app does not offer CookCache account creation or login. Users can delete individual saved recipes in the app. Users may also remove the app from their device to delete app-local storage, subject to platform backup behavior.

If CookCache later adds real household accounts, cloud sync, Sign in with Apple, or any backend account creation, this policy and the app must be updated to provide an in-app account-deletion path and any legally required data-access/deletion process.

Children

CookCache is not designed for children and should not be directed to children in App Store metadata.

Changes to this policy

This policy must be updated before launch if CookCache adds a backend, remote analytics, account creation, cloud sync, server OCR, email/SMS invites, ads, tracking, or any other material data collection not described here.

Contact

Support page: https://cookcache.app/support. Support email: support@cookcache.app.

Apple/App Store privacy research references

• Apple Developer: App Privacy Details on the App Store — explains data collection disclosures, tracking, linked data, and on-device processing.
• Apple Developer Help: Manage app privacy — notes that a privacy policy URL is required for apps.
• Apple Developer: Auto-renewable Subscriptions — subscription setup and in-app subscription disclosure expectations.