Privacy Policy for Lychee

Last Updated: October 10, 2026

Effective Date: October 10, 2026

Introduction

Welcome to Lychee. This Privacy Policy explains what information Lychee collects, how we use it, what third-party services we rely on, and the choices you have.

For support and privacy requests, use the Lychee support form. The controller’s identity and contact details are in Section 12.

Lychee is a product scanner and ingredient explainer for food and cosmetic products. The App helps users review allergens, dietary preferences, ingredient lists, nutrition labels, additives, processing signals, cosmetic ingredient concerns, and product database information. Lychee is not a medical service, allergy-management service, diet program, nutrition coach, or cosmetic safety certification service.

This policy covers the Lychee mobile application ("App"), website, and web checkout. It explains data processing; it does not replace a consent request where consent is required.

1. Information We Collect

1.1 Information You Provide

Preferences and profiles

Product contributions and corrections

1.2 Information Collected Automatically

Scan and product data

Scan history is primarily stored locally on your device unless you use AI analysis, submit a contribution or report, or limited analytics as described below.

Usage and device data

Subscription data

2. How We Use Information

2.1 Core App Functionality

2.2 Product and Ingredient Coverage

2.3 AI-Powered Analysis

2.4 Subscriptions and Trials

2.5 Advertising and Attribution

2.6 Analytics and Improvement

3. Third-Party Services

3.1 Open Food Facts

Data shared: Product barcodes, product images, ingredient information, nutrition information, packaging information, and corrections when you contribute food product data.

Purpose: Lookup and contribution to an open food product database.

License: Open Database License (ODbL)

Data information: https://world.openfoodfacts.org/data

3.2 Open Beauty Facts

Data shared: Cosmetic product barcodes, product images, ingredient label images, ingredient information, and corrections when you contribute cosmetic product data.

Purpose: Lookup and contribution to an open cosmetic product database.

License: Open Database License (ODbL)

Data information: https://world.openbeautyfacts.org/data

3.3 OpenAI

Data shared: Label photos when you use AI image scanning or photo enrichment, ingredient/label text, questions you submit, selected health goals and concerns, and product context needed for AI analysis.

Purpose: AI-powered allergen, ingredient, nutrition, and cosmetic product explanations.

Important notes:

Privacy Policy: https://openai.com/policies/privacy-policy

3.4 Google AdMob

Data shared: Device and advertising identifiers where permitted, IP address and approximate location derived from it, device model, app/ad interactions, crash, diagnostic, and performance information used for advertising delivery, measurement, and reliability.

Purpose: Serve ads to non-Premium users and support free access to the App.

Privacy Policy: https://policies.google.com/privacy

Ad Personalization: https://adssettings.google.com

3.5 Meta/Facebook SDK

Data shared: App install and app activation events, limited marketing events such as completed onboarding, checkout started, trial started, and subscription started, device/app information, and advertising identifiers where permitted.

Purpose: Measure whether Meta and Instagram ads lead to app installs or subscription events, optimize advertising campaigns, and understand campaign performance.

Important notes:

Privacy Policy: https://www.facebook.com/privacy/policy/

3.6 PostHog

Data shared: Product analytics events, such as onboarding progress and answers (including selected health-goal and concern identifiers), feature usage, scan behavior, timing/error information, app version, and device platform. Events use persistent pseudonymous installation/user identifiers; this does not make the records fully anonymous.

Purpose: Understand how the App is used, monitor performance, identify onboarding drop-off points, and improve features.

Important notes:

Privacy Policy: https://posthog.com/privacy

3.7 RevenueCat and Stripe

Data shared: App customer identifier, product identifiers, purchase/renewal status, trial and entitlement status, cancellation/refund/dispute status, transaction and receipt metadata, and restore/recovery information. For web purchases, this also includes checkout email, billing/contact information, and payment information entered into hosted checkout.

Purpose: RevenueCat manages subscription offers, Premium access, web billing, transactional messages, password-free purchase redemption/recovery, and the customer billing portal. Stripe processes web payments and related fraud checks, refunds, and disputes. Lychee can access necessary customer and billing records to provide support and meet accounting and legal obligations. Full card numbers and security codes are handled by the payment provider, not received or stored by the Lychee app.

Web checkout email is used for receipts, service and billing messages, subscription management, and recovery. With Apple Pay, the contact email selected in the payment flow may be used. Protect recovery links: opening one may grant subscription access on another device.

Privacy policies: RevenueCat and Stripe. Providers may also process some information for their own legal, security, and fraud-prevention responsibilities, as described in their policies.

3.8 Apple App Store and Google Play Store

Data shared: Purchase, trial, subscription, renewal, cancellation, refund, and billing information as required by the platform.

Purpose: Process in-app purchases and subscriptions.

Important notes:

3.9 Supabase / Hosted Storage

Data shared: Missing ingredient reports, product correction metadata, product import data, and other operational records you submit or that are needed to maintain product coverage.

Purpose: Store product and ingredient improvement data, support product catalog/import workflows, and improve recognition of unknown ingredients.

Important notes:

3.10 Google Analytics for Firebase and Google Ads

Data shared: In iOS versions with the App measurement setting, new installations default to Basic. This uses Google Analytics for Firebase with analytics identifier storage, advertising storage, advertising user data and personalized advertising consent set to denied. The SDK can send limited install and subscription signals for measurement and modeling. These signals can include technical app/device and network information; limited measurement is not a promise that network traffic is anonymous. We do not attach customer, transaction or product identifiers to our Basic subscription events or link a Firebase app-instance identifier to RevenueCat in Basic mode. If you explicitly choose Detailed, Google Analytics receives a pseudonymous app-instance identifier, app/device information, basic usage events and verified subscription events, which can include subscription product, store, currency and amount. These identifiers are not anonymous. Advertising identifier access and advertising use remain subject to Apple’s App Tracking Transparency permission. Older versions with the optional Google checkbox continue to require that choice before Firebase collection; existing explicit refusals remain Off in newer versions.

Purpose: Measure Google Ads attribution and campaign performance, understand basic conversion steps, and optimize advertising for app installs and subscription conversions. Google may use on-device conversion measurement where supported.

Apple aggregate attribution: Apple’s privacy-preserving attribution can report installs and conversion categories to ad networks without identifying you, including when you decline tracking or optional Firebase analytics. Apple controls reporting delays, privacy thresholds and the detail included in these reports. We do not use these aggregate reports to identify individual users.

RevenueCat connection: Only when you allow Detailed analytics (or allowed Google analytics in an older version), we provide the Firebase app-instance identifier to RevenueCat so it can link subscription lifecycle events to your consented app analytics, including purchases, trials, renewals, cancellations, and refunds. This first-party analytics connection does not require access to the advertising identifier and does not override an Apple tracking refusal. Advertising storage and advertising user data remain disabled when tracking is refused, and personalized advertising audiences remain off. This connection does not send checkout email, name, or card details to Google Analytics.

Limits and choice: We do not intentionally send scanned product names, barcodes, photos, ingredients, scan results, health scores, allergies, profile answers, names, email addresses, card details, or precise location to Firebase Analytics. This integration does not enable personalized advertising audiences. In Legal & Privacy > App measurement, choose Basic for limited signals, Detailed to allow additional analytics, or Off to stop Firebase collection, including limited signals. Your choice does not affect scanning or Premium access. Choosing Off resets local Firebase analytics data and requests removal of the RevenueCat identifier link; it does not automatically delete previously received records. Apple’s separate aggregate attribution and necessary billing records are not controlled by this setting. Contact us for data access or deletion requests.

More information: Google Privacy Policy and How Google uses information from apps that use its services.

3.11 Service Providers and Legal Requirements

We may use trusted service providers for hosting, analytics, subscription management, crash reporting, product lookup, product contribution, storage, and customer support. We require providers processing data on our behalf to protect it and use it for the agreed services under applicable data-protection terms. Some providers, including payment platforms, also act independently for their own legal, security, or fraud-prevention purposes as described in their policies.

We may disclose information if required by law, court order, subpoena, or another valid legal request.

4. Data Storage and Retention

4.1 Local Storage

Most day-to-day App data is stored locally on your device, including:

4.2 Cloud and Third-Party Storage

Some data is stored with third-party services or hosted infrastructure when needed:

4.3 Retention

5. Your Choices

5.1 Access and Control

You can review and change your allergen preferences, product preferences, saved products, and scan history inside the App.

5.2 Deletion

5.3 Advertising Choices

You can limit ad tracking:

5.4 Consent and other legal bases

Where EU/EEA data protection law applies, we rely on performance of a contract for requested App features, purchases, subscription access, recovery, and support; legal obligations for required billing/accounting records; and legitimate interests for proportionate security, fraud prevention, service reliability and limited campaign measurement without analytics or advertising identifier storage, subject to your rights. Optional Detailed analytics is based on consent. Where consent is required, including for device access, advertising/tracking or processing of sensitive information, it must be obtained separately; a measurement SDK setting does not itself remove legal obligations. A purchase is not consent to marketing.

You may withdraw consent using the relevant device or service privacy settings, stop using an optional feature, or contact us. You may also object to processing based on legitimate interests. Withdrawal does not affect prior lawful processing. Uninstalling stops use of the App but does not cancel a subscription or automatically delete third-party billing records. Premium removes in-app ads; it does not remove necessary billing processing or automatically disable all analytics/attribution.

6. Children's Privacy

Lychee is intended for users aged 13 and older, or 16 and older in the EU/EEA where required.

We do not knowingly collect personal information from children under 13, or under 16 in the EU/EEA. If you are a parent or guardian and believe your child has provided us with personal information, please contact us.

7. International Data Transfers

Your information may be processed in countries other than your own. These countries may have different data protection laws. Where required, we rely on appropriate safeguards such as contractual protections, standard contractual clauses, or other lawful transfer mechanisms.

8. Regional Privacy Rights

Depending on where you live, you may have rights to access, correct, delete, restrict, or object to certain processing of your personal information, and to withdraw consent where processing is based on consent.

You can contact the controller at the address below. You may also complain to your local data-protection authority; in Poland this is the President of the Personal Data Protection Office (UODO), uodo.gov.pl.

If you are in California or another jurisdiction with similar rights, you may have the right to know what personal information we collect, request deletion, and opt out of certain sharing. We do not sell personal information for money.

9. Cookies and Tracking Technologies

The native App primarily uses device storage and SDK identifiers. Our website, hosted web checkout, recovery pages, and customer billing portal may use cookies or browser storage for operation, payment security, fraud prevention, and session continuity. Third-party mobile SDKs may use similar technologies:

10. Medical and Safety Disclaimer

Lychee is an informational product scanner. It may explain allergens, ingredients, nutrition labels, food processing signals, and cosmetic ingredients, but it is not a substitute for medical advice, allergy diagnosis or management, dietetic advice, cosmetic safety advice, diagnosis, or treatment.

You must always read product labels yourself, verify important food or cosmetic information with the manufacturer, consult qualified professionals when needed, and carry prescribed emergency medication if applicable.

We are not liable for incorrect allergen, ingredient, nutrition, cosmetic, or product database information; product formulation changes; cross-contamination; or adverse health outcomes.

11. Changes to This Policy

We may update this Privacy Policy from time to time. We will update the "Last Updated" date above and may provide in-app notice for material changes.

12. Contact Us

Use the Lychee support form for access, correction, deletion, restriction, objection, consent-withdrawal, or billing requests. To find relevant records we may ask for a purchase email or the app’s support reference, and proportionate proof that the request is yours. Do not send payment card numbers, security codes, or passwords. You can also use our contact page.

Maksym Horoszczak, operating Lychee, Domaniewska 47, 02-672 Warszawa, Poland. Email: allergify@proton.me. Telephone: +39 3934652025.

Summary

What we collect

What we do not collect directly

Most everyday App data stays on your device. You can delete local history and saved products in the App. Uninstalling does not cancel payments, erase provider billing records, or guarantee a new subscription identity.

By using Lychee, you acknowledge that you have read and understood this Privacy Policy.

© 2026 Lychee. All rights reserved.