Privacy Policy
Effective August 24, 2026Last updated August 24, 2026
Who operates Cook It Again
Cook It Again is operated by BluPoint Media, Inc., a company established in the State of Florida, United States. BluPoint Media, Inc. is responsible for this policy and is who "we" means everywhere below.
This policy describes how the Cook It Again mobile app and this website handle information. Because the app works locally and has no backend of its own, the amount of data anyone else handles on your behalf is small — but it is not nothing, and this page is about the difference.
Privacy questions, and any request described under "Your privacy rights" below, go to the address at the end of this page.
What is stored on your device
Everything you enter stays on your device unless you export it yourself. None of it is transmitted to us, because there is nowhere to transmit it to.
- Product names, brands, package sizes, and barcodes
- Custom Dish names, descriptions, categories, and notes
- Ingredient names, quantities, units, and preparation notes
- Base portions
- Appliances and cooking setups: temperature or power level, duration, preheat, portion, and timed steps
- Cooking history: what was cooked, with which settings, how long it took, and how it turned out
- Photos you take or choose
- App preferences, such as temperature unit and theme
Camera and barcode scanning
Scanning needs camera access. Barcode detection runs entirely on the device — no frame is uploaded, recorded, or retained, and the camera is active only while the scanner is open.
Denying the camera does not prevent you from using the app. Barcodes can be typed, and an item can be saved without one.
Custom Dishes, ingredients, and photos
Custom Dish content is the most personal thing the app holds: it is a household’s own way of making something. It is stored on the device, it is never sent anywhere for lookup, analysis, or suggestion, and it is not read by anyone but you.
Ingredient names and amounts are notes. They are not checked against any nutrition, allergen, or ingredient database, because no such lookup exists in the app.
Optional Open Food Facts lookup
When you scan a barcode the app has not seen before, it can ask Open Food Facts for a product name, brand, and package size, so you do not have to type them. The request contains the barcode and the ordinary network metadata any web request carries, including your IP address, which Open Food Facts receives.
The lookup is a convenience and never a requirement: it is skipped when the item is already saved, it can fail without affecting anything, and every result is shown for you to confirm or correct before it is saved.
Custom Dish names, ingredients, notes, cooking settings, and history are never sent to Open Food Facts or to anyone else.
Purchases and RevenueCat
The lifetime unlock is an in-app purchase processed by Apple or Google. Payment details never reach the app; it is told only whether the unlock is active.
RevenueCat checks that status on the app’s behalf. It is given an anonymous identifier generated on the device and the store’s own transaction data. It is not given your name, your email address, or anything you have saved in the app.
Because the identifier is anonymous and there is no account, the unlock belongs to the store account that bought it. It is restored by signing in to that account and using Restore Purchases — and it does not move between Apple and Google.
Local notifications
Cooking alerts are scheduled with your device’s operating system when a cook starts. They are local notifications: nothing is sent from a server, and the app has no remote push capability at all.
An alert may name the item, the appliance, the step, and the time remaining, so it is useful on a lock screen. It carries nothing else you have saved.
Declining notification permission does not stop a cook. The timer still runs; the app simply cannot alert you when you are looking elsewhere, and it says so before you start.
Backup files
A backup is a file you create and file yourself. The app writes it and hands it to your phone’s share sheet; you choose where it goes, and the app is never told the destination and never keeps a copy.
Backups may include dish photos, ingredient quantities, preparation notes, and cooking history. Store backup files somewhere you trust — the file is as sensitive as the library it came from, and once it is in a shared folder it is subject to that provider’s terms rather than to this policy.
Purchase and entitlement status is never written into a backup. Restoring a file cannot grant the unlock, and losing one cannot take it away.
Support email
If you email support, we receive your address and whatever you choose to include. It is used to answer you and nothing else — no marketing list, no newsletter, no onward sharing.
The app can generate a support report for you to attach. It contains build identifiers, permission states, and counts of saved records. It contains no product names, dish names, ingredients, notes, photos, file paths, or purchase state, and it is never sent automatically.
Analytics, advertising, and crash reporting
There are none. Cook It Again contains no analytics SDK, no advertising SDK, and no crash reporter. Nothing measures how you use it, and no usage or crash data is collected — the app has nowhere to send any of it.
This website sets no cookies, embeds no tracking pixels, and loads no third-party scripts. That is why there is no cookie banner: there is nothing to consent to.
Retention and deletion
Because the records are on your device, you control how long they last. Individual items, setups, and history entries can be deleted at any time, and Settings offers a single action that deletes everything the app has stored.
Uninstalling the app removes its data with it. If you want to keep any of it, export a backup first.
Deleting everything keeps your purchase, because the purchase belongs to your store account rather than to the app’s data.
Your privacy rights
These rights are offered to everyone who uses Cook It Again, wherever you live, rather than only where a particular law compels them. They are modelled on the California Consumer Privacy Act as amended (CCPA/CPRA), which is the most demanding standard that clearly applies to us.
Most of them you exercise without asking anyone. Your records sit on your device, so you can already read them, correct them, export them, and delete them yourself at any time, and Settings has a single action that removes everything the app has stored. There is no request to make and nobody to make it to.
The one thing we may hold that you cannot reach from the app is an email you have sent to support, along with whatever you chose to put in it. You can ask what we have, ask for a copy, ask for a correction, or ask for it to be deleted, and we will respond within 45 days. Asking costs nothing and changes nothing about how the app works for you — there is no worse version of it to be moved to.
Your personal information is not sold, and it is not shared for cross-context behavioural advertising. There is no advertising in the app, no advertising network behind it, and no analytics data to sell, as set out under "Analytics, advertising, and crash reporting" above.
If you are in the United Kingdom or the European Economic Area, make the same requests the same way. Where we handle a support email we do so on the basis of our legitimate interest in answering you, and you may also complain to your national data protection authority if you think we have handled it badly.
Security
App data is stored in the app’s private storage, protected by the operating system’s own protections for it. A device passcode or biometric lock is the main thing standing between someone holding your phone and what is on it, and it is worth having.
A backup file you export has whatever protection its destination gives it. That is a choice worth making deliberately.
Children
Cook It Again is a general-audience utility and is not directed at children. It collects no personal information from anyone, so there is nothing collected from a child either. If a child sends personal information to the support address, contact us and it will be deleted.
Where information goes
Your saved records stay on your device, wherever that is. The narrow exceptions travel to the services that handle them: an optional lookup to Open Food Facts, purchase processing to Apple or Google, entitlement checks to RevenueCat, and a support email to the mail provider.
BluPoint Media, Inc. is established in the State of Florida, United States, so a support email you send us is handled in the United States. That is the only flow in the list above that reaches us at all — the other three go to those companies directly and are covered by their own policies, linked below.
Third-party services
These are the only services involved, and each is involved for one narrow reason. Their own policies govern what they do with what they receive.
Apple App Store
Distributes the iOS app and processes purchases.
Your payment details, which the app never sees. The app is told only whether the unlock is active.
Google Play
Distributes the Android app and processes purchases.
Your payment details, which the app never sees. The app is told only whether the unlock is active.
RevenueCat
Checks whether the lifetime unlock is active.
An anonymous identifier generated on the device, and the store’s transaction data.
Open Food Facts
Optional product name and brand lookup for a barcode you have not saved.
The barcode, and ordinary request metadata including your IP address.
A backup destination you choose
Storing a backup file, if you put one there.
Whatever the file contains, once you save it there. Their terms apply to it from that point.
Changes to this policy
If this policy changes, the effective date at the top of the page changes with it. Material changes will also be noted in the app’s release notes.
Contact
Questions about this policy, or about what the app stores, go to the address below.