Privacy, plainly.
A short, concrete account of what this site collects, why, how long I keep it, and how to reach me about it.
Updated 7 October 2026.
Who runs this site
I'm Arjun Dugar, and I run this site with The Breakfast Revolution (TBR), from Mumbai, India. I decide what this site collects and why, so I am the person responsible for it. If you have a question about your personal data or about this notice, write to me at arjun.a.dugar@gmail.com. Gifts are made on TBR's own donate page, under its own privacy terms. This site never sees a payment.
What I collect, and why
- If you make an account: your email address and the name you give me (with Google sign-in, the name and picture Google shares), to run your account. Your password is held by the sign-in service I use, and I never store it in readable form.
- Recipes: recipes you save, so you can see them again.
- Designing with Ojas: a record that your account made a recipe, and when, to keep the free service fair (more on that below). What you type to Ojas goes to Anthropic, the AI provider behind it, so it can answer.
- Chats with Ojas: I keep each chat, so I can find where Ojas goes wrong and fix it. The section “Chats with Ojas” below says exactly what.
- Partnership enquiries: the name, work email, company, role, budget, message and tier you send from the partners page, so I can reply. A copy may be emailed to the people who handle partnerships.
- The update list: your email address, so I can send occasional news about the recipes and the programme.
- Certificates: when The Breakfast Revolution confirms a gift and a certificate is issued, the name printed on it, the amount, the number of children and the date. Anyone with the certificate's link can see these. That is what lets it be verified.
- How the site is used (the usage log): which pages are viewed, which buttons are used (including the link to TBR's donate page), how far people scroll, the site a visit came from, the type of device, and the approximate location of a visit (country, region and city, from my host's network data).
- How visits are told apart: two random identifiers stored in your browser (one per visit, one per browser) that contain nothing about you, and a form of your IP address scrambled with a secret key and the day's date, so it changes every day and cannot be turned back into the address.
- After a donate click: if you come back, I may ask once whether you completed a gift. Answering is optional and records only yes or no.
Cookies and browser storage
Signing in sets cookies that keep you signed in. The usage log keeps its two random identifiers in your browser's storage. One more cookie holds a random number that I use only for the recipe limits, explained below. I use Microsoft Clarity to see how visitors move through the site: it records clicks, scrolling and the pages you visit, and makes heatmaps from them. It hides anything you type, and it never runs on the admin pages or on a gift certificate. Clarity sets its own cookies to do this. I run no advertising trackers.
Who else handles it
Supabase (my database and sign-in), Vercel (hosting and page counts), Microsoft (Clarity, the recordings and heatmaps described above), Anthropic (the AI behind Ojas), Upstash (a small store that holds one-way request counters) and, when switched on, Resend (partnership emails). Cloudflare runs a quick check that you are a person, on the sign-up and sign-in forms. Google handles your sign-in if you choose it. Its button loads from Google's own servers on any page that offers Google sign-in, so Google can see that your browser opened that page. Each of them handles data only to run its service for me, and some process it outside India. I do not sell data.
How long I keep it
- Your account, your saved recipes and the record that you made a recipe: until you delete them or ask me to.
- The usage log, the recipe-limit records and chats with Ojas: until you ask me to delete them. Nothing is deleted automatically.
- The request counters, which stop one visitor from flooding the site: a day at most. They expire by themselves.
- Partnership enquiries, the update list and certificates: until the person asks me to delete them. TBR can also withdraw a certificate, and its link then stops showing it.
Children
Anyone can make an account, including students under 18. If you are under 18, please check with a parent or guardian before you sign up. A parent or guardian who wants a child's account or data deleted can write to me, and I will delete it.
Ojas and the one-recipe-a-week limit
Each person with an account can design one recipe a week with Ojas. To keep that fair without storing your email address or your IP address, I keep one record for each recipe designed: your account, and three one-way codes made from your email address, from a random number kept in a cookie on your browser, and from your network address. A one-way code cannot be turned back into the email, the number or the address, and the network code changes every week. That cookie holds only the random number, lasts up to 400 days, and is used only for the recipe limits. I keep these records until you ask me to delete them. Each recipe you design is also saved to your account, so you can download it again. Words you type to Ojas are sent to the AI provider to be read, and I keep the chat, as the section “Chats with Ojas” explains. A dish name you ask for can appear on your recipe card, and the card is saved to your account.
Chats with Ojas
What I keep. For each turn of a chat: the words you type and the choices you tap, what Ojas says back, what it understood from you (the breakfast choices it picked out), whether anything went wrong, how long it took, and the recipe card if one was made. I do not keep your name, your email address or your IP address with a chat. A chat is filed under the account's number. Before a chat is saved, anything that looks like an email address or a phone number is replaced by a marker, but please do not type names or a child's details.
Why. To find where Ojas goes wrong: a question it misreads, a poor answer, a refusal that should not have happened, an error. I read chats to fix those things. I do not use them for advertising and I do not sell them. This store is separate from the usage log, which never holds anything you type.
How long. Until you ask me to delete them. If you ask me to delete your account, its chats go with it.
Who can read them. Only the site's admins: me, and the people at The Breakfast Revolution I have given the admin console. The database itself refuses everyone else, and the public key this site uses in your browser can neither read nor write them. The AI provider, Anthropic, also sees what you type, as explained above.
To have a chat deleted. Write to me at arjun.a.dugar@gmail.com with the subject “Data request”. A chat is filed under a number, not a name, so tell me roughly when you chatted and what you asked, and the email address of your account if you have one, and I will find it and delete it.
Your data, your call
You can ask me what I hold about you, ask me to correct, update or delete it, take back a consent you gave (leaving the update list, for example), and name someone to do this for you if you cannot.
Write to me at arjun.a.dugar@gmail.com with the subject “Data request”. I reply within 30 days. If you are not satisfied with my answer, you can complain to the Data Protection Board of India.
What I do not do
I do not sell data or run advertising trackers. I never keep your IP address in readable form, and nothing on this site asks a child for their details. The full giving story, including what this site can and cannot see, is on the Give page.