Your data plans your day. Nothing else.

• We collect what Cronch needs to plan your day: your account, your food and schedule preferences, and anything you choose to connect.
• We don’t sell your data, show you ads, or use third-party analytics or tracking cookies. We count page visits on our own servers without cookies, and keep only daily totals by page and referring site.
• Cronch never places food orders or charges you on behalf of a restaurant. “Order it” only opens a search; you check out yourself.
• You can delete your account and everything tied to it from Settings at any time.

Account

Your name, email address and a hashed password (we never store the password itself). Email verification and password-reset tokens are stored hashed and expire.

Your plan profile

Diet, allergies, cooking preference, meal budget, work hours, quiet hours, check-in cadence, water goal and time zone, plus the day plan Cronch builds from them and what you mark done, skipped or snoozed. This powers Today and History.

Calendar (optional)

If you paste meetings or connect a secret iCal link, we store the link and read only the start time, end time and title of today’s events to plan around them. We don’t write to your calendar.

Your Cronch mailbox

Every account gets a dedicated address on cronch.io. Messages sent to it are stored so you can read them in your Inbox; we pull out sign-in codes (for example from Resy) and, if you turn it on, forward a copy to an address you confirm. A forwarding address only takes effect after you click the link we send to it.

Reservation accounts (optional)

If you connect Resy, we store an encrypted session token from Resy, never your Resy password, and use it only to search, book and cancel when you ask. We keep the details of reservations you make through Cronch.

The agent

Messages you send to the Cronch agent (chat, ⌘K, or the MCP/CLI tools) are processed to answer you. We don’t keep a long-term chat history beyond what is needed to respond.

Billing

If you subscribe, Stripe handles your payment details. We store your plan, subscription status, renewal date, seat count and Stripe customer ID, never your card number.

Waitlist

If you join the waitlist we store your email, the option you picked, where you signed up from and the referring page.

Technical data

Like any web service we process IP addresses and request details to keep the service running and to rate-limit abuse. Errors are recorded in our own self-hosted error tracker so we can fix bugs; those reports can include the page or API route involved but are not used for anything else.

• To build and update your daily plan, send the check-ins you asked for, and route around your meetings.
• To suggest meals that respect your diet and allergies (allergen filtering also happens on our servers, not only in the AI model).
• To book, change or cancel reservations you request.
• To send account email: verification, password resets, check-ins, forwarded mail and receipts.
• To keep Cronch secure, debug problems and enforce plan limits.

We use a small number of providers, each only for the job listed:

Order links open Uber Eats, DoorDash or Google Maps with a search. We don’t send them any of your data; what you do there is covered by their own policies.

• Account, profile, plans and history: while your account exists.
• Mailbox messages: until you delete them or your account.
• Resy sessions: until you disconnect or they expire.
• Error reports: 30 days.
• Backups roll off within 30 days of deletion. Billing records may be kept longer where the law requires it.

• Delete: Settings → Delete account removes your account, profile, plans, mailbox and messages, connected accounts and API tokens, and cancels any subscription.
• Disconnect: remove a calendar link, Resy connection, forwarding address or API token at any time.
• Email: turn off email check-ins in your plan settings.
• Access or export: email us and we’ll send you a copy of your data.

Depending on where you live (for example under the GDPR or CCPA) you may have additional rights, including correction and objection. We honor these requests for everyone. Email [email protected] and we’ll respond within 30 days.

Traffic is encrypted in transit. Passwords are hashed, reservation sessions and secrets are encrypted at rest, one-click email links and inbound mail are signed, and access to production data is limited to the founders. No system is perfectly secure; if something goes wrong that affects your data, we’ll tell you promptly.

Cronch isn’t meant for children under 16, and we don’t knowingly collect their data. If you think a child has signed up, contact us and we’ll delete the account.

If we change how we handle your data in a meaningful way, we’ll update this page and email account holders before the change takes effect.

Questions or requests: [email protected].