Legal & disclaimers.
Privacy policy.
edible·factor (“we”, “us”) takes your data seriously. This policy explains what we collect, why, and your rights under India's Digital Personal Data Protection Act 2023 and GDPR (where applicable).
What we collect
- Account data. Your email address and password, and your name if you give us one. If you use Sign in with Google instead, Google passes us your Google account email and basic profile.
- Profile and goals. Age, sex, height, weight, activity level, dietary preferences, and the daily calorie and budget targets worked out from them.
- Usage data. Dishes added to your plate, meals you log, what you spent, favourites, and the timestamps of each.
- What you submit to the AI features. Menu and dish photos you scan, and the free text you type into the assistant or the quick meal log. See AI features below.
- Connection data. Your IP address and browser user-agent reach our edge on every request, as they do for any website. We use the IP address for one thing only: rate-limiting sign-in attempts.
- Location. Only the Bengaluru area you pick yourself from a short list, used to sort restaurants by distance. The coordinates we keep are the centre of that area, not your device's position. The app never asks your device for GPS: browser geolocation is switched off outright by the
Permissions-Policyheader we send on every page.
What we do not collect
- We do not collect or process payment data. Checkout is not live in this app today.
- We do not collect medical records or diagnoses.
- We do not sell your personal data to third parties.
How we use it
- To recommend dishes that fit your stated calorie and budget targets.
- To remember your plate between sessions.
- To count page views so we know which screens get used.
AI features
When you scan a menu or a dish, ask the in-app assistant a question, or log a meal in plain English, what you submit is sent to Google's Gemini API to be read and turned into nutrition estimates. That means the photo itself, the text you typed, and, in the assistant, your first name and your calorie and macro totals so far today.
The app does not keep the photo once the scan returns. What Google does with what it receives is governed by Google's own terms, not by this policy.
Who else handles your data
Everyone on this list was checked against what the app actually does. Nobody is listed speculatively.
- Cloudflare, Inc. hosts and serves this app and sits in front of every request to it. It sees connection data (IP address, user-agent, the URL requested) and runs the page-view counter described under Cookies.
- Google LLC (Gemini API) receives whatever you submit to the AI features above.
- Google LLC (Sign in with Google) handles the sign-in itself, if you choose that option.
- MongoDB Atlas is the managed database our own API writes your account, profile, and meal records to.
- Edible Factor's own API at
api.ediblefactor.com, which runs on a server we operate.
How long we keep it
- Sign-in cookie. The
ef-sessioncookie lasts no longer than the access token inside it, and never more than 48 hours. A guest session (ef-guest) lasts 24 hours. Signing out deletes both immediately. - In your browser. Your plate, daily targets, logged meals, spend, favourites, profile photo, the area you picked, and your assistant chat transcript are stored in
localStorageon your device. Signing out erases all of them; so does clearing browser data. - On our side. Account, profile, and meal records are kept until you ask us to delete your account.
Your rights
- Request access to all data we hold about you.
- Request correction or deletion of your account at any time.
- See Cookies for what gets measured and how to stop it.
- Lodge a complaint with the relevant data protection authority.
Email privacy@ediblefactor.com for any data request. We respond within 30 days as required by law.
Terms of service.
By using edible·factor, you agree to these terms. If you do not agree, do not use the service.
The service
edible·factor helps you browse partner restaurant menus in Bengaluru with calorie and budget tracking. We do not own the restaurants or prepare the food. Menu data, prices, and availability are provided by partners and may change without notice.
Your account
- You are responsible for keeping your password and your sign-in email account secure.
- One account per person. Sharing is not permitted.
- You must be at least 18 to place orders.
Orders & payments
- Orders are contracts between you and the restaurant; we facilitate the connection.
- Prices include taxes unless otherwise stated. Delivery fees shown at checkout.
- Cancellation, refund, and dispute policies follow the partner restaurant's terms; we mediate where possible.
Acceptable use
You agree not to: scrape data, attempt unauthorized access, impersonate others, or use the service for unlawful purposes.
Liability
Calorie and macro data are estimates and not medical advice (see Dietary Disclaimer).
Changes
We may update these terms. Material changes will be emailed to active users at least 14 days before they take effect.
Cookie policy.
We use the smallest set of cookies that lets the product work. Most data is stored in your browser's localStorage, not server cookies.
What we use
- Essential. The
ef-sessioncookie after sign-in, oref-guestif you continue as a guest. Cannot be disabled if you want to stay signed in. - Functional. Your plate, daily targets, logged meals, favourites and assistant chat transcript, all in
localStorage. Erased when you sign out or clear browser data. Your dietary preferences are not kept here: they are saved to your account on our server. - Measurement. Cloudflare Web Analytics counts page views from our edge. It sets no cookie and does not follow you to other sites.
Manage your choices
You can clear cookies and localStorage at any time via your browser's settings, and signing out erases both session cookies and the stored data listed above straight away. There is no in-app analytics toggle and no cookie banner today; blocking static.cloudflareinsights.com in your browser or an extension stops the page-view counter.
Dietary disclaimer.
Calorie and macro estimates shown in edible·factor are for informational purposes only. They are not medical or nutritional advice. Always consult a qualified healthcare professional or registered dietitian before making dietary decisions, especially if you have a medical condition, are pregnant, or are managing weight, blood sugar, or cholesterol.
How we estimate
Nutrition values come from one of three sources, surfaced per dish:
- Restaurant-provided values, where the partner has lab-tested or verified.
- USDA FoodData Central reference values for component ingredients.
- Estimated values from typical preparation methods. These can vary by ±15% from actual servings.
Allergens
We do not currently surface allergen flags. Always confirm with the restaurant if you have a serious allergy.
Not for medical use
edible·factor is not a medical device and is not intended to diagnose, treat, cure, or prevent any disease. Any reference to “protein gap”, “calorie cap”, or similar terms is informational, not diagnostic.
Contact us.
- General - hello@ediblefactor.com
- Privacy / data requests - privacy@ediblefactor.com
- Partner restaurant inquiries - partners@ediblefactor.com
- Bengaluru, India