What Platey stores, and where it goes

What you log. Meals and the foods in them, with their estimated calories and macros; any photo you took; corrections you make to a portion; foods you save as favourites; training sessions you add; and weight entries if you record them.

Your settings. Your daily targets, and the details used to suggest them — height, weight, age, sex, how active you are and what you are aiming for. These are used to calculate targets and nothing else.

Your account. If you create one, an email address and a password handled by the authentication service, never stored by Platey in readable form.

Nothing else. No contacts, no location, no health app data, no advertising identifiers, and no browsing behaviour beyond the site itself.

Without an account, everything stays in the browser you are using — the diary in local storage, photos in the browser’s own database. It never reaches a server, which also means it does not follow you to another device, and clearing your browser data deletes it.

With an account, your diary is stored in a hosted Postgres database with row-level rules that tie every row to your user ID. That check is enforced by the database itself, not merely by the app in front of it, so a bug in the app cannot show your diary to somebody else.

Photos go in a private bucket, filed under your user ID, with storage rules that make the first part of the path the ownership check. They are shown to you through links that expire. Deleting a meal removes its photos as well as its rows.

One thing: the photo or description of a meal you have asked Platey to analyse. It is sent to Anthropic’s Claude API, which identifies the food and estimates the portion, and the structured result comes back and is stored with the meal.

The request goes through Platey’s own server, so the API key is never in your browser and is never exposed to the page. Photos are resized and recompressed on your device first — a 12-megapixel phone photo becomes roughly 150KB — so less is sent than you took. The result is kept with the meal, which means opening that meal again never sends anything a second time.

Everything else — your day, your targets, what would fit next, the weekly summaries, the training adjustments — is worked out on your own device and sends nothing anywhere.

All of this is in Settings, inside the app, and none of it needs an email to anybody:

• →Delete a single meal, which removes its photo too
• →Delete a photo but keep the meal
• →Delete a whole day
• →Delete everything and close the account

Deletions are real deletions rather than a hidden flag, and the app asks before doing anything irreversible.

There are no advertising cookies and no third-party trackers on these pages. If you create an account, the authentication service sets what it needs to keep you signed in — that is a cookie doing the job you asked it to do.

Anonymous, aggregate usage measurement may be used to see which pages people read and whether the sign-up flow works. It records events such as “someone completed sign-up”, never who, and never anything about what you ate.

The deletion controls in Settings remove your account and everything in it immediately, without needing to ask anyone. A published contact route for data questions is being set up.

This page describes how Platey handles data today and is written to be readable rather than legalistic. The FAQ covers the practical questions people ask most.