Privacy Policy
Effective date: [OWNER FACT: open, set at publication (DEC-615)]
Last updated: November 16, 2026
Policy version: [OWNER FACT: open, set at publication (DEC-615)]
What changed in this version: we describe kid profiles, households and allergy data; we name OpenAI and Anthropic as our AI providers and remove Google Vertex AI; we say that analytics and crash reports are off until you choose them; we describe web checkout and Stripe, support requests in the app, email sent through Amazon SES, public collection page reports, and the end-of-service promise; and we correct how long we keep exports, Chef conversations, consent records, accounting and purchase records and account deletion records, and add how long we keep diagnostic, crash and analytics data. The version and effective date are set when this policy is published.
This Privacy Policy explains what information the CookifyAI app and the cookify.ai website collect, why, who we share it with, how long we keep it, and the choices you have. On Google Play, the app is listed as “Cookify: Recipe & Meal Planner” (package io.cyberwiz.cookifyai). On the App Store, it is listed as CookifyAI.
1. Who we are
CookifyAI is provided by Lewis Matlock, doing business as CyberWiz (“CyberWiz,” “we,” “us”). We are responsible for your information as described here. Contact: support@cyberwiz.io.
2. What we collect in the app
| Information | What it is | Why we use it |
|---|---|---|
| Account details | Your name, email address and account ID. If you sign in with Google or Apple, we get your name and email from them. | To create your account, sign you in and support you. |
| Profile and settings | Display name, optional profile photo, time zone, language and app preferences. | To run and personalize the app. |
| Your content | Recipes, notes, meal plans and grocery lists you create or save. | To store and sync your content across your devices. |
| Photos you choose | Photos you pick to import a recipe or use as a profile photo. When we process a photo for an import, we remove location and other hidden photo data (EXIF). | To import recipes and show your photos. |
| Web links you import | The address of a recipe page you ask us to import. Our server fetches that page. | To read the recipe from the page. |
| Households and kid profiles | The members of a household and their roles. For a kid profile created by an adult: a display name, an avatar and an age band, and the adult’s consent with its method, the policy version and the time. | To run households and to let children use the app under an adult’s control. |
| Allergy lists | Allergens you or a managing adult choose to save for a member, only after a separate consent. See Consumer health data. | To warn about matching ingredients. |
| Chef messages | Messages you send to the Chef cooking assistant and its replies. | To answer you and keep your conversation. |
| Purchase history | Records of Pro subscriptions, recipe packs and Cookie (in-app credit) use, verified with Google Play, the App Store or Stripe (web checkout). | To give you what you paid for, restore purchases and handle refunds. |
| Device and advertising IDs | An app instance ID, and your device advertising ID if ads are shown. | For app security, to deliver ads and to verify rewarded ads. |
| Approximate location | The app does not ask for location permission. When ads are shown, Google AdMob can estimate your general area from your IP address. | For ad delivery and fraud prevention by Google. |
| Sign-in | Passkey public keys, and sign-in events (method, device and result). No biometric data reaches us: your device checks your fingerprint or face and returns only a signed proof. | To sign you in and keep your account secure. |
| Choices you make | Your analytics, crash reporting, advertising and AI processing choices, and when you made them. | To respect and record your choices. |
| Content reports | The reason you chose, an optional note (up to 500 characters) and a reference to the reported item. For a Chef reply, also a copy of the reply text. | To review reports about AI content. |
| Support messages | What you send us by email, or from Help > Contact us in the app: the topic, your message, the app details you choose to include, and our replies. | To answer you. |
Analytics and crash reports are off until you choose. Analytics (Firebase Analytics, which receives basic events about which features you use) and crash reports with performance diagnostics (Firebase Crashlytics, which receives crash reports with device details) are separate choices, and the app works whichever you pick. Nothing is collected until you answer, and a kid profile never sends analytics events or starts crash reporting. You can change each choice under Account > Privacy choices, where Consent history lists each consent with its date and policy version and lets you withdraw it. Withdrawing stops collection, and the app does not delete the record of your consent. When this policy changes, your analytics and crash choices stay as you set them, unless we mark the change as affecting them; then they stay off until you accept the new version.
We do not collect your phone number, contacts or precise location.
3. How we use information
- To provide the app: sign-in, saving and syncing your content, imports, meal plans, grocery lists and Chef.
- To process purchases, give you Pro benefits and keep track of Cookies.
- To show ads in the free version and, when available, reward you for optional rewarded ads.
- To keep the Service safe, prevent fraud and abuse, and fix problems.
- To answer support and privacy requests.
- To meet legal, tax and accounting duties.
We do not use your private content to train AI models. We do not publish your private content.
4. AI features and our AI providers
CookifyAI offers optional AI features: the Chef cooking assistant, meal plan suggestions, grocery list optimization, and help reading a recipe from a web page or a photo you choose to import. Each one asks for your confirmation and costs one Cookie. Before your first AI task, the app shows a notice once. If you decline it, manual features and import without AI keep working and only the AI tasks turn off.
When you use one of these features, we send the content needed for that request to an AI provider that works on our behalf: OpenAI or Anthropic. Depending on the feature, that content is your message to Chef, the recipes or meal plan you selected, your grocery list, the text of the web page you asked us to import, or the photo you chose to import. We do not send your name, email address or payment details with these requests. For plan suggestions, only anonymous exclusion tags go to a provider, never an allergy record or a member name or ID.
- Neither provider uses this content to train its models, under the commercial terms we use.
- We have no zero-data-retention agreement with either provider, and we do not request one. The providers keep API data for a limited time under their standard terms: Anthropic deletes API inputs and outputs from its systems within 30 days, and OpenAI keeps abuse-monitoring logs for up to 30 days, unless the law or an agreement requires longer.
- We have not confirmed that every request is processed only in the United States, so we do not promise that it is.
- Private recipes never enter the shared import cache. Only the web address of a public recipe page can enter it. A cached entry is refreshed after 30 days, and a takedown request purges it.
- The AI result is returned to us and held as a draft for up to 30 days until you choose to save or apply it. Once you save it, it is like any recipe, plan or list you create. You can edit or delete it, and it is deleted with your account.
- Video import. You can add a video file you supply: one you pick from your gallery, share to the app or record from your screen. We do not download videos from other sites; for a link we read only the public details the site gives. A video can be up to 100 MiB and 2 minutes, and the import page shows the cost, 1 Cookie, before the video uploads. The video uploads in pieces to private storage in your account. On Android a notification, “Uploading your recipe video,” shows while it uploads. Our own video worker cuts the video into scenes and key frames (with ffmpeg and PySceneDetect), reads the text on the frames (OCR), and turns the speech into text with faster-whisper software that we run ourselves. For key frames where OCR finds fewer than 3 characters, an AI provider (section 4) writes a short caption, up to a fixed number of frames per video. As a fallback, the speech-to-text can instead be done by OpenAI’s transcription service, a third party that then receives the audio. The text digest is then sent to our AI providers to find the recipe. The video file is deleted once the recipe draft has been published successfully. If extraction fails, we keep the video and the digest so a retry can use them. Leftover uploads are scheduled for cleanup 24 hours after processing is confirmed stopped, which can be later than the moment the job ends. Deletion can take longer if cleanup is delayed or fails. A kid profile can add a video only if a managing adult has given a separate media consent, and a kid profile can use an AI provider for an import only if a managing adult has also given a separate AI consent. The two consents are separate; the media consent does not give the AI consent.
If you do not want your content processed this way, do not use the AI features. Recipes, plans and grocery lists work without them. Avoid including sensitive personal information, such as health details, in Chef messages or report notes.
5. Ads and your choices
The free version of the app may show ads from Google AdMob. Pro removes ads.
- Depending on where you live, Google’s consent form may ask for your ad choices.
- Ads are not personalized unless you agree in Google’s consent form and turn on Personalized ads in the app.
- Even non-personalized ads use your device advertising ID and approximate location (from your IP address). Google uses them to deliver ads, limit how often you see an ad, count views and prevent fraud.
To change your ad choices:
- In the app, go to Account > Advertising choices. You can turn off personalized ads and open Google’s privacy form.
- On Android, you can reset or delete your advertising ID in your device settings (Settings > Google > Ads, or Settings > Security & privacy > Privacy > Ads, depending on your device).
- Subscribing to Pro removes ads.
6. Who we share information with
We share information only as described here.
Service providers that work for us:
- Google Firebase and Google Cloud (Google LLC): sign-in, database, file storage, servers, app integrity checks, text reading of receipt photos (Cloud Vision) and, if you turn them on, analytics and crash reports. Your data is stored in the United States.
- OpenAI and Anthropic: AI features, as described in section 4.
- Stripe: card payments for web checkout on cookify.ai (United States only), and billing management.
- Amazon Web Services: Amazon SES sends our transactional email, such as replies to support requests and billing notices, to your email address. We do not use tracking pixels or click tracking in these emails.
- Google Play Billing and the Apple App Store: payments and purchase verification for store purchases. They also have their own relationship with you as the seller of record.
- Apple: Sign in with Apple, if you use it.
Companies that receive information for their own purposes:
- Google AdMob (Google LLC): when ads are shown, Google receives your device advertising ID, approximate location and ad interactions. Google uses them under its own privacy policy. See how Google uses information from apps that use its services.
- Instacart (Maplebear Inc.): when available, and only if you choose to open your grocery list in Instacart. We send the items on your list (name, amount and unit). We do not send your name, email or account ID. After that, Instacart’s privacy policy applies.
Other cases: we may share information if the law requires it, to protect people’s safety or our rights, or as part of a sale or transfer of the Service. If the Service moves to a new owner, this policy still applies to your information.
7. The cookify.ai website
When you visit cookify.ai:
- Hosting and security. Our web host (Google Firebase Hosting) and Cloudflare process your IP address and browser details to deliver the site and protect it from attacks. Cloudflare may set a strictly necessary security cookie when it needs to check a request.
- Now. Our pages set no analytics, marketing or tracking cookies, and Cloudflare may set a strictly necessary security cookie. Our pages also load no analytics or marketing scripts and have no cookie banner or newsletter signup form.
- Public collection pages. When someone publishes a collection as a public page, anyone with the link can read it, and the page can be stopped with Stop sharing, by deleting the collection or by a takedown. A stopped page answers “removed.” A small record stays so the address is never reused; it holds only the address, an opaque collection ID, the dates, and after a takedown the time and the staff member’s ID, with no content and no owner ID. Anyone can use Report this collection without signing in. A report stores the page address, the reason you choose, your optional note (up to 500 characters), the page owner’s account ID and the date the page was published. We do not keep your IP address, browser details or contact details with it. Reports are deleted after 90 days.
Before the website moved to Firebase Hosting, it ran on WordPress hosted on Microsoft Azure, and:
- Hosting and security. Our web host (Microsoft Azure) and Cloudflare processed your IP address and browser details to deliver the site and protect it from attacks. Cloudflare Web Analytics counted visits without cookies.
- Cookie choices. Our cookie banner saved your choice in a cookie. It also kept a record of the choice on our server as proof of consent: the date, the page, your approximate country, your browser type and your choices. You can ask us to delete it.
- Analytics (only if you accepted analytics cookies). Google Analytics and Microsoft Clarity measured how people used the site. Clarity recorded clicks, scrolling and mouse movement to show how pages were used.
- Marketing (only if you accepted marketing cookies). Google could use the Google Analytics data to measure our Google Ads campaigns. HubSpot tracking measured interest in our marketing.
- Newsletter. Our newsletter signup form was run by HubSpot. If you signed up, HubSpot stores the details you entered for us. Every newsletter email has an unsubscribe link.
See our Cookie Policy.
8. How long we keep information
| Information | How long we keep it |
|---|---|
| Account details, profile and settings | Until you delete your account. |
| Recipes, plans, grocery lists and saved photos | Until you delete them or delete your account. When you delete an item, a small record without its content is kept so your devices stay in sync. It is marked for removal after 90 days and is always deleted with your account. |
| Chef conversations | You can delete a conversation at any time. A conversation expires after 90 days without use. The stored text of a Chef reply you reported is kept until we finish reviewing the report (or until the report is deleted at 90 days if it is marked for follow-up), even if you delete the conversation, and it is deleted with your account. |
| Videos uploaded for an import | The video file is deleted once the recipe draft is published successfully; if the import fails it is kept for a retry, and leftover uploads are scheduled for cleanup 24 hours after processing is confirmed stopped (not 24 hours after the job ends). Deletion can take longer if cleanup is delayed or fails. The text digest and keyframes are kept with the saved recipe, or deleted with the draft if you do not save it. |
| Photos uploaded for an import | Scheduled for cleanup 24 hours after processing is confirmed stopped (not 24 hours after the import finishes). Deletion can take longer if cleanup is delayed or fails. |
| Import results you have not saved | Up to 30 days. |
| Data exports | Deleted after 7 days. Download links expire after 15 minutes. |
| Content reports | 90 days, or until you delete your account if that is sooner. The copy of a reported Chef reply follows the Chef conversations row. |
| Instacart shopping links | Marked for removal after 90 days, and always deleted with your account. |
| Your privacy and ad choices | Until you delete your account. |
| Consent records | An adult’s own consent records are kept for the life of the account. When the account is deleted, a copy of each one, filed under a one-way hash of the account ID, is kept for 3 years after we accept the deletion, as proof of consent, and then deleted. A record about a kid follows the kid, not the adult: it is kept for 3 years after we accept the deletion of the kid’s profile, even if the managing adult’s account is deleted first, and is then deleted. Until the kid is deleted it stays in the adult’s account or, if that adult is deleted first, as a hashed copy with no end date yet. The minimal evidence of a household’s verifiable parental consent (method, notice and policy versions, a hashed verification reference and dates) is kept on the same 3-year clock after the kid is deleted; a signed form scan is deleted on its own 30-day rule. The audit-log entry that records a kid’s consent is also kept for 3 years after the kid’s profile is deleted. It is kept as written, not hashed: it holds the consenting adult’s account ID, the kid’s household member path and the kid’s account ID. |
| Support requests from the app | 2 years after we close the request, or until you delete your account. |
| Kid profile data | 30 days after the kid profile is removed, or at once when a managing adult asks. |
| Sign-in events | 400 days. Passkey records are kept until you remove the passkey or delete your account. |
| Public collection page records | See section 7. Reports are deleted after 90 days. The small record of a stopped page is kept for as long as the address must stay unused. |
| App server logs | Up to 30 days. They do not include your content. |
| Diagnostic and crash records (only if you turned them on) | Our own raw diagnostic records and Crashlytics exports are kept 90 days. How long the provider’s own console keeps data is verified separately and is not covered by this row. |
| Diagnostic and performance summaries | 26 months (790 days). They hold no user content and do not identify you. |
| Raw analytics events (only if you turned analytics on) | 14 months, in BigQuery. |
| Backups | Copies in backups expire within 30 days. |
| Purchase accounting records | Seven years after settlement, even after you delete your account. These records include only the product, a transaction reference, the amount, dates and any refund outcome. |
| Purchase check records | The purchase records that tie a store purchase to an account (digests of the store receipt) so the same purchase cannot be used twice, and so we can keep accounting records. Kept for seven years after settlement (the end of the paid period for a subscription, the purchase for a one-time product, or the refund or revocation, dated when the store or Stripe says it happened; checking a purchase again later does not restart the seven years). After that they are deleted once your account no longer exists and no live household plan (Family or Lifetime) still relies on the purchase; if one does, they stay while it is live. While your account exists they stay, because they back your plan. Without them a deleted account could start a second trial. A record with no usable settlement date when we dated older records is kept seven years from that day. |
| Account deletion records | Your account ID and the time of deletion, and a deletion receipt with no content, so a deleted account is not restored by mistake after a backup is restored. Deleted 35 days after the deletion finishes. Daily backups are kept 30 days, so no backup taken after that point holds the account. When we delete them, we leave one empty record keyed by a one-way hash (unsalted SHA-256) of your account ID, so a deleted account ID is never treated as a new account. It holds no content and no readable account ID, and we keep it indefinitely. Anyone who already knows your account ID can compute the hash and match it. |
| Website analytics and newsletter signups collected by earlier versions of the website | Kept by Google, Microsoft and HubSpot under the retention settings of those services. You can ask us to delete your newsletter signup at any time. |
| Website cookie consent records from earlier versions of the website | Kept as proof of your choice. You can ask us to delete them. |
9. Deleting your account
You can delete your account in the app or by email. See Delete your CookifyAI account for the steps. Before you delete, transfer ownership of any household that has other adults, and hand over or delete any kid profile that you are the only managing adult of; the app asks for this first. We acknowledge a privacy request within 2 business days and answer it within 30 days. When we accept a deletion, your account is blocked from new work and you are signed out. A few kinds of stored files can still be read for up to one hour, until your sign-in token expires. Our system is set to finish deleting your data within 7 days, and copies in backups expire within 30 days. The records we keep are listed in section 8. Some data saved by older versions of the app, and ratings you gave to recipes in our catalog, are not yet deleted automatically. Email us and we will delete them. Deleting your account does not cancel a subscription. Cancel it in Google Play, the App Store or the Stripe billing portal.
10. Security
We protect your information with measures such as encrypted connections (HTTPS), private storage that is not publicly accessible, and access limited to our team and the service providers listed above. No method of storing or sending data is completely secure, so we cannot promise perfect security.
11. Children, households and kid profiles
CookifyAI accounts are for adults 18 and older. The app is a mixed-audience app: children, including children under 13, can use it only through a kid profile that a managing adult creates. A household has members with roles. Adults see the household plan, groceries, pantry, cookbook and members. A kid member sees only what the kid screens show. What a household can see is limited to that household.
Before a kid profile is created, the adult gets a notice that says what we collect (a display name, an avatar, an age band, any allergens the adult enters, skill progress, ratings and cook sessions), why, who can see it, and how to delete it. Before we collect anything for the kid, the adult gives verifiable parental consent in one of three ways: a Pro Family purchase through Google Play or the App Store on the adult’s account, a one-time $1.00 card check that we refund in full, or a signed form that we approve. A confirmation tap alone is not consent. The consent is recorded with its method, the policy version and the time. A kid session shows no ads, sends no analytics events and starts no crash reporting. The adult can review and delete the profile at any time; its data is deleted as section 8 says. Kid profiles need a managing adult’s consent in every region.
We do not knowingly collect information from a child except through a kid profile that an adult has created and consented to. If you believe a child has given us information in another way, email us and we will delete it.
Consumer health data
Allergy lists are health data. We store them only after you give a separate consent (“Save allergies for warnings”); for a kid, the managing adult consents. Allergen codes are visible to the member and to the adult members of the household. We do not sell or share allergy data, and no allergy value or count reaches analytics. For plan suggestions, only anonymous exclusion tags go to an AI provider, with no member name or ID. Withdrawing the consent deletes the allergen codes in the same step and clears the warnings; export archives we already hold are not changed, and they are deleted after 7 days; a copy you already downloaded stays with you. Warnings name the member and the matched ingredient. CookifyAI never says a recipe is allergen-free, and the comparison can miss an allergen.
End-of-service promise
If CookifyAI is ever closed, sign-in, reading, editing, sync and full export keep working for at least 180 days. Each adult gets one email with a signed link to a final export, and we delete no data before the final export has been offered to every adult.
12. International transfers
We are based in the United States, and our app data is stored in the United States, and we process it there. Our AI providers may process some content elsewhere (see section 4). If you use CookifyAI from another country, your information is transferred to the United States, where data protection laws may be different from those in your country. Email us if you have questions about these transfers.
13. Your rights
Depending on where you live, you may have the right to:
- Get a copy of your information. You can also use Account > Request data export in the app.
- Correct information that is wrong.
- Delete your information.
- Receive your information in a portable format.
- Object to or restrict some uses of your information.
- Withdraw consent at any time. This does not affect what we did before you withdrew it.
To make a request, email support@cyberwiz.io from the email address on your account. We may need to confirm that the account is yours. Never send your password, verification codes or full store receipts. We will not treat you differently for using your rights.
California residents
We collect these categories of personal information:
- Identifiers (name, email, account ID, device and advertising IDs).
- Commercial information (purchase history).
- Approximate geolocation (from ads).
- Internet activity (ad interactions and, on the earlier version of the website and with your consent, website analytics).
- Photos and other content you provide.
We collect them from you, your device and the sign-in provider you choose, for the purposes in section 3. We disclose them to the service providers in section 6.
We do not sell personal information for money. When the free version of the app shows ads, Google AdMob receives your advertising ID and approximate location, and Google may use them for its own purposes (see section 6). On the earlier version of our website, if you accepted marketing cookies, they sent data to Google and HubSpot. Our pages now set no analytics, marketing or tracking cookies and send no data to advertisers. California law may treat these as a “sale” or “sharing” of personal information. To opt out:
- Turn off Personalized ads in Account > Advertising choices.
- Delete your Android advertising ID in your device settings, or subscribe to Pro to remove ads.
- On the earlier version of our website, you could choose Reject all in the website’s cookie settings.
- Or email us and we will help.
California residents have the right to:
- Know what personal information we have about you.
- Delete it.
- Correct it.
- Opt out of the sale or sharing of personal information.
- Not be treated differently for using these rights.
Your sign-in details are sensitive personal information. We use them only to sign you in and keep your account secure. We do not use sensitive personal information to infer things about you. You can use an authorized agent; we may ask for proof that they act for you.
European Economic Area and United Kingdom residents
We use your information on these legal bases:
- To perform our contract with you: your account, your content, the features you ask for and your purchases.
- Your consent: ads in the free version (given through Google’s consent form), personalized ads and, on the earlier version of the website, non-essential website cookies. You can withdraw your consent at any time.
- Our legitimate interests: security, fraud prevention, fixing problems, the newsletter you sign up for, and keeping accounting records.
- Legal obligations: tax and accounting duties that apply to us.
You need to give us your account details to use the app. Everything else is optional. We do not make decisions about you based only on automated processing that have legal or similarly significant effects. You can also complain to your local data protection authority.
14. Changes to this policy
We may update this policy. We will post the new version on this page, change the “Last updated” date and policy version, and describe what changed at the top. If a change is important, we will also try to tell you in the app or by email.
15. Contact us
Lewis Matlock, doing business as CyberWiz
Privacy requests: privacy@cookify.ai (answered within 30 days)
General support: support@cyberwiz.io
Website: cookify.ai
See also: Consumer health data, Privacy Choices, Cookie Policy, Terms of Service.