Privacy Policy — CookWeave
CookWeave: Recipes & Menus

Privacy Policy

Delete your CookWeave account ↓

1. Who this policy covers

This Privacy Policy explains how Kakushadze Maksym, operating under the Dazlight name (“we”, “us”), handles information in the CookWeave Android app. We operate from Ukraine. For privacy, account deletion or purchase questions, contact info@dazlight.com.

This policy covers CookWeave. Browsing dazlight.com and using its support form are covered by the separate Website Privacy Policy, including its explanation of website analytics and form submissions. The Terms and Conditions are available separately.

Availability of online features and Pro purchases depends on the app version. Purchases and the public catalog are currently unavailable. Signed-in account and entitlement checks may still use the providers described below.

2. Your local cooking data

CookWeave stores the recipes, ingredients, menus, private notes and photos, kitchen profile, cooking sessions, history, corrections and related settings you create on your device. It also stores local menu drafts and any private copies you choose to save. The app uses this information to provide recipe, planning, shopping and cooking features.

You can use the local recipe book and cooking tools without an account or internet connection. We do not automatically upload your private book to Dazlight. Its local cooking diagnostic journal stays on your device and is not automatically uploaded. In versions offering optional usage analytics, analytics is off until you choose to enable it; you can change “Usage analytics” in Profile. This choice does not affect recipes, cooking or Pro access. The optional analytics service is described below. Firebase, Google Play and RevenueCat may separately process account, security and purchase information as described in this policy. Website analytics are covered by the separate Website Privacy Policy.

Depending on your Android settings, the operating system may back up eligible local app data. Device-bound encrypted credentials and protected purchase-verification storage are excluded from the app’s configured Android backup and transfer rules. Files you export yourself are separate copies under your control and may be stored by a file provider you choose. CookWeave does not provide automatic online sync of your private book.

3. Optional account and online actions

If you choose to create or use an account, Firebase Authentication processes your email address, account identifier, password or Google sign-in information, and technical service information needed for authentication and security. Google provides Firebase Authentication and Cloud Firestore; these services may process data outside your country.

Your Firebase account identifier associates online actions with your account. Firestore may store your public display name, acceptance of publishing terms, submitted recipe or menu drafts, publication decisions, favorites, blocks, reports, feedback and deletion requests. Account-linked purchase recovery may also create a verification record associated with your account.

Publication drafts are restricted to their author and authorized operators. Recovery verification and purchase-ownership records are also not public; some are available only to authorized operators. Approved recipes, menus, public author names and approved public feedback can be visible to other users. Private book content is not uploaded or published merely because you sign in. Public photo uploads are not provided in this version.

The current public catalog is unavailable. This section describes how optional account and submission features handle data when they are used, rather than promising that every online feature is available now.

4. Recipe links and files you choose

If you choose to import a recipe from a URL, your device requests the selected page. That website may receive your IP address and other normal request information under its own privacy practices. The result is an editable private draft unless you separately choose to submit permitted content online.

You can export or import CookWeave backup files. A backup may contain private recipes, notes and other content. You choose its file destination or source through your device. If you save it with a cloud file provider, that provider handles the copy under its own policy. Removing the app does not remove exported files.

5. Timers, support and service providers

Cooking timers and reminders use your device’s notification services, subject to your device settings. They help track time but do not check whether food is safe or done.

If you email us or use our website support form, we receive the contact details and message you send to answer your request. Your device, Google Play, Firebase and RevenueCat may process technical or service information needed to provide their respective services. We do not use your private recipe book for advertising or sell it to data brokers.

5A. Pro verification, purchases and recovery

CookWeave uses Google Play and RevenueCat to check Pro access and, when available, process or restore purchases. RevenueCat receives your CookWeave account identifier and purchase or entitlement information. Account-linked entitlement checks may occur when you sign in or refresh Pro status, including when new purchases are unavailable. The providers also process technical information needed to operate and secure these services. Google Play handles payment information; CookWeave does not receive your payment-card details.

Purchase information is used to validate access, restore verified rights, handle refunds or revocations and help prevent fraud. RevenueCat also processes purchase information for purchase-related analytics. CookWeave keeps protected verification evidence on your device so previously verified access can remain available offline. Local cooking remains available without an account.

After account deletion, you can ask support to verify recovery of a purchase using the recovery code saved before deletion and your Google Play purchase evidence. A request contains the new account identifier, recovery code, purchase token and order identifier, and request-verification details. Sending a request does not itself unlock Pro.

In app versions with a built-in public support encryption key, you can choose “Send encrypted recovery request” while an authorised support operator has opened a short receiving window. The app encrypts the request on your device for that operator and sends the encrypted contents, account identifier and verification metadata to Firebase Cloud Firestore. The public support encryption key is included in the app; the receiving-window record does not supply a replacement encryption key. The authorised operator decrypts the request for verification. These records are restricted, not public recipe content.

Receiving is closed by default. The app checks support availability before sending; an unavailable or closed window does not accept a request. Contact info@dazlight.com to ask when support is available, without attaching a file, recovery code or purchase token. Do not send these secrets through ordinary email, the website support form or another unverified channel. A private request file you choose to save is not sent automatically; share it only after support confirms a protected channel and gives its instructions. Never send your password or card details.

Requests are checked manually with Google Play and RevenueCat. The recently authenticated account’s identity proof expires after five minutes; if verification cannot be completed in time, sign in again and create a fresh request while support is ready. This verification window is not an automatic deletion schedule. Ongoing recovery records retain linked account identifiers, purchase and recovery-code hashes, entitlement state and relevant dates; they are not anonymous. Encrypted inbox contents and any operator-held raw request files are handled separately from these limited records, as described below.

5B. Optional app usage analytics

If you choose to enable usage analytics, CookWeave uses Google Analytics for Firebase to understand which features people use, where a task stops, whether they return, and which technical errors need attention. The app sends predefined events for app entry, screen categories, foreground or background state and whether cooking is active, account and catalog operations, recipe and menu actions, shopping, planning, cooking, Pro purchase attempts and verified-access outcomes. It sends fixed status or error categories and limited count categories, rather than your written content or raw error messages. A completed cooking event records the steps you marked complete; it does not establish that food is safe or ready.

Google Analytics also processes an identifier for this app installation, app and device information, session and engagement information, an approximate region derived from network information, and supported Google Play purchase events, which may include the product and price. These records are pseudonymous, not anonymous. CookWeave does not set your account ID as an Analytics User-ID, send your email, recipe titles or text, ingredients, notes, photos, imported URLs, purchase tokens, order IDs or recovery codes as custom analytics data. CookWeave disables Analytics advertising-ID collection and advertising consent. Google Signals and advertising personalization are disabled. We do not use these events for advertising or session replay.

Analytics is optional and disabled by default. You can turn off “Usage analytics” in Profile at any time without affecting cooking or Pro; the app then stops future usage-analytics collection, clears its local Analytics data and resets its installation identifier. This does not automatically erase information already received by Google. Actions before consent are not uploaded from the local diagnostic journal. We currently configure Analytics event-data retention to two months and user-data retention to fourteen months, with user-identifier retention renewed by new activity. These are distinct provider settings, not a promise that every record disappears on an exact day; standard aggregated reports can remain longer. Deleting a CookWeave account does not by itself identify or erase Analytics records, because CookWeave does not link the Analytics installation identifier to your account. Contact info@dazlight.com for questions or a deletion request; we explain what can be identified and removed and any limits. Do not email purchase tokens, recovery codes or private recipe content. Google may process Analytics information outside your country. See Google’s information about partner services.

6. Retention, account deletion and your choices

Local data and exported copies

Your local book remains on your device until you remove it, clear the app’s data or uninstall the app. Signing out or deleting an online account does not erase the local book, active cooking or files you exported. Android and any file provider you selected may retain backup copies under their own settings. You manage those copies separately.

Online account and content

Account and online activity records are kept to provide the features you use until the information is removed or a verified deletion request is processed, subject to the limited retention described below. Requests are processed manually; submitting one does not immediately delete the account or associated data. We start verification promptly after receiving a request. For a request we can verify, we complete deletion without undue delay, no later than 30 calendar days after receipt or a shorter applicable legal deadline, and send completion confirmation to the email address linked to the account. If we need more information to verify control, we explain that promptly. During processing, we remove the sign-in account, associated profile and private online records, and remove the account’s public publications from new access. Copies already saved or exported by other people, including independent private drafts, cannot all be recalled. Deletion does not issue a purchase refund.

Limited retained records

Limited records may remain where necessary to prevent renewed access or fraud, document completion of a request, resolve a security or legal matter, or verify and restore purchased access. These records can include former and replacement account identifiers, hashes linking a purchase or recovery code, entitlement state, deletion or recovery status and relevant dates. They remain linked records rather than anonymous statistics. We keep a minimal log of completed deletion requests and purchase-recovery checks for up to 12 months after completion, unless a specific legal obligation or active dispute requires longer retention. Records that protect an active paid right or prevent repeated access or purchase misuse are kept only while needed for those purposes. We review that need at least once a year and remove records that are no longer necessary; an active purchase link is not automatically deleted with the 12-month operator log.

Deleting a CookWeave sign-in account does not automatically delete every purchase record held by Google Play or RevenueCat. Requests involving provider-held data must be reviewed with the relevant provider, subject to necessary, disclosed retention. Google Play controls its own store transaction records. We do not treat all provider records as an unrestricted exception to deletion.

Support messages and recovery files

We keep support correspondence for up to 12 months after a case is closed when needed for follow-up or a dispute, then remove it unless a specific legal obligation or active dispute requires longer retention. A raw recovery request can contain a purchase token and secret code, and its encrypted inbox copy also requires controlled retention. After verification is complete and the recovery case is closed, the operator removes the encrypted inbox contents and any operator-held raw request files, retaining only the minimum record of the result needed for the purposes above. Case closure and cleanup are manual operator actions; expiration of an identity proof or receiving window does not erase those materials automatically. Private copies you exported or kept with your own file provider remain under your control. Do not send a recovery file until support confirms that a protected channel is available and gives you its instructions. These materials are not public recipe content.

Your requests

You can contact info@dazlight.com to request access, correction or deletion of your account or support information, and to ask which limited records need to be retained and why. We may need to verify control of the account using a proportionate method. We do not ask you to send a password or payment-card details.

7. Delete your CookWeave account

You can request deletion without reinstalling CookWeave:

  1. Email info@dazlight.com with the subject “CookWeave account deletion request.”
  2. Identify the email address used for your CookWeave account, or provide the account identifier if you know it. Say that you want the account and its associated online data deleted. You do not need an internal identifier to make a request.
  3. We will verify control of the account and explain any necessary next steps. Do not send a password, card details, recovery code or purchase token in the initial message.

You can also start a request inside the app from Profile → Account → Request account deletion after confirming your identity. Requests are processed manually; opening an email link or submitting a request does not complete deletion. Your sign-in account, profile and associated private online data are removed during processing; public content is removed from new access. Limited security, deletion-audit and purchase-recovery records may remain as described above. Previously saved copies held by others cannot all be recalled.

Your local recipe book and exported files remain separate. Deleting an account does not refund a purchase. If support provides a recovery code before final deletion, save it securely, even if you do not currently have Pro. Do not purchase Pro again just to resolve an account-recovery problem.

We start identity verification promptly and complete a request we can verify without undue delay, no later than 30 calendar days after receipt or a shorter applicable legal deadline. We confirm completion by email to the address linked to the account. If verification needs additional information, we explain what is needed. The retention section above describes the limited records that may remain.

8. Security, children and changes

Protect your device, account and exported files with appropriate security settings. No method of electronic storage or transfer is perfectly secure.

CookWeave is not designed for children. If you believe a child has sent personal information through an account or support channel, contact us so we can address it.

We will update this policy and the “Last updated” date if CookWeave’s data practices change.