Last updated 22 August 2026
This policy explains exactly what ProScan AI collects, why, who it goes to, and how to erase it.
ProScan AI is an iOS app published by Luke Boylan. For anything in this policy, including any request about your data, write to anonymous@actualoccasions.com. For UK and EU data protection law, we are the data controller for the information described below.
The first time you open the app it quietly creates an anonymous account for you. This is a randomly generated identifier. It is not linked to your name, your email, your phone number, or your device's advertising identifier, and there is no signup screen. Its only job is to keep your profile and your scan history attached to you across sessions.
To calculate your daily protein target and grade products for your goal, the app asks for your gender, age range, height, weight, activity level, training frequency, dietary goal, and any allergies you want flagged. It also records which source you said you came from, if you answer that question.
Your allergies, height, and weight are health related information. Under UK and EU law this is a special category of personal data, and we process it only on the basis of your explicit consent, which you give by choosing to enter it. Every one of these answers is optional, you can change them later in Profile, and you can withdraw consent at any time by clearing them or deleting your account.
When you scan a product we store the barcode, the product name and brand, the nutrition values we looked up (calories, protein, sugars, saturated fat, sodium, serving size), the score the app calculated, and the time of the scan. This is what powers your history and your recommendations.
Linking Sign in with Apple is entirely optional and the app works fully without it. If you do link it, Apple sends us the email address you approve, which may be one of Apple's private relay addresses that hides your real one. We use it for a single purpose: restoring your subscription and history if you reinstall the app or move to a new phone.
Purchases are processed by Apple. We never see or receive your card number, billing address, or any other payment detail. We receive only whether your subscription is currently active, by way of RevenueCat, which manages entitlements for us.
If you tell us a product is missing or wrong, we store the barcode, whatever name you typed, the reason, and your anonymous account id so we can tell reports apart.
We use a small number of service providers. They process data on our instructions only and cannot use it for their own purposes.
| Provider | What it handles | What it receives |
|---|---|---|
| Supabase | Database and anonymous authentication | Your account id, profile answers, and scan history |
| RevenueCat | Subscription entitlements | Your account id and subscription status |
| Apple | Payments, and Sign in with Apple if you link it | Payment details, which we never see |
| Open Food Facts | Product and nutrition lookup | The barcode only |
| USDA FoodData Central | Product and nutrition lookup | The barcode only |
The last two are worth being precise about. When the app looks up a product, it sends the barcode number and nothing else. Your account id, your profile, your goal, and your allergies are never included in those requests, so neither database can associate a lookup with you.
If you are in the UK or the EU, our legal bases under the GDPR are:
Your profile and scan history stay until you delete them. There is no fixed expiry, because a history that silently erased itself would make the app worse.
When you delete your account, your profile, your scans, and your missing product reports are removed from our database immediately and permanently. Cached nutrition facts for a barcode are kept, because that information describes a product on a shelf rather than a person, and it carries no link to you.
Wherever you live, you can ask us to give you a copy of your data, correct it, delete it, export it, restrict how we use it, or object to our using it. If you are in the UK or the EU you may also withdraw consent at any time and complain to your data protection regulator, which in the UK is the Information Commissioner's Office. If you are in California you have the rights to know, delete, and correct, the right to opt out of sale or sharing, which is moot because we do neither, and the right not to be treated differently for exercising any of them.
The fastest way to erase everything is in the app: open Profile, then Delete Account. It is immediate and it is not recoverable. For anything else, email anonymous@actualoccasions.com and we will respond within 30 days. We do not charge for this.
Your data is held on infrastructure operated by our providers, which may process and store it in the United States and other countries outside the UK and the EEA. Where that happens, the transfer is covered by Standard Contractual Clauses approved by the UK and EU authorities, or an equivalent approved safeguard.
Every table enforces row level security, so a given account can only ever read or write its own rows, and that rule is applied by the database itself rather than by the app. All traffic runs over TLS. Your session token is held in the iOS Keychain. No system is perfect, and we will not claim otherwise, but we do not hold payment details or passwords, which removes the two things most worth stealing.
ProScan AI is not directed at children under 13, and we do not knowingly collect their personal information. If you believe a child has given us data, email us and we will delete it.
ProScan AI gives general nutrition information. It is not a medical device, and nothing in it is medical or dietary advice. Allergy flags are a convenience built on label data that can be incomplete or out of date, so always read the physical packaging. If you have a health condition that affects your diet, talk to a qualified professional.
If we change this policy we will update the date at the top. If a change materially affects your rights or what we collect, we will tell you in the app before it takes effect rather than hoping you re-read this page.
