Privacy Policy

Who we are

Muninn is operated by Shonny Kurian Mathew, an individual based in Westmead, New South Wales, Australia ("we", "us", or "our").

Muninn is an AI-powered food ingredient analysis application. This policy explains what personal data we collect, why, how long we keep it, who we share it with, and what rights you have. We do not sell your data, show you ads, or build profiles for marketing purposes.

This policy should be read alongside our Terms of Service, which contains the health and AI disclaimer and liability limitations that apply to your use of the app.

Information we collect

• Account info (Google or Apple) — when you sign in with Google or Apple, we receive your display name and email address via Firebase Authentication. For Google, we request only the email and profile OAuth scopes — we never access your Google Drive, Gmail, contacts, calendar, or any other Google service, and your Google profile photo is displayed in the app but not stored on our servers. For Apple, we receive only the name and email you choose to share at sign-in — if you use Apple's "Hide My Email" option, we only ever see the private relay address Apple generates. We never see your Google or Apple account password.
• Scan history — the product names, barcodes, small thumbnail images (compressed to approximately 80 × 80 px), and timestamps of products you scan. Scanning requires sign-in, and your scan history is stored on our servers so it can sync across your devices. It is deleted when you delete your account.
• Health profile (sensitive data) — the health conditions you voluntarily choose, such as pregnancy, diabetes, or food allergies. This data is stored on your device only (IndexedDB) and is never sent to or stored on our servers. Used only to personalise the ingredient warnings we display. You can clear it at any time by removing conditions from your profile or clearing browser/app data.
• Nickname — an optional username (3–10 characters) you may choose. This is visible on the community contributor leaderboard. You can skip, change, or remove it at any time.
• Anonymous device ID — a randomly generated UUID stored in your browser's local storage. Used solely to rate-limit API requests and prevent abuse. It is not linked to your name or email. If you later sign in, this device ID may be associated with your account in our server logs.
• Ingredient label photos — if you photograph a product's ingredient list, that image is transmitted to our server over an encrypted connection for AI text extraction. We do not store the photo. It is processed by Google Gemini and then discarded. Google processes it subject to their own data retention terms (see Third-Party Services below).
• Server logs — our servers automatically record your IP address, the type of request made, a timestamp, and whether the request succeeded or failed. These logs are used exclusively for security monitoring and debugging. They are retained for up to 30 days and are not archived by us.
• User-submitted corrections — if you submit a correction to a product's ingredient data, we store your Firebase UID alongside the correction to prevent duplicate submissions. The correction content itself (ingredient names) is not personal data.

Why we process your data (lawful bases)

For users in the EU/EEA, we rely on the following legal bases under GDPR Article 6 (and Article 9 for health data):

For Australian users, we collect personal information in accordance with the Australian Privacy Principles (APPs) under the Privacy Act 1988 (Cth). Health information is collected with your explicit consent under APP 3.3.

How we use your information

• To analyse food ingredients and show you an AI-generated safety score and per-ingredient breakdown.
• To apply personalised health-condition warnings (for example, flagging an ingredient that may be harmful during pregnancy). We only do this if you have explicitly provided health conditions in your profile.
• To save and synchronise your scan history across devices when you are signed in.
• To improve the accuracy of our ingredient database using corrections you voluntarily submit.
• To prevent abuse and rate-limit API usage via the anonymous device ID.
• To monitor server security and debug technical issues via server logs.

We do not use your data to train AI models. We do not use your health data for any purpose other than displaying warnings to you.

Third-party services & international data transfers

Muninn uses the following services to operate. Each receives only the minimum data needed for its function. Your data may be transferred to and processed in the countries shown below.

• Firebase / Google US — authentication (Google sign-in, and Apple sign-in processed through Firebase Authentication). Firebase stores your Firebase UID, email, and display name. Subject to Firebase Privacy Policy. Google participates in the EU–US Data Privacy Framework.
• Apple US — Sign in with Apple. Apple provides your name and email (or a private relay email if you choose to hide it) directly to our Firebase authentication flow. Subject to Apple's Privacy Policy.
• Google Gemini AI US — processes ingredient label photos for OCR text extraction, and serves as a fallback AI for ingredient analysis. Photos are sent to Google's API; Google's terms govern their handling. Subject to Google's Privacy Policy.
• DeepSeek AI China — classifies and analyses food ingredient names (e.g., "sodium benzoate") to determine safety tier. Only ingredient names are sent — no personal data, no health profile, no user identifiers. Subject to DeepSeek Privacy Policy. DeepSeek is operated by Hangzhou DeepSeek Artificial Intelligence Co., Ltd., People's Republic of China. EU users should be aware this is a transfer to a country without an EU adequacy decision; we rely on the fact that only non-personal ingredient names are transferred.
• MongoDB Atlas US — cloud database hosting for scan history, nickname, and ingredient data. Data is encrypted at rest (AES-256) and in transit (TLS 1.2+). Subject to MongoDB Privacy Policy.
• Fly.io US — server infrastructure hosting the Muninn backend API. Subject to Fly.io Privacy Policy.
• Vercel US — hosting for the Muninn web application (frontend). Vercel may log IP addresses for CDN routing. Subject to Vercel Privacy Policy.
• Open Food Facts France — an open, non-commercial product database. When you scan a barcode, that barcode number is sent to their API to retrieve the product name and ingredient list. Open Food Facts does not receive your identity. Subject to Open Food Facts Privacy Policy.

For EU/EEA users: transfers to the United States rely on Standard Contractual Clauses (SCCs) or equivalent safeguards maintained by each provider. The transfer to DeepSeek involves only non-personal ingredient vocabulary data — no user identifiers or health information are ever sent to DeepSeek.

Data security

• In transit: all communication between your device and our servers, and between our servers and third-party services, uses HTTPS (TLS 1.2 or higher).
• At rest: personal data stored in MongoDB Atlas is encrypted at rest using AES-256.
• Access control: the production database is accessible only from the Muninn backend server. No public access is permitted.
• Authentication: user authentication is handled entirely by Firebase — we never store passwords.
• Breach notification: if we become aware of a data breach that is likely to result in a risk to your rights, we will notify affected users and, where required, the relevant supervisory authority (for EU users: within 72 hours of becoming aware; for Australian users: in accordance with the Notifiable Data Breaches scheme under the Privacy Act 1988).

No system is 100% secure. If you discover a vulnerability, please contact us at muninn@krobim.com before public disclosure.

Analytics and tracking

We do not use Google Analytics, Mixpanel, Meta Pixel, or any other third-party analytics or advertising SDK. We do not place tracking cookies of any kind. The only data stored in your browser is:

• A random device UUID in localStorage — for rate-limiting only
• Your local scan cache in IndexedDB — so your recent scans are available offline
• Your health profile (conditions) — stored locally on your device only, never sent to our servers

You can clear all of this at any time by clearing your browser's site data for unveilr.vercel.app.

Data sharing

We do not sell your personal information. We do not share your personal information with advertisers, data brokers, or marketing platforms.

California residents (CCPA/CPRA): We do not sell or share your personal information as defined under the California Consumer Privacy Act. No opt-out mechanism is needed because we do not engage in such sales or sharing.

Your data is shared only with the third-party services listed above, and only to the extent necessary to operate the app. If we are ever required to disclose your data by law or court order, we will notify you unless prohibited from doing so.

Data retention

Account data is retained until you delete your account. If you would like to have your data deleted without deleting your account, contact us at muninn@krobim.com with subject line "Data Deletion Request".

Your rights

Your rights depend on where you live. We honour all of the following upon request:

To exercise any right, email muninn@krobim.com with the subject line "Privacy Request". We will respond within 30 days. For account deletion, the fastest method is to use the Delete Account option inside the app — this takes effect immediately.

Account deletion

You can delete your account at any time from the Account menu inside Muninn. Deletion immediately and permanently removes your scan history, nickname, and all other server-held personal data. Your health profile (conditions) is stored on your device only and is not affected by account deletion — to remove it, clear the app's local data or uninstall the app. This cannot be undone. Server logs that include your IP address are purged on their 30-day cycle regardless of account deletion.

If you open Muninn without signing in, no personal data is stored on our servers — scanning and analysis require sign-in.

Children's privacy

Muninn is not directed at children under 13 and does not knowingly collect personal information from children under 13. Users aged 13–17 may use the app with parental consent, as described in our Terms of Service.

If you believe a child under 13 has provided personal information to Muninn, please contact us immediately at muninn@krobim.com and we will delete it promptly.

Changes to this policy

We may update this policy from time to time. For material changes — changes that affect how we use your personal data or your rights — we will provide at least 14 days' advance notice via email (for signed-in users) or via a prominent in-app notice before the change takes effect.

Non-material changes (corrections, clarifications, new third-party service disclosures that do not change data use) will be reflected by updating the "Last updated" date above. Continued use of the app after a material change takes effect constitutes acceptance of the revised policy.

Governing law

This policy is governed by the laws of New South Wales, Australia. For EU users, nothing in this policy limits your rights under the GDPR or the jurisdiction of your local supervisory authority. For Indian users, the Digital Personal Data Protection Act 2023 applies to the extent mandatorily applicable.

Contact

For privacy questions, data access requests, or concerns:

• Email: muninn@krobim.com — subject line "Privacy Request"
• Operator: Shonny Kurian Mathew
• Location: Westmead, New South Wales, Australia
• Response time: within 30 days of receipt

If you are an EU resident and are not satisfied with our response, you have the right to lodge a complaint with your local data protection authority.