Data Retention & Deletion Policy

The public demo and a future account

The mobile demo shown on this site uses example entries and does not save a personal food log. That statement does not rule out technical information handled by hosting, security, contact or analytics systems; the Privacy and Cookie policies address that review.

A future production account may involve contact details, nutrition entries, recipes, targets, body or training information, subscription records and support requests. The exact categories must be verified against the service that is actually deployed.

No invented retention periods

The production retention schedule, storage regions, backup expiry, restoration process and deletion implementation are not confirmed. This draft does not promise immediate erasure, a fixed deletion deadline or a particular backup cycle.

The final schedule must explain how long each category is needed for its purpose, how user deletion affects it, and what must be retained for a lawful obligation or a documented dispute. General business convenience alone is not a substitute for that review.

Requesting access, correction or deletion

Email the support contact above with the account email and the request you want to make. Ask for access, correction, an available copy, deletion, or another applicable privacy right as appropriate. Do not send passwords or unnecessary health records.

Callory may need proportionate verification to avoid acting on the wrong person’s account. The final request process, applicable legal time limits, export formats and any self-service controls must be confirmed before launch.

If a lawful retention exception applies, the response process should identify what cannot be deleted and why, subject to applicable law. No account dashboard or automated export is currently promised on this site.

Deletion is not the same as cancellation

Deleting entries, clearing browser data or removing a home-screen shortcut does not necessarily delete server-side information. Requesting account deletion does not by itself establish that future subscription billing has stopped.

If you also want to cancel future billing or seek a refund, say so explicitly. The Cancellation & Refund Policy and the launch checkout must explain those separate processes.

Backups, service providers and updates

The treatment of backups, provider copies and legal purchase records needs a documented operational process. Do not interpret an unresolved item in this draft as proof that no copies exist.

Any change to data categories, vendors, storage, account controls, payment records or applicable legal requirements must trigger a coordinated update of this policy and the Privacy Policy.

Future food-photo and planning records

Before a live photo or meal-planning workflow is introduced, the retention schedule must address original images, derived food-analysis results, weighed entries, saved recipes, meal plans and shopping lists separately where needed. Image-analysis providers, temporary processing, backups and deletion propagation remain unconfirmed. The marketing walkthrough does not upload visitor photos or save these records, and this draft promises no new deletion deadline.