Privacy policy

Last updated 2026-09-11. This policy is written to be read, not to be survived.

The short version

• Reading this site needs no account and sets no tracking cookies.
• Scanning needs a Google sign-in, so scans are tied to your account — that is what makes your history and your allowance work.
• Photographs you scan are sent to our AI provider for analysis and are not retained by us afterwards.
• Your food diary and scan history are yours. We do not sell them, and there is no advertising network in the page.
• You can export everything, or delete your account and everything in it, from your account page.

What we collect

If you only read the site

Nothing identifying. No account, no tracking cookies, no advertising network. Our host keeps the ordinary request logs any web server produces.

If you sign in and scan

We store your email address, and your name and avatar where Google supplies them. Each scan is recorded against your account: the food, the figures and the time. That record is what your history page shows and what your allowance is counted from — the same rows serve both, so what we meter and what you can see are never different numbers.

Your food diary is separate and lives in your own browser. It is not sent to us.

Photographs

An image you scan is transmitted to our AI vision provider, analysed, and the resulting figures are returned. We do not store the image on our servers once the scan completes. Do not photograph anything you would not want processed by a third-party service — a food photograph that happens to include a person, a document or a screen is still a photograph of those things.

What we never collect

We do not ask for, and have no way to store, your weight, your body measurements, your medical history or any health condition. A calorie target you set is a number you chose, kept alongside your diary.

Camera access

The barcode scanner needs your camera. The video stream is processed entirely inside your browser to find the barcode — frames are never uploaded. Only the decoded number leaves your device. Permission is asked for by the browser, is limited to this site, and can be revoked at any time in your browser settings.

Cookies

A session cookie when you are signed in, and that is all. No advertising or cross-site tracking cookies are set.

Processors we use

• Open Food Facts — receives the barcode you scan, nothing else.
• Our AI vision provider — receives photographs you submit for analysis.
• Stripe — handles payments. Card details go to Stripe directly and never touch our servers.
• Vercel — hosts the site and processes the request logs any web server produces.

Your rights

From your account page, without emailing anybody:

• Export everything we hold — account, scan history, diary and payment record — as a single JSON file.
• Cancel a subscription through Stripe's own billing portal.
• Delete your account, which removes your scan history and account record and cancels any active subscription first. If that cancellation fails, nothing is deleted — you are never left with a deleted account and a live charge.

Deletion is irreversible, so export first if you want to keep the record. If you would rather ask a person, email support@caloriescanner.io and we will action it.

If you are in the UK or EU, you have the right to access, correct, export and erase your personal data, and to object to processing. The lawful basis for the processing described here is performance of a contract for the account features, and legitimate interest for anonymous aggregate counts.

Children

This site is not directed at children under 13 and we do not knowingly hold their data.

Changes

If this policy changes in a way that affects what we collect, the date at the top changes and signed-in users are told by email.