Privacy Policy
1. Overview
This Privacy Policy explains what information KetoSense, operated by Aria Commerce (Exempt dealer under Maayan Milevsky Bassan) ("we," "us"), collects when you use the KetoSense app (the "App"), how we use it, and your choices. By using the App, you agree to the practices described here.
2. Information We Collect
Account information: email address and display name, collected at sign-up.
Health-screening answers: responses to a small set of contraindication questions (including pregnancy, insulin-dependent diabetes, and eating disorder history) shown before you can use the App, plus the timestamp of your acknowledgment. Used solely to show appropriate in-app guidance — never sold, never used for advertising.
Body metrics and goals: age, gender, height, weight, activity level, goal weight, and your stated motivation — used to calculate personalized macro targets.
Dietary restrictions: any restrictions/allergies you enter, used to constrain AI Chef recipe generation and, where relevant, sent to our AI provider as part of that generation request.
Logged meals: meal descriptions (text you type or speak), timestamps, and estimated macros. If you attach a photo to help estimate a meal, it is sent to our AI provider for that one estimate and is not stored afterward — see "Third-Party AI Processing" below.
AI Correction Data: When you manually adjust the nutritional macros of a meal logged via our AI, we store your original input and the corrected macros indefinitely. This data is securely stored in your personal profile and is not shared with other users.
Usage analytics: in-app events (e.g., which screens are opened, where onboarding is abandoned, whether a paywall is viewed) via PostHog, tied to an anonymized account identifier — never including your logged-meal content or health-screening answers.
Diagnostic/crash data: technical crash reports via Sentry, including your account identifier so we can investigate an issue tied to your account, plus device/OS information and a stack trace. Sentry does not receive your logged meals, health-screening answers, or dietary restrictions.
Purchase data: subscription status, AI-credit top-up purchases and balance, and transaction identifiers from Apple/Google's in-app purchase systems (processed via RevenueCat) — we do not receive or store your payment card details; those are handled entirely by Apple/Google.
3. How We Use Information
We use your information to: provide and personalize the App's core features (macro targets, meal logging, AI Chef, insights); operate AI meal extraction and recipe generation; maintain and improve the App (analytics); diagnose and fix crashes; enforce daily usage limits on AI-powered features; and communicate with you about your account.
We do not sell your personal information, and we do not use your logged meals or health-screening answers for advertising.
4. Third-Party AI Processing (OpenAI and TypeSafe)
When you use natural-language meal logging or AI Chef, the text you type (and, for AI Chef, your saved macro targets, stated goal, and dietary restrictions) is sent to OpenAI's API to generate a macro estimate or recipe. This request is made server-side, through our own backend — OpenAI never receives your raw account identity or email.
Personalized AI Memory: To improve your future AI meal logging, we explicitly use your past manual corrections. If you correct an AI-generated meal, we inject that correction into your future requests to OpenAI so the system learns your preferences. This injected data is strictly isolated to your account; your corrections are never used to train global models or injected into other users' prompts.
If you attach a photo instead of (or alongside) typing, that photo is sent to OpenAI for that single estimate and is not retained by us afterward — we do not store meal photos.
This processing is subject to OpenAI's own data-usage terms for API traffic, which at the time of writing state that API inputs and outputs are not used to train OpenAI's models by default.
OpenAI also powers nutrition-label photo scans, recipe import, and AI recipe images, receiving only the content needed for that request (the label photo, the recipe page or text, or the recipe title and ingredients).
TypeSafe: To evaluate and improve how accurately we match ingredients to USDA nutrition data, we send the short ingredient name (for example, "heavy cream") and the matching USDA food descriptions to TypeSafe's API. This request is made server-side and does not include your account identity, email, meal descriptions, photos, health-screening answers, or body metrics. Its result does not change the nutrition values you see.
If AI processing is unavailable, the App falls back to a local, non-AI estimator that never leaves your device.
5. Cloud Storage & Security
Your account data, logged meals, and saved recipes are stored with Supabase (built on PostgreSQL), a third-party cloud infrastructure provider. Data is encrypted in transit (TLS) and at rest. Access is enforced with row-level security, so your data is readable only by your own authenticated account — not by other users, and not by unauthenticated requests.
6. Data Retention
We retain your data for as long as your account is active. If you delete your account (available anytime in Settings), your account and all associated data — logged meals, saved recipes, health-screening answers, body metrics — are permanently deleted immediately. This action cannot be undone. See Delete Your Account for step-by-step instructions.
One exception: a one-way cryptographic hash of the email address is kept indefinitely, separate from the deleted account, solely to detect repeated free-trial sign-ups on the same address. This hash cannot be reversed back into the original email, but it is pseudonymous, not anonymous — it can still be matched against a future signup using the same email address. It is never used for any purpose other than trial-abuse prevention.
7. Your Rights
Depending on your location, you may have rights to access, correct, export, or delete your personal information. You can:
- Delete your account and all data anytime from Settings — self-service, immediate, and permanent. See Delete Your Account.
- Request a copy of your data by contacting ketosense.app@gmail.com.
- Correct inaccurate information directly in the App (Settings) for most fields.
8. Children's Privacy
KetoSense is not directed at children and is not intended for use by anyone under 16. We do not knowingly collect personal information from children. If you believe a child has provided us information, contact ketosense.app@gmail.com and we will delete it.
9. International Data Transfers
Our service providers (Supabase, OpenAI, TypeSafe, PostHog, and others listed below) may process data in countries other than your own. Where required by law, we rely on appropriate safeguards (such as standard contractual clauses) for these transfers.
10. Third-Party Service Providers
| Provider | Purpose | Data involved |
|---|---|---|
| Supabase | Auth, database, cloud storage | Account, meals, macros, recipes, AI-credit balance and usage |
| OpenAI | AI meal-macro extraction, AI Chef recipe generation and import, nutrition-label scans, recipe images | Meal/recipe request text, meal and label photos (not stored), macro targets, stated goal, dietary restrictions, and your past AI corrections |
| TypeSafe | Evaluating ingredient-to-USDA matching accuracy | Short ingredient names and USDA food descriptions only (no account identity) |
| PostHog | Product analytics | In-app usage events, anonymized identifier |
| Sentry | Crash/error reporting | Crash data, device info, account identifier |
| RevenueCat | Subscription and AI-credit purchase management | Account identifier, purchase/subscription status, AI-credit purchases, transaction identifiers |
| Apple App Store / Google Play | Subscription and AI-credit billing | Purchase/subscription status |
11. Changes to This Policy
We may update this Privacy Policy from time to time. Material changes will be notified in-app or by email before taking effect.
12. Medical Disclaimer
KetoSense is not a medical device and the information it collects and generates is not used to provide medical advice or diagnosis. See the Terms of Service for the full medical disclaimer. Health-screening answers are used only to display in-app guidance and are never used for any clinical decision-making by us.
13. Contact
Questions about this policy or your data: ketosense.app@gmail.com.