trackcalr.Open Trackcalr
TRACKCALR

Privacy policy

How Trackcalr uses and stores your information. Updated 14 October 2026.

Who to contact

This policy covers Trackcalr at trackcalr.app and its connected-assistant tools. For privacy questions, access or correction requests, or account deletion, contact the app developer at [email protected].

Google sign-in and your profile

When you sign in with Google, Google provides basic account information, including an account identifier, email address, name and profile image if available. Supabase processes sign-in and manages your account and session. Trackcalr uses this information to identify you, associate your saved data with your account and provide account support. We do not receive your Google password or request access to Gmail, contacts or Drive files.

Your calorie-planning profile includes the details you enter, such as your name, date of birth, height, weight, activity and goals. We use these details to calculate and display your daily plan.

Meals, photos and local storage

When you save a meal with a Google account, its foods, portions, nutrition, notes, description, analysis explanation and any saved photo are stored with your account in Supabase. Meal photos use private storage. The app uses browser storage for sign-in sessions, preferences, draft recovery and draft photo bytes.

A local profile stores its profile, journal and photos in your browser instead of syncing them to your Google account. Clearing this site's browser data can permanently remove that local journal and unsaved drafts. Choosing an AI provider still sends the input you ask it to analyze to that provider.

AI analysis and food references

When you request managed analysis, Trackcalr sends your photo, description or both through its server to OpenRouter and the selected model provider. Food names and preparation details may also be sent to USDA FoodData Central to find nutrition references, and candidate matches may be sent to a model for selection. These services process requests under their own data policies.

If you choose your own OpenRouter or custom provider, the browser sends the analysis request directly to that provider. Personal provider keys are kept in the current app session. Review your chosen provider's policy before sending information you consider sensitive.

Completed managed scans from Google accounts are kept privately for 30 days for troubleshooting and improving estimate consistency. These records include the submitted photo and description, AI response, reference candidates, selection explanations, calculations and final result. They are separate from your journal and can exist even if you discard a draft or delete the saved meal. Local-profile and personal-provider scans are not included in this cloud scan archive.

The app developer can review these private records for investigation. They are not available through public pages or connected-assistant tools. Expired cloud records are removed by scheduled cleanup; investigation exports require separate cleanup.

Connected assistants

If you connect an assistant such as ChatGPT or Claude, it can read the account data covered by the permissions you approve, including your nutrition goals and journal, and add meals when authorized. Data returned to an assistant is then handled under that service's policies. You can revoke a connection in Settings. Revoking access does not remove information already received by the assistant.

Service providers and operational records

Trackcalr uses Supabase for authentication, account data and private photos; Railway for hosting; Cloudflare for domain services; and Better Stack for operational logs. Managed analysis uses OpenRouter, its selected model providers and USDA FoodData Central. Providers may process data outside your country.

Application logs contain technical details such as request identifiers, timings, model names, error categories and status codes. The application does not include photos, meal contents, account identifiers, tokens or raw provider responses in these logs. Hosting and authentication providers may separately process connection and security information such as IP addresses.

We do not sell your Google account information or use it for advertising. We use it to provide the account features described here.

Retention and your choices

Your saved cloud profile and meals remain available until you delete them or request account deletion. You can edit your profile and meals and delete individual meals in the app. To request a copy of your cloud data or deletion of your account and diagnostic records, email [email protected] from the address associated with the account. We may need to verify ownership before acting.

Signing out or removing Trackcalr's Google access does not itself delete your journal. Local data can be removed using your browser's site-data controls. Provider logs and backups may have separate retention periods and may not be removed immediately when live app data is deleted.

Trackcalr's calorie-planning features are intended for adults. Contact us if information about a child has been submitted. Changes to this policy will be published here with an updated date.