Support

CookCache support, FAQ, cancellation, and restore-purchases help.

CookCache Support

This page provides CookCache support, cancellation, restore-purchases, and current pre-launch app behavior information.

Contact support

When contacting support, include your device model, iOS version, CookCache app version, and a short description of the issue. Do not send full private recipes, screenshots, or personal information unless support specifically needs it and you are comfortable sharing it.

What CookCache does today

CookCache helps you save user-provided recipes into a private cookbook. The current app stores data locally on your device. It supports pasted recipe text, optional source URLs stored for context, user-selected photos/screenshots, parsed recipe cards, grocery-list export, and a local mock household workflow.

The app does not currently have CookCache accounts, a backend server, cloud sync, remote recipe scraping, public recipe hosting, ads, or remote analytics.

Importing recipes

Saved recipes and deletion

Saved recipes are stored locally. You can delete individual recipes from the recipe detail screen. Removing the app may remove local CookCache data, subject to platform backup behavior.

CookCache currently has no account-login system, so there is no CookCache account to delete in this build.

Subscriptions, trials, and restore purchases

CookCache is intended to offer:

Final App Store product screens control the exact offer, local currency, taxes, renewal terms, and trial eligibility. Subscriptions are managed through the user's Apple ID/App Store account. Users should be able to restore purchases from inside the app once live purchase products are configured.

To cancel or manage a subscription, use Apple App Store account settings.

Household features

The current household feature is mock/local only. It stores entered mock invite email addresses or phone numbers locally and does not send real SMS, email, or backend invitations.

Privacy

CookCache is local-first in the current build. Recipe data, mock household data, settings, and local event records are stored on-device. RevenueCat and Apple will process purchase/subscription/customer identifiers when live subscriptions are configured. See the Privacy Policy for details.

Known setup items before App Store submission

Before App Store submission, the following must be finalized: