Privacy policy

Last updated 22 November 2026. What HariLens collects, why, who receives it, how long it is kept, and how to have it deleted.

HariLens is a food-label scanner app for Android (com.harilens.app). It is made and run by one independent developer in Sri Lanka, the developer named on the HariLens listing on Google Play. In this policy, "we" means that developer. You can reach us at [email protected].

This policy covers the HariLens app and the harilens.com website. It is written against how the app actually works, and it changes when the app changes.

The short version

What the app does

You scan a packaged food's barcode. If the product is already in our shared database, you get its result straight away. If it is not, the app guides you through photographing the pack (front, rating logos, nutrition panel, ingredient list, lid and dates), reads the label from those photos, and checks it against published Sri Lankan rules and scientific reference data.

What we collect and why

1. Barcodes you scan

When you scan, the app sends the barcode to our backend to look the product up. If we do not have the product, the app asks Open Food Facts for its name and brand, sending only the barcode.

We count scans so we know which products and categories to add first. Each count holds the barcode, the time, whether the result came from our database or had to be read fresh, and which AI model read it. It holds no user ID, no device ID, no IP address and no location. We only ever look at these counts in groups, and we hide any group with fewer than five scans.

2. Label photos you take

When you photograph a new product, or photograph an ingredient list to add or correct it:

If you are offline, the photos wait in a queue on your phone and are sent when you are back online. They are deleted from the queue once sent, or if you discard them. Your own front-of-pack photo is also kept on your phone so the result screen can show the pack you photographed, and other phones keep a copy of a product's shared picture once they have shown it.

If you would rather not have your kitchen in the picture, fill the frame with the label.

3. Your anonymous contributor ID

The first time you send photos or a report, the app creates an anonymous account on our backend. It is a random ID with no name, email address or phone number. It ties your contributions together so we can tell when photos from different phones agree, and so we can remove abuse. Before the ID is created, hCaptcha checks that you are a person. This is usually invisible; hCaptcha receives information about your device and how you interact with the check, as described in its own privacy policy.

The app also makes a random number when it is installed. With your contributions we store a one-way scrambled code made from that number, never the number itself.

4. Reports that a result is wrong

When you tap "Doesn't match the pack", we store the barcode and your reason (up to 500 characters). Reports that a result or a picture is wrong are linked to your anonymous contributor ID (for an older app version, a one-way code made from the install number) and a one-way, salted hash of your network address, which cannot be turned back into the address. We use them only so that one phone counts once. When the product is restored or its reading is replaced, that link is removed from its earlier reports. Picture reports are deleted after 30 days.

5. Daily fair-use counts

To enforce fair-use limits, we keep a daily count of the new products, label photos and picture checks sent by each anonymous install, and of the new products and picture checks sent from each network (by the same salted hash of its address). The counts hold nothing else and are deleted after 7 days.

6. MRPs you report

If you answer "MRP still Rs …?" or type the MRP printed on a pack, we receive the product's barcode, the MRP and the date, so everyone can see how MRPs change. We also keep a one-way scrambled code made from the app's install number, and another made from your internet connection's address (for a newer IPv6 address, from the part that belongs to your home or mobile connection). We use them to stop anyone flooding us with fake MRPs, to remove all of theirs together, to count how often a phone's reports turn out right, and to count how many different phones agree on a new MRP, so that one connection cannot pose as several phones. Neither code can be turned back into the install number or your address, and we never store either of those. No shelf price, shop, location, name or account is sent, and nothing from your diary.

7. Re-check requests from makers or sellers

If you make or sell a product and use "I make or sell this product" to ask for a re-check, we store your name, company, email address, your message, the product's barcode and the rating you were looking at. A person reads it and replies by email. So that one phone cannot flood us with requests, we also keep a one-way code made from the install number and the same one-way, salted hash of your network address with the request, never the install number or the address itself. We use these details only to answer that request, never for marketing.

8. Crash reports

If the app crashes, a crash report is sent to Sentry so we can fix the fault. It contains the error, the app version, and the phone model and Android version. It does not contain photos, screenshots, your name or your IP address (Sentry is told not to store it), and it is not linked to your scans.

9. Additive lookups

When you open an additive's WHO JECFA entry, the app fetches that page from the World Health Organization's public JECFA database. Only the additive's identifier is sent.

10. What stays on your phone

When you tap I'm buying this, the purchase, how much you had, and your own calorie, protein, sugar, salt and saturated-fat targets are saved only on your phone. Your scan history is kept on your phone too. We never receive any of this. It is included in your phone's own Google backup if you have that switched on, so it can come back when you reinstall the app or move to a new phone. Uninstalling the app or using "Clear data" deletes it. The body weight you may type to work out a protein target is used once and not saved.

What we do not collect

The camera permission is used only to scan barcodes and photograph labels inside the app.

Who receives data

PartyWhat they receiveWhy
DeepSeek (DeepSeek API)Label photos and shared pack pictures, when routed to DeepSeekReading the label and checking pictures
Xiaomi (MiMo API)Label photos and shared pack pictures, when routed to MiMoReading the label and checking pictures
Google (Gemini API)Label photos and shared pack pictures, when routed to GeminiReading the label and checking pictures
Supabase (hosts our backend, Mumbai region)Barcodes, what was read from labels, evidence photos, shared pack pictures, contributor IDs, scrambled codes, reports, daily fair-use counts, MRPs, re-check requests, anonymous scan countsRunning the shared product database
hCaptcha (Intuition Machines)Device and interaction signals during the person checkStopping automated abuse
Open Food FactsThe barcode of a product we do not have yetSuggesting its name and brand
SentryCrash reportsFinding and fixing crashes
World Health OrganizationAn additive's identifierShowing its JECFA entry
CloudflareWebsite requests and emails sent to [email protected]; the shared pack pictures it stores and serves, and the app's requests for them (including your phone's IP address)Protecting and delivering the website, forwarding support email and serving shared pack pictures

We do not sell data and we do not use it for advertising. Results in the app come from a fixed, cited ruleset and are never changed for payment.

How long we keep it

DataHow long
What was read from a label, evidence photos, MRP historyAs long as the product is in the shared database, or until you ask us to delete your photos
Reports that a result is wrongAs long as the product is in the shared database; their link to an install and a network is removed when the product is restored or its reading is replaced
Reports that a picture is wrongDeleted after 30 days
Daily fair-use countsDeleted after 7 days
Re-check requestsDeleted 12 months after the request is closed
Crash reportsDeleted automatically by Sentry after its retention period (90 days at most)
Anonymous scan countsKept as counts, with nothing that identifies you
Diary, targets and scan historyOn your phone until you clear the app's data or uninstall it

Security

All traffic between the app and our backend uses HTTPS. Database access is limited by row-level security rules, writes go only through our server-side functions, and evidence photos sit in private storage that only the account that uploaded them and our server can read.

Deleting your data

We reply to deletion requests within 30 days.

Children

HariLens is meant for general audiences and is not directed at children under 13. We do not knowingly collect personal information from children.

The harilens.com website

The website is a static site served from a server we run ourselves, with Cloudflare in front of it. It sets no cookies and uses no analytics or trackers, and its fonts are served from the site itself. Cloudflare handles the requests (including your IP address and browser details) to deliver and protect the site, and passes them on to our server, which keeps no record of them. Emails sent to [email protected] are forwarded by Cloudflare to our inbox, and we use your email address only to reply.

Cloudflare also stores and serves the shared pack pictures. When the app shows one, your phone asks Cloudflare for it, so Cloudflare receives that request, including your phone's IP address.

Changes

If this policy changes materially, the date at the top changes and the new version is published at harilens.com/privacy before the app update that needs it ships.

Contact

Questions, requests or complaints: [email protected].