Privacy policy
What changed on 28 October 2026: Crash reports are now off unless you turn them on. The app asks you once, and you can change your answer at any time in Profile (see Your choices and rights). If you’re signed in, the app now asks you before it saves your allergies, typed allergens, diets, goals and watch list in your account. We keep a record of your answer, and you can stop saving them there at any time in Profile → Preferences (see Health information). We added the legal basis for each use of your data (see Legal bases), and, for the services we use, where they are and how data sent to them from the EU, the UK and Switzerland is protected (see Where they are). We now say how long we keep emails, password reset emails and subscription records, list all your rights, with a section for Washington State and Nevada, and explain that Knowsie isn’t medical advice. Product photos you send are now saved without the camera details hidden in them. We also explain what the beta testers page remembers in your browser. Versions of the app before 1.0.15 can’t receive these changes. If you’re signed in on one, it still saves your preferences in your account without asking, as before. Please update the app, and it will ask you.
What changed on 24 October 2026: Scan history also notes whether you scanned a product with the camera (yes or no, not when), because the Label reader badge now counts only scanned products (see What we collect). Products already in your History on 24 October 2026 count as scanned. If you’re signed in, your phone also keeps a copy of the products you open, so the app can tell you when a change to our ingredient database moves a score (see What stays on your phone).
What changed on 23 October 2026: From app version 1.3.0, you can attach a screenshot or photo to your feedback when you’re signed in. We explain what we keep, who can see it and when it’s deleted (see What we collect and How long we keep it). Deleting your account now also deletes the screenshots you attached.
What changed on 21 October 2026: We added badges: what they keep in your account and on your phone, and for how long (see How long we keep it). Badges are reaching the app step by step, so you may not see them yet. If you’re signed in, your weeks with at least one product checked are noted from your History from now on, also before badges are shown to you. We also explain what we keep so the app can tell you what happened to a product or report you sent in: the reason, if we don’t use it, and a short list on your phone of what you sent (see How long we keep it).
What changed on 19 October 2026: We added recipe changes and favourites: what they store, where and for how long, and what signing out or deleting your account removes (see How long we keep it). We described how notifications about recipe changes will work once we add them; they aren’t available yet. We also corrected scan history: opening a product from Search or from your favourites adds it to your history, and so does a product you send in while signed in.
This policy describes the Knowsie app for iPhone and Android, version 1.3.0, including the updates we deliver inside the app. Until a new version of the app renames it, your phone may still show its earlier name, Malvi.
Knowsie (“we”) is an app that scans packaged food, reads the ingredients and rates them. This policy explains what we collect, why, who processes it, and the choices you have. We don’t show ads, we don’t track you across other companies’ apps or websites, and we don’t sell your data.
Knowsie is run by Malwina Stachurska, who is responsible for your data (the “data controller”). For anything about your data, write to privacy@knowsie.app.
What we collect
You can use Knowsie without an account. We collect only what the features you use need.
| What | When | Where it’s kept |
|---|---|---|
| Email address and password | You create an account with email | Our sign-in provider. Your password is stored only in scrambled (hashed) form, so we never see it. We don’t send a confirmation email or any marketing email. If you ask to reset your password, we email you a link to set a new one, from our mailbox. |
| Your email address, name, profile picture link and Google’s ID for you | You sign in with Google | Our sign-in provider. Google passes these on automatically, and they’re saved with your account. |
| Your email address (or Apple’s private relay address, if you hide yours) and Apple’s ID for you | You sign in with Apple (iPhone only) | Our sign-in provider. Apple may offer to share your name, but we don’t keep it. We may also keep a token from Apple that lets us ask Apple to end Knowsie’s access when you delete your account. It’s deleted with your account. |
| When you created your account and last signed in, and the IP address and device type of each sign-in | You’re signed in | Our sign-in provider, until you sign out on that device or delete your account. Deleting the app without signing out doesn’t end a sign-in. |
| Your preferences: allergies, allergens you type in, diets (vegan, vegetarian, halal, kosher), nutrition goals and watch list, and whether you finished or skipped the first-run setup | You set them when you first open the app, or later in Profile → Preferences | On your phone, whether or not you’re signed in. When you’re signed in, also in your account, but only if you agree (see Health information, which also explains what older versions of the app do). Preferences you set without an account are added to your account when you sign in, if you agree. |
| Your answer to saving your preferences in your account: when you agreed, when you withdrew if you do, and which version of the question you saw | You’re signed in and the app asks you, or you change your answer in Profile → Preferences | Your account |
| Scan history: barcode, product name, score and time, and whether you scanned it with the camera (yes or no) | You scan a barcode, or open a product from Search or from your favourites, while signed in, and the app finds and scores it. A product you send in while signed in is added too, even before it has a score. Opening a product from History updates its entry. Opening one from Recipe changes or from the alternatives we suggest doesn’t add anything. A product you scan with the camera is marked as scanned, which is what the Label reader badge counts; opening it later doesn’t remove the mark. Products already in your History on 24 October 2026 count as scanned. | Your account. One entry per product, with the latest time. The saved score includes the effect of your goals. |
| Favourites: the products you mark with the heart (barcode, product name, brand, the score and rating the app last showed you, and when you added it) | You tap the heart on a product while signed in | Your account, so they’re on all your phones and can be checked for recipe changes. Up to 200. As in scan history, the saved score includes the effect of your goals. Kept until you tap the heart again to remove it, or delete your account. |
| Recipe changes: which changes we found to products in your History or favourites, and when you saw each one in the app | You have an account, and a product in your History or favourites changes its ingredients or allergen information on Open Food Facts | Your account. See “Recipe changes and notifications” below. |
| Badges: the badges and levels you’ve earned, when you earned them and when you saw each one in the app; how many ingredient explanations you’ve opened (a number, not which ones); when you first opened the research behind a rating; the last week you checked a product, how many weeks in a row you have, and your longest run; your phone’s time difference from UTC, so weeks run Monday to Sunday where you are; and when you started using badges. | You’re signed in and use the app. Your weeks are noted from your History each time a product is added to it, also before badges are shown to you; weeks from before badges came to Knowsie are worked out from the dates already in your History. Badges for your History (Label reader counts the products you scanned with the camera) and for products and problem reports you sent in (once our team approves them) are worked out from what we already keep, above. | Your account. No one else using Knowsie can see your badges, and there are no leaderboards. |
| A product you send in: photos (front, ingredients, nutrition label and any extras), its barcode, and the name, brand, ingredients, nutrition values, serving size and organic seal | You add a missing product, add a missing ingredients list, or update a product whose package looks different | Our database and private photo storage, reviewed by our team. If you’re signed in, it’s linked to your account. If not, it isn’t linked to anyone. |
| A problem report: your note, an optional photo and the product’s barcode | You tap “Report a problem with this data” on a product | Same as a product you send in |
| Feedback: the type you pick (idea, problem, name or logo idea, or other), your message, an optional screenshot or photo you choose to attach (signed in only, from app version 1.3.0), the app version, and your phone’s operating system and its version | You use Profile → Send feedback | Our database, read by our team. Linked to your account if you’re signed in. A screenshot is kept in private storage that only our team can open. |
| Emails you send us: your email address, your message and anything you attach | You write to one of our email addresses | Our mailbox, hosted by Google Workspace |
| Barcodes you scan and words you search for | You scan or search | Sent to Open Food Facts and to our database to find the product. They aren’t saved to your account, except as scan history or favourites (above). |
| Names of ingredients we don’t recognize yet, with the product’s barcode | A product you look at contains an ingredient we don’t know | Our database, not linked to you. We use it to grow our ingredient list. |
| Crash and error reports, and a short stability report each time you use the app | Only if you turn on crash reports. Then every time you use the app, and when something goes wrong. Your choice is kept on your phone. | Our crash reporting provider (Sentry). See “Who processes it”. |
| Subscription details (iPhone only for now): an anonymous ID, or your account’s random ID, and your purchases once there’s something to buy | Each time you open the app on iPhone | Our subscription provider (RevenueCat). Knowsie doesn’t sell anything yet. |
| Technical details: IP address, device model, operating system and app version, language, and random installation IDs | Whenever the app talks to one of our service providers | Each provider, as described under “Who processes it” |
The app never asks for your location, and we don’t collect your contacts. The app doesn’t read your photo library: we only receive a picture you choose yourself to attach to your feedback. Our server’s request logs do note the approximate area each connection comes from (such as the city), worked out from its IP address. We don’t use it, and those logs are deleted after 1 day on our current plan. The camera is used only to read barcodes (that happens on your phone) and to take the product photos you choose to send. Before a product photo or a problem report photo leaves your phone, the app saves a new copy of it without the details a camera hides in a photo (metadata), such as the phone model and the time it was taken. Please keep people and personal details out of those photos.
Screenshots in feedback. If you are signed in, you can attach a screenshot or photo from your phone when you send us feedback. We keep it privately with your message, and only the Knowsie team can open it. Before it is sent, the app makes a smaller copy without the photo’s location and camera details. A screenshot shows whatever was on your screen, so please only attach one you are happy for us to see. We delete it together with your message 12 months after you sent it.
Recipe changes and notifications
Recipe changes. Recipe changes and favourites need an account. For the products in your History that you’ve scanned or opened in the last 6 months, and for your favourites (up to 200 products per account, favourites first), our server checks Open Food Facts again, usually once a day. It sends only the barcodes, never anything about you or about who has the product. When a product’s ingredients or allergen information change, we record that the change is for your account, and when you saw it in the app. These records are deleted 6 months after we find the change, within a day once the product is in neither your History nor your favourites, or with your account. What a change means for you, given your allergies, typed allergens, diets, goals and watch list, is worked out on your phone; our servers don’t use your preferences for this. Your phone keeps the recipe changes listed for you, and what each one means for you, until you sign out.
To spot changes, our server keeps the latest Open Food Facts version of each product it checks, and the changes it finds. That’s product information, with nothing about who has the product. A product’s version is deleted once we stop checking it (and at least 7 days after we first saved it), and the changes 6 months after we find them.
Notifications (not available yet). The app doesn’t offer push notifications yet, so for now you’ll find recipe changes only in the app. When we add them, they’ll work like this, and we’ll update this policy first if anything changes:
- Knowsie will send them only if you turn them on in the app and allow them when your phone asks. You’ll be able to turn them off at any time in Profile → Preferences or in your phone’s settings.
- Their text will always be one of two short messages: “A product from your history or favourites changed its recipe.” or, for two or more products, “Some products from your history or favourites changed their recipes.” They’ll never name a product, ingredient, allergen, diet or score, and you’ll get at most one a day.
- While they’re on, we’ll store your phone’s push token (an Expo push token), its platform, the app version and when the app last ran on it while you were signed in, linked to your account, and we’ll note which recipe changes a notification told you about. We’ll delete the token when you turn notifications off in the app (if you do it in your phone’s settings, the next time the app starts while you’re signed in), sign out on that phone or delete your account, when Expo tells us it no longer works (for example, after you delete the app), or 180 days after the app last ran there while you were signed in. If you turn them off or sign out while you’re offline, the app tells us the next time it starts with an account signed in. For each notification we send, we’ll keep Expo’s ticket number with the token until we get Expo’s receipt for it, for at most 2 days.
- To create the token, the app will send Expo the push address Apple gives your phone, a random ID for this installation and the app’s ID. Notifications will go through Expo and Apple Push Notification service. They’ll start on iPhone; Android isn’t supported yet.
- If you sign out, that phone stops getting notifications. Your choice is remembered on the phone and applies again if you sign back in with the same account.
Badges
If you’re signed in, we keep your badges in your account: which badges and levels you’ve earned, when you earned them and when you saw each one in the app; how many ingredient explanations you’ve opened (a number, not which ones); when you first opened the research behind a rating; your run of weeks with at least one product checked, noted from your History; your phone’s time difference from UTC, so your weeks start on your Monday; and when you started using badges. No one else using Knowsie can see them, there are no leaderboards, and they’re deleted with your account.
What stays on your phone
- Your preferences, how far you’ve got in the app tour, and which one-time notices in the app you’ve already seen.
- If you’re signed in: a copy of your favourites (with any changes to them not yet sent), and the recipe changes listed for you, with the product versions they compare and what each change means for you. They’re removed when you sign out.
- If you’re signed in: for up to 200 products you’ve opened, the product as you last saw it and how we read its label then, so the app can show “Score updated” when a change to our ingredient database moves its score. It isn’t sent anywhere, and it’s removed when you sign out.
- Your badges. Without an account: the badges you’ve earned, which ingredient explanations you’ve opened (so each counts once), when you first opened the research behind a rating, whether you’re a Founding tester (worked out from when Knowsie was installed on this phone; if you sign in, your account gets only a yes or no, never the date), and which of these badges you were already shown while signed in, so they aren’t celebrated twice. They’re added to the account you sign in to on this phone, each time you sign in. With an account: a copy of your badges and the ingredient explanations you’ve opened on this phone (only their number is sent to your account), removed when you sign out.
- To tell you what happened, the app keeps a short list of what you sent from your phone (a reference number, the barcode and the product name) on the phone, and asks us about those reference numbers only. Deleting your account also removes that list for the account from the phone.
- Your sign-in, so you stay signed in until you sign out. It includes your email address, your account’s random ID and, with Google sign-in, your name and profile picture link.
- Your light or dark mode choice, and whether you turned crash reports on or off.
- A count of your first 5 scored scans. On iPhone, it’s used once, to ask Apple to show its rating window (only if you installed Knowsie from the App Store). Apple handles any rating you give, and nothing about it is sent to us. On Android, the app doesn’t ask for ratings.
- A copy of our ingredient database, and the photos you take in the app, in the app’s temporary storage until your phone clears it.
- Random IDs that our update provider, and our crash reporting provider if you turned crash reports on, keep for this installation. On iPhone, also one for our subscription provider, and on Android, one for Google’s barcode reader (see “Who processes it”).
How we use it
- To score products. The base score is the same for everyone. If you choose nutrition goals, they can move your score up or down by up to 15 points. Your allergies, typed allergens and diets add warnings, and the alternatives we suggest leave out products whose information conflicts with them. Your watch list adds alerts. None of these four change the score.
- To keep your scan history and favourites in your account when you’re signed in, and your preferences too if you agree, so they’re there on your other devices.
- To check the products in your History and your favourites for recipe changes, and show you in the app what changed and what it means for you.
- To show you badges for being curious and for helping: scanning, reading about ingredients, adding products and reporting problems. They never depend on what you eat, and no one else using Knowsie can see them. When you tap Share on a badge, your phone gets a short text with a link to knowsie.app; we don’t see what you share or with whom.
- To read the label photos you take and fill in the product’s details for you to check.
- To review products and reports you send in, and add them, or the corrections, to our product database, where every user can see them. A front photo you send, or a photo from a problem report, may become the product’s picture.
- To read your feedback and your emails, and answer them.
- To find and fix bugs and keep the app stable, using crash, error and stability reports, if you turned them on.
- To run your account and, later, your subscription.
- To grow our ingredient list from the ingredient names we don’t recognize.
We don’t use your data for advertising, and we don’t sell it.
Legal bases
Data protection laws, such as the GDPR in the EU and the UK, ask us to name the legal reason (the “legal basis”) for each use of your data. We rely on four:
- Contract: we need the data to give you a feature you asked for (Article 6(1)(b) GDPR).
- Consent: you said yes, and you can take it back at any time (Article 6(1)(a)). For health information and beliefs, it’s your explicit consent (Article 9(2)(a)).
- Legitimate interests: we have a good reason that doesn’t outweigh your rights, such as keeping Knowsie secure or the product database accurate (Article 6(1)(f)). You can object to these uses (see Your choices and rights).
- Legal obligation: a law requires us to keep the data (Article 6(1)(c)).
| What | Why | Legal basis | How long |
|---|---|---|---|
| Your account: email address, password (scrambled), the details Google or Apple pass on when you sign in with them, and whether you finished the first-run setup | To create your account and sign you in | Contract | Until you delete your account |
| Sign-in records: the IP address and device type of each sign-in | To keep you signed in, and to keep accounts secure | Contract; legitimate interests (security) | Until you sign out on that device or delete your account |
| Preferences in your account: allergies, typed allergens, diets, nutrition goals and watch list | To show your warnings, adjust your score for your goals, leave conflicting products out of the alternatives, and explain what a recipe change means for you, on every phone you sign in on | Explicit consent | Until you clear them, withdraw your consent or delete your account |
| Your answer to saving your preferences in your account: when you agreed, when you withdrew if you do, and which version of the question you saw | To be able to show that you agreed, as the law requires | Legal obligation (Article 7(1)) | Until you delete your account |
| Scan history, favourites, recipe change records and badges | To give you these features | Contract | Until you delete your account. A favourite goes when you remove its heart. Recipe change records: 6 months at most. |
| Products and problem reports you send in, with their photos | To read your label photos and show you a score, then to review what you sent and add it, or the correction, to our product database | Contract (reading your photos and scoring them); legitimate interests (a product database that’s accurate for everyone) | Approved ones stay in the product database, linked to your account until you delete it. Rejected ones: 90 days after we review them. |
| Feedback, with any screenshot | To read and answer it, and to improve the app | Legitimate interests | 12 months |
| Emails you send us, and our replies | To answer you | Legitimate interests; contract, when it’s about your account | About 2 years after the conversation ends |
| Password reset emails we send you | To help you set a new password | Contract | Our copies: about 3 months |
| Barcodes you scan and words you search for | To find the product | Contract | Not saved, except as scan history or favourites. Server request logs: 1 day. |
| Names of ingredients we don’t recognize yet | To grow our ingredient list | Legitimate interests | Not linked to you |
| Server request logs | To run Knowsie and keep it secure | Legitimate interests | 1 day |
| Crash, error and stability reports | To find and fix bugs | Consent: only if you turn crash reports on | 30 days |
| Subscription details (iPhone only for now) | To run your subscription once there’s something to buy, and to have it ready until then | Contract, once you subscribe; until then, legitimate interests | While Knowsie uses RevenueCat, unless we delete them sooner (see How long we keep it) |
| Update checks | To deliver app updates, including fixes | Legitimate interests | Handled by Expo under its own privacy policy |
| Records of sales, once subscriptions start | To meet tax and accounting rules | Legal obligation | As long as those rules require |
Your preferences on a phone where you’re not signed in stay on that phone and never reach our servers. More detail on each period is under How long we keep it.
Who processes it
Knowsie relies on these services. Each receives only what its job needs.
| Service | What it does for Knowsie | What it receives |
|---|---|---|
| Supabase | Hosts our database, accounts, photo storage and server functions. Its servers are in the United States (Oregon). | Everything we keep on our servers, listed under “What we collect”, except crash reports, subscription details, update checks and emails. Also the IP address and device type of each sign-in, and short-lived logs of the app’s requests (kept for 1 day on our current plan). These logs include IP addresses, the approximate area worked out from them (such as the city), and the barcodes and search words looked up, and can show which account made a request. |
| Anthropic (Claude) | Reads your label photos to fill in the name, brand, ingredients, nutrition values and organic seal. During our review, it also suggests a product category. | The front, ingredients and nutrition photos you’ve taken. They’re sent as soon as you add an ingredients or nutrition photo, before you tap Submit, and even if you then cancel. For a category suggestion, only a product’s name, brand and ingredients. Requests go through our server, so Anthropic doesn’t get your account, IP address or device details. Anthropic deletes this data within 30 days, unless the law requires it to keep it longer or its safety systems flag it as breaking Anthropic’s usage policy. By default, Anthropic doesn’t use this data to train its models. |
| Open Food Facts | The public, collaborative product database the app looks products up in. It’s based in France. | The barcodes you scan and the words you search for. When we look for alternatives: a product’s category and country, or words from its name and brand if it has no category. Like any website, it also sees your IP address, including when product pictures load from its servers. To check for recipe changes, our server also sends it the barcodes of products in our users’ History and favourites, with nothing about who has them. We never send it your account, preferences or photos. |
| Sentry | Crash and error reports, only if you turn them on | Nothing while crash reports are off. When they’re on: a short stability report every time you use the app. When something goes wrong: device details (such as model, operating system, memory, language and time zone settings), app version and update, a random installation ID, and the app’s recent activity before the problem. That activity includes which buttons you tapped (by their names in our code) and the web addresses the app called, with barcodes, search words, account IDs and email addresses removed before the report leaves your phone. Never your name or email. Your IP address isn’t stored with the reports. Sentry keeps them for 30 days, in the United States. |
| RevenueCat | Will manage subscriptions. It already runs on iPhone from version 1.2.0, before anyone can buy anything. It doesn’t run on Android yet. | An anonymous ID, or your account’s random ID when you’re signed in. Your device, operating system and app version, language, App Store country and IP address. Once subscriptions start, the purchases Apple confirms. Never your card details. Its servers are in the United States. |
| Expo (EAS Update) | Delivers app updates | Each time you open or return to the app, it checks for an update. The check includes the app version and update, your phone’s platform, a random installation ID and your IP address. It doesn’t include your account or anything you’ve entered in the app. |
| Apple | On iPhone only: Sign in with Apple, if you choose it. App Store payments once subscriptions start, and the rating window. | What you agree to share with Apple. Apple handles payments, so we never see your card details. |
| Sign in with Google, if you choose it. Google Workspace also hosts our email. On Android, the app reads barcodes with Google’s ML Kit, which does the reading on your phone. | What you agree to share with Google, the emails you send us and our replies, and the password reset emails we send. On Android, ML Kit sends Google usage data for diagnostics and analytics: device model and operating system, app version, a random installation ID, and performance and error details. It doesn’t send the barcodes it reads or your photos, and it isn’t linked to your account. |
Product information from Open Food Facts is available under the Open Database License (ODbL).
Ingredient pages link to research and official sources. If you open one, that website sees your visit, and its own privacy policy applies.
Our website, knowsie.app, is hosted by GitHub Pages. GitHub logs visitors’ IP addresses for security. The website serves its own fonts, and it uses no cookies and no analytics. Its password reset page, which opens from the link in a reset email, loads Supabase’s sign-in code from jsDelivr, a public service that delivers code to websites, so jsDelivr sees your IP address when you open that page. The new password you type there goes straight to Supabase, our sign-in provider, over an encrypted connection. On the beta testers page, the checklist remembers which items you ticked, in your browser’s own storage on your device. It never leaves your browser, and we can’t see it. Clearing this site’s data in your browser removes it.
Where they are, and how transfers are protected
Some of these services work for us and use your data only on our instructions (“processors”). Others decide for themselves how they use what they receive, under their own privacy policies (“independent controllers”): Open Food Facts; Apple and Google, when you sign in with them, use their stores or, on Android, Google’s barcode reader; Expo, for update checks; and GitHub and jsDelivr, for visits to our website.
When data from the EU, the UK or Switzerland goes to the United States, it’s protected in one of two ways. Either the company is certified under the EU-U.S. Data Privacy Framework, with its UK Extension and the Swiss-U.S. Data Privacy Framework, or its agreement includes the European Commission’s standard contractual clauses, with the UK and Swiss additions. The Data Privacy Framework covers only the United States, so where Google keeps data in other countries, standard contractual clauses protect it there. Data that goes to the UK needs neither: the EU and Switzerland recognise that the UK protects data well enough. We checked each US company against the official Data Privacy Framework list at dataprivacyframework.gov on 27 October 2026.
| Service | What for | Role | Where | How transfers are protected |
|---|---|---|---|---|
| Supabase | Our database, accounts, photo storage and server functions | Processor | United States (Oregon) | Standard contractual clauses in its data processing agreement |
| Anthropic | Reading label photos, and category suggestions | Processor | United States | Standard contractual clauses in its data processing agreement |
| Sentry | Crash and error reports, only if you turn them on | Processor | United States | Data Privacy Framework (EU, UK and Swiss) |
| RevenueCat | Subscriptions (iPhone only for now) | Processor | United States | Standard contractual clauses in its data processing agreement |
| Google Workspace | Our email | Processor | United States and other countries where Google has data centres | Data Privacy Framework (EU, UK and Swiss) in the United States; standard contractual clauses in Google’s data processing terms for other countries |
| Open Food Facts | The product database the app looks products up in | Independent controller | France | Not needed: it’s in the EU |
| Apple | Sign in with Apple, the App Store and the rating window | Independent controller | United States | Standard contractual clauses, as described in Apple’s privacy policy |
| Sign in with Google, Google Play (where you get the app on Android), and on Android, the barcode reader (ML Kit) | Independent controller | United States and other countries where Google has data centres | Data Privacy Framework (EU, UK and Swiss) in the United States; standard contractual clauses for other countries, as described in Google’s privacy policy | |
| Expo | Checks for app updates and delivers them | Independent controller | United States | Data Privacy Framework (EU, UK and Swiss) |
| GitHub | Hosts our website, and logs visitors’ IP addresses for security | Independent controller | United States | Data Privacy Framework (EU, UK and Swiss) |
| jsDelivr | Delivers the sign-in code that our password reset page loads | Independent controller | United Kingdom (the company, Volentio JSD Limited). Its delivery networks, Cloudflare, Fastly and Gcore, serve the code from servers around the world. | Not needed for the UK. jsDelivr’s privacy policy covers its delivery networks. |
Health information
Allergies, typed allergens and nutrition goals can count as health information. Halal and kosher diets can reveal religious beliefs, and vegan or vegetarian diets can reveal other beliefs. We use them only to personalize the app: your warnings, the effect of your goals on your scores, the alternatives we suggest, and what a recipe change means for you (worked out on your phone). We never use them for advertising, and we never sell them.
They’re optional. You can choose them when you first open the app or later. You can leave them empty, change them or clear them at any time in Profile → Preferences. If you’re not signed in, they stay on your phone.
Your consent. If you’re signed in, we save them in your account only if you agree. The app asks you once: when you first choose them while signed in, when you sign in with preferences already on your phone, or, if you already had an account, once after this update. The question names these kinds of data and what we use them for, and the box isn’t ticked for you. We keep a record of your answer in your account: when you agreed, when you withdrew if you do, and which version of the question you saw. If you don’t agree, your preferences stay on your phone only, we remove any copy already in your account, and the app keeps working with them on your phone. You can change your answer, or withdraw your consent, at any time in Profile → Preferences (see Your choices and rights).
Older versions of the app. The question comes in an app update. Your phone downloads it while the app is open, and it starts working when you tap Restart on “A new version is ready”, or the next time the app starts. Until then, if you’re signed in, the app keeps saving your preferences in your account without asking, as before. Versions before 1.0.15 can’t receive the update at all, so if you’re signed in on one, it keeps doing this. Please update the app.
Not medical advice. Knowsie gives general information about food ingredients. It isn’t medical advice, and it doesn’t replace a doctor, dietitian or pharmacist. Your preferences help the app point things out, but product and allergen details come from labels, Open Food Facts and people who send in products, so they can be incomplete, out of date or wrong, and recipes change. Always read the package, and if you have an allergy or a health condition, follow your doctor’s advice.
How long we keep it
- Account, preferences, scan history and favourites: until you delete your account (a favourite also goes when you remove its heart). Deleting your account in the app removes them from our servers right away, together with your recipe change records. If you ask us by email instead, we delete them within 7 days. Our current database plan doesn’t include backups, so we don’t keep a backup copy.
- Recipe change records: 6 months after we find the change, within a day once the product is in neither your History nor your favourites, or with your account.
- Badges and badge counters: until you delete your account. On your phone: a guest’s badges until you delete the app; a signed-in copy until you sign out or delete your account in the app.
- Favourites and recipe changes on your phone: until you sign out or delete your account in the app. If your sign-in ends some other way, for example because you deleted your account on another phone, they stay on that phone until you delete the app there, or sign in there again with the same account and then sign out.
- Sign-in records (IP address and device type): until you sign out on that device or delete your account. Deleting the app without signing out doesn’t end them.
- Preferences on your phone: if you’re not signed in, until you clear them or delete the app. If you’re signed in, until you sign out or delete your account in the app. If your sign-in ends some other way, for example because you deleted your account on another phone, they stay on that phone until you sign out there or delete the app.
- Products and problem reports you send in, with their photos: kept while we review them. Approved ones become part of our product database and stay there. Ones we reject are deleted, with their photos, 90 days after we reject them.
- If we don’t add a product you sent us, or don’t change a product after your report, we keep the reason with your submission (one choice from a short list, or a short note from our team) and delete it together with the submission 90 days after we reviewed it. Approved submissions are kept as product data, as before.
- Feedback, with its screenshot: deleted 12 months after you send it. A screenshot whose message never reached us is deleted after 7 days.
- Your answer to saving your preferences in your account (when you agreed, when you withdrew if you do, and which version of the question you saw): until you delete your account.
- Emails you send us, and our replies: deleted about 2 years after the conversation ends. Every 3 months, we delete the conversations that ended more than 2 years ago and empty the mailbox’s trash. Ask us and we’ll delete yours sooner.
- Password reset emails: our mailbox keeps a copy of each one we send. Every 3 months, we delete these copies and empty the mailbox’s trash, so each copy is kept for about 3 months. Ask us and we’ll delete yours sooner. The link in it works only once, for a limited time.
- Server request logs: 1 day on our current plan.
- Crash and error reports, if you turned them on: 30 days. Turning crash reports off stops new ones; the ones already sent are deleted when their 30 days are up.
- Subscription records (iPhone only): kept by RevenueCat for as long as Knowsie uses RevenueCat, unless we delete them sooner. Write to us and we’ll have yours deleted within 7 days. Once subscriptions start, records of sales that tax and accounting rules require us to keep are kept for as long as those rules require.
- Update checks: handled by Expo under its own privacy policy. They don’t include your account.
- Label photos read by Anthropic: deleted by Anthropic within 30 days, except in the cases described under “Who processes it”.
- Read-outs of your label photos (the details Anthropic read from the label, never the photos themselves, and nothing that links them to your account, IP address or device): kept on our server for 15 minutes so the app can ask again if the answer didn’t reach your phone, and deleted within 30 minutes.
Your choices and rights
- Use Knowsie without an account. Your preferences then stay on your phone. The barcodes, searches, photos, reports and feedback you send still leave your phone, as described above.
- Change or clear your preferences at any time in Profile → Preferences. Clearing them doesn’t change your answer about saving them in your account.
- Withdraw your consent to us keeping your preferences in your account at any time: turn off saving them in your account in Profile → Preferences, or write to privacy@knowsie.app. We then remove them from our servers and note in your account that you withdrew, so none of your phones saves them there again unless you agree again. Your preferences stay on your phone, so your warnings keep working. Deleting your account also removes them. Withdrawing doesn’t change how we used them before.
- Crash reports are off unless you turn them on. The app asks you once, and you can turn them on or off at any time in Profile.
- Sign out in Profile. That also clears your preferences, favourites and recipe changes from that phone.
- Remove a favourite at any time by tapping its heart again.
- Delete your account in Profile → Account settings → Delete account. It takes effect right away. Products, reports and feedback you sent stay (until the times listed above), but the link to your account is removed. Screenshots you attached to feedback are deleted with your account. A few things don’t go away on their own yet. Write to privacy@knowsie.app and we’ll remove them:
- Our photo storage still notes which account uploaded each photo.
- If you used Knowsie on iPhone, RevenueCat keeps its record of your account’s random ID.
- No longer have the app? Email privacy@knowsie.app from your account’s email address, and we’ll delete your account within 7 days. See Delete your Knowsie account for the steps, and what we delete and what stays.
- Copies of your preferences, favourites and recipe changes on your other phones stay until you sign out there (while that phone is still signed in) or delete the app.
- If you signed in with Apple, the app can also ask Apple to end Knowsie’s access when you delete your account. Check that it’s gone: on your iPhone, open Settings, tap your name, then tap Sign in with Apple (on some versions of iOS, it’s under Sign-In & Security). If Knowsie, or Malvi, its earlier name, is still listed, choose it and tap Delete. You can also check at account.apple.com, under Sign-In & Security → Sign in with Apple.
- There’s no way yet to delete single scan history entries in the app. Write to us and we’ll do it.
- If you’ve forgotten your password, tap “Forgot password?” on the app’s log-in screen, and we’ll email you a link to set a new one. If that doesn’t work, or you can’t sign in, write to support@knowsie.app from the email address you signed up with, and we’ll help.
Your rights
Depending on where you live (for example the EU or the UK), some or all of these may be legal rights. We offer them to everyone. You can:
- ask what data we have about you, and get a copy (access);
- ask us to correct data that’s wrong (rectification);
- ask us to delete your data (erasure);
- ask us to stop using your data for a while and only keep it, for example while we check whether it’s correct (restriction);
- ask for the data you gave us in a common format you can take elsewhere (portability);
- object to the uses that rely on our legitimate interests (objection);
- withdraw your consent at any time, wherever we rely on it. That doesn’t change how we used your data before.
Write to privacy@knowsie.app. We may ask you to confirm it’s you, usually by writing from your account’s email address. We answer without undue delay, and within a month. If a request is complex, or you send us several, we may need up to two more months; if so, we’ll tell you why within the first month.
In the EU and the UK, you can also complain to a data protection authority, for example where you live or work. In Poland, that’s the UODO; in the UK, the ICO.
No automated decisions about you. Scores, warnings and the alternatives we suggest are worked out automatically, from the label and your preferences. They’re information to help you choose food, not decisions about you with legal or similarly significant effects (Article 22 GDPR).
We don’t sell your personal information, and we don’t share it for advertising, in the sense California law uses those words.
If you live in Washington State or Nevada
Washington’s My Health My Data Act and Nevada’s consumer health data law protect information about your health. In Knowsie, that can include your allergies, typed allergens, diets, nutrition goals and watch list. Whether or not these laws apply to Knowsie, we give you the rights they describe. You can:
- ask whether we collect, share or sell this data, and see it, with a list of anyone we’ve shared it with and how to contact them. We don’t sell it, and we don’t share it: it’s stored in your account by Supabase, which works for us as our database provider, and only if you agreed (older versions of the app don’t ask; see Health information);
- withdraw your consent, so we stop collecting it in your account (see Health information);
- ask us to delete it. We delete it from our systems and tell our service providers to delete it too. Our current database plan doesn’t include backups, so there’s no backup copy to wait for.
Write to privacy@knowsie.app. You don’t need a Knowsie account to ask. Requests are free, up to twice a year. We answer within 45 days. If we need more time, we may take up to 45 more days, and we’ll tell you why within the first 45. If we turn down your request, you can appeal: reply to our answer with “Appeal” in the subject. We’ll tell you in writing what we decided, and why, within 45 days. If we turn down your appeal, we’ll tell you how to contact your state’s Attorney General.
Children, security and international transfers
Children. Knowsie isn’t meant for children under 16, and we don’t knowingly collect their data. If you think a child has given us data, write to us and we’ll delete it.
Security. Data travels encrypted between the app and our services. On your phone, your sign-in is kept in the app’s own storage, which other apps can’t read. Apart from the AI service that reads label photos (see “Who processes it”), only our team can open the photos you send before they’re approved. If we approve a product and use one of its photos as the product’s picture, that photo becomes public: anyone with its web address can see it. No system is completely secure, so we can’t guarantee it.
International transfers. Supabase, RevenueCat and Sentry keep the data they receive from Knowsie in the United States. Anthropic, Expo, Apple, Google and GitHub (which hosts our website) are US companies, and may process data there too. Open Food Facts is in France, and jsDelivr, which delivers code for our password reset page, is in the UK. How each transfer from the EU, the UK and Switzerland is protected is listed under Where they are.
Changes and contact
If we change this policy, we’ll update the date at the top. For important changes, we’ll also tell you in the app first.
Knowsie is run by Malwina Stachurska.