Kitchenly
Privacy Policy
Last updated 9 September 2026
Kitchenly plans meals for a household. To do that it has to hold some information about you and the people you cook for. This page says exactly what that is, where it goes, and how to get rid of it. It is written to be read, not to be survived.
Who we are
Kitchenly is operated by Kritika Sharma, India. For anything on this page, write to kitchenlysupport@gmail.com.
What we collect
- Your phone number. It is how you sign in, and it is the only identifier we require. We never ask for a password.
- Your name and profile picture, if you set them.
- Household details you enter: the members you cook for, their names, and who is allowed to change the plan.
- Health and dietary information for each member, all of it optional except what you choose to give: height, weight, age, sex, activity level, health goals, calorie and protein targets, diet type, allergies, and disliked foods.
- What you plan, cook and buy: meal plans, recipes you save or create, pantry contents, grocery lists, meals logged, supplements logged, and ratings.
- Content you submit: photos of food or ingredients, voice notes, and recipe links you ask us to import.
- Details of a cook or house manager you employ, if you add one: their name, phone number, photo, working days, salary, and — only if you choose to attach one — a photo of an identity document. Only add someone else's details, and only attach an identity document, with that person's knowledge and permission. You can delete any of it from their profile at any time, and you do not have to provide any of it to use Kitchenly.
- A device push token, if you allow notifications.
- Basic technical logs: IP address, request times and error traces, kept so the service can be operated and abuse can be stopped.
Health data. Allergies, weight and health goals are sensitive. We use them for one purpose — filtering recipes and calculating nutrition inside your household. We do not use them for advertising, and we do not sell them. There is no advertising in Kitchenly at all.
Identity documents. If you attach a photo of a cook's ID, it is stored only so it appears on their profile in your own household. Nobody outside your household sees it, it is never sent to any third party, and it is not read, verified or used for anything else. You never have to attach one, and deleting it removes it.
Who else sees it
We do not sell your data and we do not share it for anyone else's marketing. We use a small number of service providers, and each one only receives what it needs to do its job:
- Twilio — receives your phone number to send the sign-in code, and your cook's number plus the menu when you send one over WhatsApp or SMS.
- AI providers (Google Gemini, Groq, Cerebras, OpenRouter) — receive recipe text, the ingredients or photo you submit, and the relevant parts of your preferences when you use the assistant, import a recipe, or generate a cook message. We send the minimum needed for the request, not your whole profile.
- Apple and RevenueCat — handle subscription purchases and tell us only whether your household's subscription is active. We never see your card details.
- Expo — delivers push notifications to your device.
- Fly.io — hosts the servers and the database.
We will also disclose information if the law genuinely requires it.
Other people in your household
A household is shared by design. Anyone in your household can see the household's meal plan, recipes, pantry and grocery list, and the profiles of the members in it — including their dietary and health details. Only add someone to a household if that is what you both want. The primary member can remove anyone at any time.
How long we keep it
We keep your data while your account exists. You can delete your account from Profile at any time; doing so removes your account, your household's data, and the content you added.
One thing survives deletion, and only one: a one-way, salted hash of your phone number, kept so that the same number cannot claim the free trial repeatedly. It is not reversible into a phone number, it is not linked to anything else, and it is used for nothing but that check.
Security
All traffic between the app and our servers uses HTTPS. Sign-in is by a one-time code sent to your phone; sessions are held as revocable tokens. No system is perfectly secure, but we do not store passwords or payment details at all, which removes the two things most worth stealing.
Your rights
You can see and edit almost everything from inside the app. You can also ask us to send you a copy of your data, correct it, or delete it, by writing to kitchenlysupport@gmail.com from the phone number on the account or in a way we can reasonably verify. We will respond within 30 days.
Children
Kitchenly is not intended for children under 13, and we do not knowingly create accounts for them. You may add a child as a household member — a profile you manage, with no phone number and no account of their own. If you believe a child has created an account, write to us and we will remove it.
Where your data is held
Our servers and the providers listed above operate internationally, so your data may be processed outside your country. We only use providers that commit to protecting it.
Changes
If we change what we collect or who we send it to, we will update this page and change the date at the top. Significant changes will be announced in the app.