Privacy Policy

This Privacy Policy explains how Fastsnap collects, uses, shares, and protects personal data when you use our website and mobile apps (the “Service”). The Service is run by Henry Pui Yip Chan, an individual (natural person) in Hong Kong — not through a registered company, partnership, or sole proprietorship. “Fastsnap” is the name of the Service only; it is not a separate legal entity. In this policy, “we”, “us”, and “our” mean Henry Pui Yip Chan in that capacity. It should be read together with our Terms of Service.

1. Who is responsible

The data controller is Henry Pui Yip Chan, acting in his personal capacity as an individual based in Hong Kong Special Administrative Region (“Hong Kong”). He provides the Fastsnap Service in his own name, not as a company or registered business. For privacy questions or requests, contact us at support@fastsnap.ai.

2. What we collect

Depending on how you use the Service, we may process:

• Meal photos — images you upload for analysis. Photo metadata (such as EXIF and GPS location tags) is removed on your device before upload (web: re-encoded via canvas; mobile: stripped on resize). Each photo is sent to our servers and to AI providers to generate a result. When a scan is saved to your account history, we also store the photo in private cloud storage so it can appear in History; it stays there until you delete your account. We do not store the raw image bytes inside the scan database row itself. A temporary preview may remain in your browser until you close the tab or clear storage.
• Analysis results — meal name, scores, verdict, impact bullets, and (for Premium users) macro estimates, healthier swaps, and personalised tips. These may be saved to your account history when you are signed in.
• Profile and health-related information — goal mode (lose fat / low-carb protocol, or build muscle), optional daily carb budget and strict low-carb setting, and optional fields such as age, sex, weight, and height if you provide them. Together with your meal analysis (metabolic risk scores, insulin spike estimates, protein adequacy, and related outputs) this is health-related information — see section 3.
• Account data — a user identifier from our authentication service. You can scan without an email using an anonymous session. If you choose email sign-in, we store your email address for authentication and account recovery.
• Consent records — when you give explicit consent (section 3), we record that you consented, the purpose, the version of this policy, and the time, as our audit trail.
• Subscription data — whether you have Premium, plan status, and payment-processor references. Payment card details are handled by our payment provider; we do not store full card numbers.
• Usage and security data — scan quota ledger entries (tier, timestamps), and a one-way hashed (salted SHA-256) form of your IP address used to enforce rolling scan limits and to rate-limit abuse. We do not store your raw IP address in that ledger. These records are not visible to other users.
• Product analytics — event names such as scan_completed or paywall_viewed, trust signals (not_right_clicked, non_success_short_dwell, etc.), an anonymous session identifier, optional user id when signed in, and small property bags (for example UTM source/medium from a share link). Used to measure funnels and improve the product — not sold.
• Technical data — browser or device type, approximate region from our CDN for consent rules, and cookies or similar tokens needed for authentication sessions.

3. Health-related and special-category data

The Service analyses meals and produces metabolic estimates — fat-storage risk, insulin spike, satiety, and fasting impact — and you may add details such as weight, height, age, and a health goal. This information relates to your health and may be treated as a special category of data under the UK GDPR and EU GDPR (Article 9).

Where the law requires it (for example in the European Economic Area, the United Kingdom, and EFTA countries), we ask for your explicit consent before we process your meal photos and health-related information to generate an analysis. We present this request in the app before your first scan in those cases, and again if this policy changes materially. We decide whether that prompt is needed using your approximate region (for example from connection signals on the web app, or device time zone as a fallback on mobile). In other regions we may rely on other lawful bases described in section 6. You are not required to provide the optional profile fields, and you may choose not to use the Service.

You can withdraw consent at any time by deleting your account (section 13), which stops further processing and erases the data we hold. Withdrawal does not affect processing already carried out before withdrawal.

4. How we use your data

We use personal data to:

• Analyse meal photos and return metabolic estimates.
• Save scan history and sync your profile across devices when you sign in.
• Provide Premium features and verify subscription status.
• Enforce free-tier limits and protect the Service from abuse.
• Process payments and manage subscriptions.
• Improve reliability and security of the Service.
• Respond to support requests and comply with legal obligations.

We do not sell your personal data. We send meal photos and related context to AI providers under our agreements to run analysis; we do not use your content to train our own models. How those providers handle API data is governed by their own terms and privacy notices.

5. Hong Kong (PDPO)

If you are in Hong Kong, the Personal Data (Privacy) Ordinance (Cap. 486) applies. We collect data for purposes stated in this policy, keep it no longer than necessary, and take practicable steps to protect it. You may request access to and correction of your personal data, and may inquire how we use it, by contacting us at the email below. You may complain to the Office of the Privacy Commissioner for Personal Data, Hong Kong (PCPD).

6. Legal bases (EEA, UK, and similar regions)

Where applicable law requires a legal basis, we rely on:

• Explicit consent — for processing your meal photos and health-related information to generate an analysis (special-category data, section 3).
• Contract — to provide the Service you request, including Premium features and account functionality.
• Legitimate interests — to secure the Service, prevent fraud, enforce quotas, and improve the product, balanced against your rights.
• Legal obligation — where we must retain or disclose data by law.

7. Service providers

We use companies that help us run the Service. They process personal data only on our instructions and for the purposes in this policy. Categories include:

• AI providers — meal photos and related context for recognition and coaching text (inference only, not used to train our models).
• Infrastructure providers — authentication, databases, APIs, and private meal-photo storage.
• Payment and subscription providers — web checkout and verification of app-store subscriptions; card details stay with the payment processor.
• CDN and security providers — delivery of the app and API; may see connection metadata at the edge before we apply our own limits.
• Reference data services — for some packaged foods we may send a meal name only (not your photo) to a public nutrition database to improve macro estimates.

Subscriptions bought through the Apple App Store or Google Play are billed by those platforms; their policies apply. You can email us for the current list of subprocessors we use in each category.

8. International transfers

Our providers may process data in the United States and other countries that may not have the same data-protection laws as your home country. Where required, we use appropriate safeguards (such as standard contractual clauses) for transfers from the EEA, UK, or Switzerland.

9. Storage on your device

The web app stores your goal, profile fields, a consent flag, an analytics session id, optional UTM attribution for the current browser session, and the latest scan result in localStorage and sessionStorage so pages load quickly and share cards can be generated. You can clear this data via your browser settings. Native apps may store similar data on your device (for example AsyncStorage).

10. Retention

• Scan history and profile — kept while your account is active. You may export or delete them at any time (see section 13).
• Usage ledger entries — the hashed-IP / scan-count records used to enforce quotas are automatically deleted on a rolling schedule (currently within about 7 days, where that job is enabled in our infrastructure).
• Consent records — kept as our audit trail of your consent for as long as your account exists, and erased when your account is deleted.
• Subscription records — kept as long as required for billing, tax, and fraud prevention.
• Meal photos — kept in private cloud storage while your account exists and the scan row remains; removed when you delete your account (best-effort purge of your storage folder).
• Product analytics events — retained for product measurement and funnel reporting; we may delete older rows periodically where practicable.

11. Security

We use technical and organisational measures appropriate to the risk, including HTTPS, access controls, server-side premium gating, hashing of IP addresses, removal of photo metadata on-device, and limiting direct client access to sensitive tables. No method of transmission or storage is 100% secure; we cannot guarantee absolute security.

12. Automated processing and AI

Analysis is produced partly by automated systems (AI and scoring rules). Outputs are estimates, not medical advice and not decisions with legal or similarly significant effects. You can correct macro values in the app and recalculate scores where that feature is available.

13. Your rights

Depending on where you live, you may have the right to:

• Access a copy of your personal data.
• Correct inaccurate data.
• Delete your data or account.
• Restrict or object to certain processing.
• Data portability.
• Withdraw consent where processing is consent-based.
• Lodge a complaint with your local data protection authority (for example the Office of the Privacy Commissioner for Personal Data in Hong Kong, or your EU/UK supervisory authority where applicable).

In the web or mobile app, open your profile (⚙ Personalize on mobile) and use Download my data for a portable JSON export (profile, scan history and analysis fields, subscription summary, and consent records — not a zip of meal photos), or Delete my account to permanently erase your account, scan history, stored meal photos, profile, consent records, and usage data (any active web subscription is cancelled where applicable).

For any request, email support@fastsnap.ai. We may need to verify your identity. We aim to respond within 30 days where GDPR or similar laws apply, and within a reasonable time under Hong Kong law.

California residents. We do not sell or share personal information. You may request disclosure of categories collected and deletion, subject to legal exceptions.

14. Children

The Service is not directed at anyone under 18. We do not knowingly collect personal data from children. If you believe a child has provided data, contact us and we will delete it.

15. Changes

We may update this policy from time to time. The “last updated” date and version at the top will change when we do. For material changes affecting how we process health-related data, we will ask for your consent again before continuing.

16. Contact

Data controller: Henry Pui Yip Chan (individual), Hong Kong. Product name: Fastsnap. Privacy questions or requests: support@fastsnap.ai.