Privacy Policy

1. Account information

To create and verify your account, we process your email address, account identifier and the name you provide. If you choose Google sign-in, Google provides the authentication service with the basic account information you authorize, which may include your name and profile picture.

If you set a password, the authentication service processes the relevant credentials to provide email-and-password sign-in.

2. Calculations and cloud data

Your browser may store calculation drafts, default units, interface preferences and unfinished save operations. If you choose cloud saving, your ingredients, prepared ingredients, recipes, costs and related settings are stored under your account for later access, editing, calculation and recovery.

3. Browser storage and technical information

The product uses necessary cookies and browser storage to maintain sign-in, verify authentication returns, preserve drafts and recover operations.

The application and infrastructure services may process request times, IP addresses, device or browser information and error records to provide the service, investigate faults and protect access. Clearing site data may remove local drafts or your sign-in state.

4. Third-party services

Supabase provides authentication and cloud database services. Google provides the third-party sign-in option you may choose to use. Each provider processes necessary data for its role.

When security verification is enabled, Cloudflare Turnstile helps detect automated abuse on email/password sign-in and account recovery forms. Cloudflare processes the browser's challenge interaction and technical signals needed for this check; Supabase validates the resulting token. Our application does not store challenge tokens as account or recipe data.

Providers, storage regions, cross-border transfer arrangements and the email-delivery service will be verified and documented before public release.

The links below are the providers' own information. Supabase's Data Processing Addendum describes its customer-data processing terms. This product remains responsible for explaining and managing its own data processing.

• Cloudflare Turnstile Privacy Addendum
• Google Privacy Policy
• Supabase Data Processing Addendum
• Supabase Privacy Policy

5. Your choices

You can change your account name, choose to set or change a password, manage cloud records with the available backup and individual-record deletion features, and clear site data in your browser.

Use the feedback form for a privacy or account-deletion request and include a reply email if you want a response. We must verify identity before account changes. Deleting cloud records, clearing local drafts and deleting an account each affect different data.

Optional usage statistics and feedback

Feedback works without signing in and without Turnstile. Only your chosen category, text, optional reply email and a fixed page category are submitted. Do not include passwords, private recipes or sign-in links. Authorized operators can privately review and mark feedback; a reference number does not grant access to its contents.

Usage statistics are optional and off until you allow them under Usage statistics in the footer. Only after consent do we create a signed first-party 30-day browser identifier. No advertising or session-replay SDK is used. Events contain fixed actions, page categories, coarse device/source categories and safe error codes, never email, names, recipe or ingredient names, amounts, inputs, URL queries, tokens or full referrers.

After consent, short-lived anonymous session, calculator-task and save-flow identifiers pair ordered steps and elapsed time. A bounded browser outbox and save-flow continuation expire within 24 hours. Task state continues across reloads until 30 minutes idle or draft replacement. Withdrawal clears this optional local context. Reports use observed browsers and mature observation windows, not cross-device people.

Routine usage events from anonymous and signed-in visits use the same consenting-browser measure and do not contain raw account IDs. New-account confirmation separately uses a salted account digest for 35-day deduplication, without joining browsers across devices. Devices, blocked storage and cleared cookies limit browser deduplication. New-account confirmation is counted once only for a real verified account created after instrumentation began, within its first 30 days, and with consent; it is not a count of every login or all registrations. Test, staging and example activity are separated from normal production reports.

You may withdraw consent in Usage statistics at any time. This removes the optional cookie and stops future collection; previously collected events follow the expiry schedule below. Browser draft and sign-in storage are separate. To limit abuse without blocking feedback behind a challenge, the application keeps daily HMAC network digests rather than raw IP addresses in its business database. Hosting providers may independently process request IPs and logs.