Encryption in transit
The mobile apps, this website, and the API communicate over HTTPS (TLS). We do not offer a downgraded plain-HTTP API for production clients. Store purchases and sign-in with Apple or Google stay on those providers’ own secure channels.
Access to your account
Sessions use short-lived access tokens and rotating refresh tokens stored hashed on the server. Signing out invalidates the refresh session. Staff do not get a backdoor into your diary; support looks at an account only when you ask us to.
What we store
Account identity, profile and goals, food entries, weight, water, fasting, reminders, and subscription status needed to run the product. Photos you submit for logging are used to produce an estimate. We do not sell personal data.
GDPR and privacy requests
You can access and correct most data inside the app. Export covers a portable copy of your log. To restrict or object to processing, or to ask a question about a subprocessor, email the contact address and we will verify the account before changing anything. Legal bases and retention details live in the privacy policy.
Deleting your data
Account deletion removes the Calora profile and associated logs. Encrypted backups roll off on their normal cycle rather than vanishing from every replica in the same second. Records we must keep for fraud, tax, or security investigations are limited to that purpose and are not part of the product diary.
Coach links are not account access
A trainer share link is a read-only summary you can revoke. It does not include your password, payment method, or edit rights.