Privacy policy

Last updated: 8 November 2026

AisleSee ("the app") is provided by [NAME] ("we"). We are the data controller for the personal data described here. Contact: [CONTACT EMAIL].

In short

• You can use the app without an account. Photos and camera frames are read on your phone.
• If you sign in, your settings are backed up to a private record that only you can read.
• Products you share with other shoppers carry no name, email or account ID.
• We don't sell your data and the app shows no adverts.

What stays on your phone

• Photos and live camera frames. Text reading and bottle detection run on the phone. Photos are not uploaded unless you use AI identify (below).
• Your location. Used on the phone to pick the nearest store you have saved.
• Saved stores, products and settings, and the field-test log.
• Store alerts. The phone checks for new shared finds about once an hour and shows a notification itself. No push token is sent to us.

What leaves your phone, and why

• Product lookups. When you look up a barcode, or the app reads a product name from a pack, the barcode or the words are sent to our server (a Google Cloud Function in London), which finds the product on Open Food Facts. No photo or account details are sent. Your IP address is used briefly, in memory only, to limit how many lookups one phone can make. See the Open Food Facts privacy policy.
• OpenStreetMap. When you tap Find nearby, your approximate location is sent to the Overpass API (overpass-api.de) to list nearby shops.
• Speech. When you tap the microphone, your phone's own speech recogniser turns speech into text. Depending on your phone this may be processed by Google. The app only receives the text.
• AI identify (off by default). If you turn it on and tap the AI button, a smaller copy of that photo is sent to Google Gemini through Firebase AI Logic to read the products in it.
• Account (optional). If you sign in, Firebase Authentication (Google) holds your email address, and your Google account name and ID if you use Google sign-in.
• Private settings backup (signed in only). Your home cards, allergens and custom searches, the sharing switch and watched stores are stored in a record that only your account can read or change. Allergens and coeliac disease can reveal health information. We store them only to back up the choices you make, and you can delete them at any time by deleting your account.
• Shared finds (signed in, sharing switched on). When you save a green result to a store, the store, product name, barcode, the label words that matched and the dates are shared with all users. These records contain no user details.
• Shared product cache. Our server keeps the Open Food Facts records it fetches for 30 days, so they needn't be fetched again. They contain no user details.

Where it is stored

Account and database records are held by Google Firebase. The database is in London (europe-west2). Firebase Authentication and Gemini may process data outside the UK under Google's safeguards. See the Firebase privacy information.

Legal basis

We use your data to provide the features you choose (contract). We store health-related settings only with your explicit consent, given when you sign in and save them; you can withdraw it by deleting your account.

How long we keep it

• Your account and private settings: until you delete your account (Settings → Account → Delete account), which removes both.
• Shared finds and the product cache contain no personal data and stay after you delete your account.
• Data on your phone: until you uninstall the app or clear its data.

Your rights

Under UK data protection law you can ask to access, correct, delete or export your personal data, and object to or restrict its use. Contact [CONTACT EMAIL]. You can also complain to the Information Commissioner's Office.

Children

The app is not intended for children under 13, and they should not create an account.

Changes

We will update this page when the app changes how it uses data, and change the date at the top.