Your food diary stays yours.

Last updated: September 12, 2026

Information we collect

Atlas Calories collects the information needed to provide a calorie and meal diary:

• Account information: your email address and password are handled by Supabase Auth when you create an account or sign in.
• Diary information: meals, diary entries, calories, nutrition values, goals, and dates that you enter or save.
• Custom content: custom foods and saved meals that you create.

Camera, barcode, and nutrition-label scanning

Atlas Calories requests camera access to scan food barcodes and, when you explicitly choose the nutrition-label feature, to take a photo of a nutrition label. Barcode scans do not capture or store images. The app does not record video or use the camera for facial recognition or advertising.

Food data providers

Atlas Calories uses curated reference food data and may query USDA FoodData Central for food searches. Barcode lookups may use Open Food Facts. Open Food Facts results are live, unverified data and are shown with attribution. Open Food Facts data is available under the Open Database License (ODbL).

When you scan a barcode, the barcode and lookup request are sent to the service needed to return a result. Results are not inserted into the shared Atlas food catalog as verified foods. Temporary lookup cache records may be retained to improve reliability and limit provider requests.

When you choose AI extraction, the nutrition-label photo is sent to Google Gemini to extract food and nutrition text. Atlas does not intentionally retain the submitted photo. If you save the extracted food, the values you confirm are stored with your custom food. Google processes the photo under the Gemini API Terms and Google Privacy Policy. Google controls its own processing, retention, and other practices; review those documents before using the feature. AI-assisted results may be inaccurate.

Community foods

Foods you create are private by default. If you choose to share a food with the community, its name, brand, barcode, aliases, serving information, nutrition values, and provider information become visible to other Atlas Calories users. Public community foods are unverified and may be reviewed, corrected, or removed if they are inaccurate or violate content rules.

How we store and protect information

Account and diary data are hosted by Supabase. Access to your private records is protected by authentication and PostgreSQL row-level security policies. Your records are associated with your account and are not sold or used for targeted advertising.

Retention and deletion

We retain your account and personal diary data while your account is active or until you request deletion. In the app, Profile > Delete account permanently removes your Supabase Auth account. Database foreign-key cascade rules then remove the associated profile, diary entries, custom foods, and saved meals. No storage objects are used for account data.

If you cannot use the app, submit a request through the account deletion page. We aim to handle those requests within approximately 72 hours. Limited copies may remain temporarily in secure backups or logs as required for security, fraud prevention, or legal obligations, and are removed according to the provider's retention cycle.

Your rights

You may access and manage your data in the app, request deletion, and ask questions about how your information is handled. To report an inaccurate or inappropriate public food, contact us and include the food name, barcode, and issue. We may ask for account information to verify a deletion request before acting on it.

Contact

For privacy or deletion questions, contact caloriesatlas@gmail.com.