What the app sends
In short: to look up a product, the LabelSage iPhone app sends only a barcode, your search words or a product category. Names, allergies and your household stay on your iPhone.
Every request the app makes
| When | Address | What it carries | What comes back |
|---|---|---|---|
| When the app opens | GET api.labelsage.app/v1/config.json |
Nothing | Feature switches. A switch can only turn a feature off. |
| You scan a barcode or open a product | GET api.labelsage.app/v1/products/{barcode} |
The barcode | The product: name, brand, ingredients, allergens and nutrients |
| You search by name, or the app looks for other options | GET api.labelsage.app/v1/products?q=…&limit=…&full=true |
Your search words, or the product's category | A short list of matching products with their ingredients. If the server does not accept full, the app looks up each result by barcode. |
| A product photo is shown | GET api.labelsage.app/v1/images/… |
The photo's address | The photo. Many photos come from Open Food Facts. |
| You tap the privacy, terms or support link | Opens in your browser | The page address | The page |
Every request
- No account, no sign-in and no cookies.
- No device identifier and no advertising identifier.
- The same two headers for everyone:
User-Agent: LabelSageandAccept-Language: en. - HTTPS only.
- Like any internet service, our server and our network provider, Cloudflare, see the IP address of a request while handling it.
Never sent
- Names and the members of your household
- Allergies and diets
- Favourites and recent products
Checking a product against your household happens on your iPhone. The app has no analytics, ads or tracking tools. If iCloud Backup is on, the app's data is part of your own Apple backup.
The report form on our support page is different: it sends what you type there to LabelSage.
Details
The technical description of these requests is in the LabelSage app API file (OpenAPI). What we keep, and how to ask us to delete it, is in the privacy policy.