Gramo — Privacy Policy
Simple summary: your photos are never stored. Your meal data is yours. We never sell it.
1. Summary
Gramo uses AI to analyse your meals from a photo or text description and log your calories and macros. Meal data is stored in the cloud so it syncs across your devices. We never sell your data or use it for advertising.
2. Information We Collect
2.1 Account Data
Gramo requires an account to sync your meal history. When you sign up, we collect your email address and a securely hashed password, stored in Supabase and used solely for authentication.
2.2 Meal and Nutrition Data
Meals you log — descriptions, calorie estimates, macros (protein, carbs, fats), portion sizes, meal categories, and timestamps — are stored in our Supabase database linked to your account. This data powers your history, daily totals, and trends screens.
2.3 Photos and Food Descriptions
When you photograph a meal or type a description, that input is sent to our AI service (powered by Google Gemini) to estimate calories and macros. Photos are not permanently stored on our servers after the AI analysis completes. Text descriptions used for AI parsing are not retained beyond the duration of the API request.
Google’s data practices for Gemini API inputs are governed by Google’s Privacy Policy.
2.4 Analytics (PostHog)
We use PostHog to collect anonymized usage analytics, including screens visited, feature interactions (e.g. photo capture started, meal logged, history viewed), app version, and platform. This data helps us understand which features are useful. PostHog analytics do not include the content of your meals or photos.
PostHog’s privacy policy: posthog.com/privacy.
2.5 Crash Reporting (Firebase Crashlytics)
We use Firebase Crashlytics to collect crash reports and error logs. Crashlytics may collect device type, OS version, app version, and stack traces at the time of a crash. This is used exclusively to diagnose and fix bugs.
Google’s privacy policy (covering Firebase): policies.google.com/privacy.
2.6 Permissions
| Permission | Purpose | Required? |
|---|---|---|
| Camera | Photograph meals for AI analysis | Optional |
| Photo Library | Upload meal photos from gallery | Optional |
You can revoke any permission at any time in your device Settings. Revoking camera or photo library access only disables photo-based logging; you can still log meals by typing a description.
3. How We Use Your Information
| Data | Purpose |
|---|---|
| Account data | Authentication and account management |
| Meal and nutrition data | Display history, totals, trends, and calorie targets |
| Photos and descriptions | Sent to AI for calorie/macro estimation; not retained after response |
| Analytics events | Improve app features and user experience |
| Crash reports | Identify and fix bugs |
We do not sell your data, use it for advertising, or share your meal content with any party other than the AI parsing service described above.
4. Data Storage and Retention
- Meal data is stored in Supabase (cloud). You can delete individual meals or your entire account at any time from within the app.
- Account data is deleted when you delete your account.
- Analytics and crash data are retained by PostHog and Firebase per their own retention policies.
- AI parsing inputs (photos and text) are not retained on our servers after the response is returned.
5. Children’s Privacy
Gramo is not directed at children under 13 (or under 16 in the EEA). We do not knowingly collect personal information from children. If you believe a child has provided us information, contact us and we will delete it promptly.
6. International Users
Our servers and third-party providers (Supabase, Google, PostHog) may process data in the United States or other countries. By using Gramo, you consent to this transfer.
7. Your Rights
Depending on your location, you may have rights to access, delete, or opt out of collection of your personal data. You can delete your account and all associated meal data from within the app. For other requests, contact: indiebuilderasad@gmail.com.
8. Security
All data transmitted to our servers uses HTTPS encryption. Passwords are hashed and never stored in plain text. Your meal data in Supabase is protected by row-level security policies.
9. Changes to This Policy
We may update this policy as the app evolves. We will update the “Last updated” date at the top. Continued use of the app after changes constitutes acceptance of the updated policy.
10. Contact
Muhammad Asad Shoaib / Meridian&
Email: indiebuilderasad@gmail.com