Cal4Cal home

Privacy Policy

Effective September 30, 2026. Cal4Cal is operated by George Asrian. Contact george.asrian@gmail.com with privacy questions or deletion requests.

Information we collect and why

Google sign-in supplies your name, email address, and Google account identifier to identify your Cal4Cal account and keep your saved log separate from other users. A session cookie keeps you signed in.

We store the meal names, dates, times, notes, calories, and macronutrient estimates that you save. When you select Interpret meal, your submitted photos and meal description are sent to OpenAI to estimate nutrition. The analysis can use web search to look up food nutrition. Photos are processed for analysis and are not saved in Cal4Cal’s meal database. OpenAI processes submitted content under its own API data-handling policies; provider retention may differ from Cal4Cal’s storage.

Optional Google Health connection

If you connect Google Health, Cal4Cal requests read-only activity and fitness access for daily total calories burned, read-only health metrics and measurements access for weight, and separate read-only sleep access for sleep duration, onset, wake times, stages, and source metadata. These permissions cover broader data categories; our integration currently retrieves daily calorie totals, weight measurements, and sleep sessions. You can decline sleep or weight access and still sync calories. Cal4Cal does not write to Google Health.

We associate these values with your account to display calories out, calorie balance, weight trends, and exploratory sleep and calorie association analyses. Manual sleep entries, timezone preferences are also stored with your account. We store an encrypted refresh token to maintain the connection and refresh data when you use Cal4Cal or select Sync. We do not send Google Health values or connection tokens to OpenAI’s meal-analysis service.

Storage, sharing, and limited use

Cal4Cal runs on Cloudflare through ChatGPT Sites. Cloudflare processes and stores account records, saved meals, and synced health values to operate the service. Google processes sign-in and health authorization. OpenAI processes the meal content you submit for analysis. Service providers may process operational logs for reliability and security.

We do not sell Google user data, use it for advertising, or use it to train general-purpose AI models. Cal4Cal’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Health data is used to provide the calorie-balance and weight features you choose. Access for support or security is limited to what is necessary and permitted by those requirements.

Guest viewers

If you create a guest viewer, that person can view your saved meals, calorie history, weight, sleep and reports. You choose their password and share it yourself. You may change the password or delete the viewer at any time; doing so ends existing guest sessions. Guest passwords are stored as salted hashes, not as readable passwords.

Your choices and deletion

You can use meal logging without connecting Google Health. You can edit or delete individual meals in your journal. To stop future health access, revoke Cal4Cal in your Google Account connections. Revocation does not automatically delete previously synced records.

Saved records are retained until deleted or a deletion request is fulfilled; we do not currently apply an automatic expiry to saved meal or health records. Email george.asrian@gmail.com from your account’s email address to request deletion of synced health data or your Cal4Cal account and saved records. We may verify your identity before fulfilling a request. Provider logs or backups can have separate retention schedules.

Security and updates

Connections use HTTPS, health refresh tokens are encrypted in storage, and account checks restrict access to saved records. No online service can guarantee absolute security. We will update this page when our data practices change.

About Cal4Cal · Contact