Effective 27 May 2026.
Meri Kitchen is a small mobile app for households who plan, cook, and eat together. We collect only what we need to make it work for you and the people in your household. We don't sell your data. We don't run ads. We don't track you across the internet. If you want your account gone, you can delete it yourself — from inside the app or on this website.
Meri Kitchen is built and operated by Ravi Agarwal, based in India. It is an independent personal project. You can reach me at flideravi@gmail.com for anything related to your data or this policy.
Meri Kitchen uses Google Sign-In. When you sign in, Google passes us your name, email address, profile photo URL, and a stable user ID. We use these to identify you across devices, show your initials and photo in your household, and email you about things that affect your account.
Everything you create inside the app belongs to your household. That includes the household name, the members you add (their names, initials, colors), your recipes (titles and the prose you write), your weekly meal plans, and your shopping list. We also keep a short-lived invite code for each household so members can join.
Your device also stores your theme preference (light, dark, or system) locally. That never leaves your phone.
If you joined the pre-launch waitlist on meri.kitchen, we kept your email address so we could tell you when the app is ready. That's the only thing the website collects.
No analytics. No usage telemetry. No location. No contacts. No advertising identifiers. No microphone, no health data, no financial info. The app does not phone home about what you tap or how often.
All of your app data is stored in Google Firebase (Cloud Firestore for content, Firebase Auth for sign-in). Firebase is operated by Google Cloud and is the only company besides me that processes your data on our behalf. Data is encrypted in transit and at rest by default.
Your data is scoped to your household. Other Meri Kitchen users — strangers, people from other households — cannot see your recipes, plans, members, or shopping list. The only way someone joins your household is with your invite code, and invite codes expire automatically.
For as long as you keep your account, your data stays. When you delete your account, we delete your user record and remove you from your household. If you were the only person in your household, we delete the household and everything in it — recipes, plans, shopping list, members.
Waitlist emails on this website are kept until launch outreach is complete, then deleted.
You can see your data anytime: it's everything visible inside the app for your household.
You can correct any of it from inside the app — edit your recipes, change your member info, update your plan, anything.
You can delete your account in two ways:
Either path removes the same things: your user record, your membership in your household, and (if you were the last member) the entire household and its contents. The deletion is immediate and permanent.
If you'd rather email me directly, write to flideravi@gmail.com and I'll process the request myself.
Meri Kitchen is not directed at children under 13, and we don't knowingly collect data from them. Households often include kids — a child's name might be a household member, marked with a color — but that's a name typed by an adult, not an account a child controls.
Data is encrypted in transit (HTTPS) and at rest. Access from the app is gated by Firebase Authentication; only signed-in members of a household can read or write that household's data. Invite codes are short, time-limited, and easy to rotate.
Nothing is perfectly secure. If something happens that affects your data, I'll tell you directly.
If we change anything meaningful about what we collect or how we use it, the new policy will be posted here with a new effective date, and we'll let you know in the app before the change takes effect.
Questions, complaints, requests, second thoughts — flideravi@gmail.com. I read everything.