Privacy Policy — Calzone

Calzone is a calorie and nutrition tracking app. This policy explains what personal data the app and this website collect, why, who else gets to see it, and what you can do about it. It is written to be read, not to be survived.

The short version

We collect what the app needs to work: your account, your profile, and what you log.
Food and menu photos are sent to OpenAI to be turned into an estimate. We do not keep them.
There are no advertising or analytics SDKs in the app. Nothing follows you around.
We do not sell personal data, and we never will.
Deleting your account from inside the app really deletes it.

1. Who we are

Calzone is operated by Krzysztof Szyszka, a sole trader registered in Poland, who is the data controller for the personal data described here. You can reach a person at support@calzone.fit.

2. What we collect

What you give us

Account — your email address and which method you signed up with (Apple, Google, or email and password). Passwords are handled by our authentication provider and stored hashed; we never see them.
Profile and goals — sex, age, height, weight, activity level and target weight. These exist for one reason: to calculate your daily calorie and macro targets.
What you log — meals, portions, calories, macros, micronutrients, timestamps, daily scores, saved restaurants, meal plans and any products you create yourself.
Photos and descriptions you send to the AI — a photo of a plate, a photo of a menu, or a typed description. It travels through our server to OpenAI, comes back as an estimate, and is not stored on our servers afterwards.
Products you publish to the shared catalogue — when you add a product, its name, brand, barcode and nutrition values are saved to a catalogue that every other Calzone user can search, together with the account identifier of whoever created it. That identifier is not shown to other users, but the product entry itself is public inside the app. Do not put anything personal in a product name.
Anything you write to us — support emails, bug reports, beta sign-up details on this website.

What the service records by itself

AI usage counters — each AI request is counted against your account for that day, so the daily limit can be enforced and abuse spotted. The counter stores your account identifier, a date and a number, not the content of the request.
Ordinary server logs — our hosting and database provider keeps short-lived technical logs, including IP addresses, as every server does.
Website analytics — this site uses Vercel Web Analytics, which counts page views and referring pages without cookies and without building a profile of you.

What we do not collect

No advertising SDKs, no third-party analytics SDK and no crash-reporting SDK inside the app.
No location, no contacts, no microphone, no calendar.
No Apple Health or Google Fit data. The app does not connect to either.
No card or bank details. Payment happens inside Apple's or Google's system and we only learn whether your subscription is active.

3. What we use it for

Running the app: signing you in, storing your logs, calculating your targets and your daily score.
Producing AI estimates from the photo or text you submit.
Keeping your subscription status in sync so Premium features unlock on every device you sign in on.
Enforcing the daily AI limit and stopping abuse of a service that costs real money per request.
Answering you when you write to support.
Fixing bugs, using what you tell us and what the server logs show.
Meeting legal and accounting obligations.

We do not use your logs to profile you for advertising, and no automated decision with a legal or similarly significant effect is made about you.

4. Legal basis (GDPR)

Performance of a contract — your account, your logs, AI estimates and subscriptions. Without this data there is no app.
Legitimate interest — security, abuse prevention, debugging, and keeping the shared product catalogue usable.
Consent — marketing emails, if you ever ask for them. You can withdraw it at any time.
Legal obligation — tax and accounting records relating to purchases.

We do not sell your data and we do not share it with advertisers. These are the processors that make the app work:

Supabase — database, authentication and the server functions that talk to the AI. Holds your account, profile and logs.
OpenAI — receives the photo or description you submit for analysis, and sends back an estimate. Under OpenAI's API terms, API inputs are not used to train their models. They may hold a copy briefly for abuse monitoring before deleting it.
RevenueCat — tells the app whether your subscription is active. Receives an account identifier and purchase status, not your logs.
Apple and Google — sign-in, payment, distribution. They are controllers of what they collect themselves, under their own policies.
Open Food Facts — when you scan a barcode, that barcode is looked up in their public database. Your identity is not sent, though your device's IP address reaches them like any web request.
Vercel — hosts this website and its cookie-free analytics.

We may also disclose data if the law requires it, or to protect the service and its users from fraud or serious abuse.

6. Transfers outside the EEA

OpenAI is based in the United States, and some of our other providers operate globally. Where data leaves the European Economic Area it is covered by the European Commission's Standard Contractual Clauses or an equivalent safeguard under Chapter V of the GDPR.

7. How long we keep it

Account, profile and logs — until you delete your account. Deletion removes them from the live database immediately and from backups as those backups roll off, within 30 days.
AI photos and descriptions — not stored by us at all. The estimate is saved, the image is not.
Shared catalogue products — they stay in the catalogue, because other people's logs point at them. They contain no personal data once the creator identifier is detached, which is what account deletion does.
AI usage counters — rolling, kept only as long as the limit needs them.
Beta sign-ups on this website — until launch plus twelve months, or until you ask us to remove yours.
Purchase records — as long as tax law requires, which in Poland is five years from the end of the accounting year.

8. Your rights

Under the GDPR you can ask us to:

Give you a copy of the personal data we hold about you.
Correct anything that is wrong.
Delete your account and data.
Restrict or object to processing based on legitimate interest.
Export your data in a machine-readable format.
Withdraw consent where consent is what we relied on.

Deletion is built into the app: Settings, then Privacy, then Delete my account. It is immediate and it is real. For anything else, email support@calzone.fit and we will answer within 30 days. If you think we have handled your data badly, you can complain to the Polish data protection authority, the Urząd Ochrony Danych Osobowych, ul. Stawki 2, Warsaw.

9. Security

Traffic is encrypted with TLS and data is encrypted at rest. Each account can only read its own rows, enforced by row-level security in the database rather than by trust in the app. Access to production is limited and protected by two-factor authentication. No system is perfectly secure, and we would rather say that plainly than promise otherwise.

10. Age

Calzone is not for children. You need to be at least 16 to use it in the European Economic Area, or at least 13 elsewhere where local law allows it. If you believe a child has an account, write to support@calzone.fit and we will remove it.

11. Cookies and tracking

This website sets no advertising or cross-site tracking cookies. Its analytics are cookie-free and aggregate. The app contains no tracking SDK, does not use the advertising identifier, and therefore never shows an App Tracking Transparency prompt, because there is nothing to ask permission for.

12. Changes

If this policy changes in a way that matters, the date at the top changes and we tell you in the app or by email before it takes effect.

13. Contact

support@calzone.fit. A person reads it.