PlateSight Privacy Policy

Edition 2026-08-25. The app retrieves the effective version from the server: if it changes materially, we will show this notice again and request renewed consent.

Updated September 16, 2026: subscription and trial period.

1. Data Controller

Data Controller: PLATESIGHT LTD.
Contact email for all inquiries under this policy, including account deletion requests: privacy@platesight.tech.

2. What Data We Store

• Account credentials: email address, name and profile picture from your Google Account, Google ID, or your Apple account (user identifier; email address, if not hidden; name, if shared), and unique nickname (if specified).
• Access grounds for premium tier: trial period, subscription, support-granted access — along with effective dates.
• Health data: biological sex, date of birth (from which age is derived), height, body weight and weight history, target weight and desired rate of change, food diary entries (meals, weight, and nutritional composition).
• Health Connect (with your explicit permission): reading step counts, workout durations, and sleep metrics to assess activity levels and recovery. Upon granting permissions, PlateSight also writes logged meals (calories and macronutrients), water intake, and weight measurements to Health Connect, making them accessible to other apps on your device. Retrieved time series are retained on our server: hourly step distributions and nightly sleep stages (sleep/wake times, sleep duration, deep sleep phase, resting heart rate, and heart rate variability). Without storage, comparative trends cannot be calculated over weeks and months. All of this is included in your account data export and deleted together with your account. Permissions can be revoked at any time in Health Connect or inside app settings.
• Apple Health (with your explicit permission): reading step counts, workout durations, sleep metrics, and heart rate (including heart rate variability) to assess activity levels, evaluate recovery, and calibrate your daily nutritional target. Upon granting permissions, PlateSight also writes logged meals (calories and macronutrients), water intake, and body weight to Apple Health, making them accessible to other apps on your device. Retrieved time series are retained on our server: hourly step distributions and nightly sleep stages (sleep/wake times, sleep duration, deep sleep phase, resting heart rate, and heart rate variability). Without storage, comparative trends cannot be calculated over weeks and months. All of this is included in your account data export and deleted together with your account. Permissions can be revoked at any time in iOS Settings (Health → Data Access & Devices) or inside app settings.
• Social visibility settings for friends: granular toggles (streak, consistency, macro compliance, shared meals, typical meal times). By default, all metrics are hidden (disabled).
• Technical records: server access logs — timestamp, HTTP method, request path, response code. Retained for 30 days.

Food photos are not retained: they are sent for multimodal AI recognition and discarded immediately after processing; photos are not saved on the server or in the app. Only the verified dish name, weight, and nutritional values (calories and macronutrients) are stored.

Charts, rolling averages, adaptive expenditure estimates, and goal timelines are not stored: they are dynamically computed whenever you open the analytics screen. Only your daily caloric target and generated recommendation text are saved, both of which are included in your personal data export.

3. Purpose of Processing

• Calculate daily calorie and macronutrient targets based on your body measurements and goal.
• Maintain a food diary and generate dynamic nutritional analytics.
• Recognize meals via photo scans, barcodes, or text descriptions.
• Generate personalized nutritional guidance based on your diary.
• Provide community and peer-habit sharing features with mutual friends under strict reciprocity and only with your explicit consent.
• Provide full access to entitled users and prevent multiple trial activations on the same device (using a salted HMAC hash of device identifier that is completely detached from your account).

4. Legal Grounds (Legal Basis)

Health data is processed on the basis of your explicit consent — Article 9(2)(a) GDPR; other personal data is processed on the basis of consent, Article 6(1)(a) GDPR. Consent is obtained during initial onboarding and stored with the exact policy version reference.

You may revoke consent at any time. Revocation results in account deletion: without health data the service cannot function, and we have no legal basis to retain it without your consent.

5. Third-Party Disclosures & Processors

Google LLC as data processor: Google Sign-In for authentication; Gemini API for meal recognition and nutrition guidance. Data is transferred to the United States. Legal transfer mechanism: Standard Contractual Clauses (SCC) pursuant to Article 46(2)(c) GDPR.

Apple Inc.: Sign in with Apple for authentication; App Store for subscription billing. Apple receives only what is necessary for login and purchase processing; food diary and health data are not shared with Apple.

Mutual friends within the app: no personal data is shared by default. Only upon your explicit opt-in, and strictly provided that your friend has enabled reciprocal sharing, the friend may see: current streak, 4-week logging consistency percentage, qualitative goal compliance ("on target / above / below" without disclosing exact calories, weight, or numbers), shared meal names over 7 days (without weight or calories), and approximate meal times. When sharing a specific dish with a friend, only the name, weight, and macros of that single item are sent without food diary context.

We do not sell, rent, or transfer personal data to any other third parties. Data retrieved from or written to Health Connect or Apple Health is never shared with third parties, advertising platforms, or data brokers, is not used for advertising, and is not stored in iCloud, in compliance with Google Health Connect Permissions policy and App Store Review Guideline 5.1.3.

6. Retention Periods

• For the active duration of your account.
• Upon account deletion: erased immediately from active databases; purged from rotating encrypted backups within 35 days.
• Device verification hash: indefinite (not linked to any user identity or account).
• Server access logs: 30 days.

7. Automated Decision-Making

Daily calorie targets are computed using the Mifflin-St Jeor formula based on your metrics; recommendations are generated by an AI language model from your diary. The service does not make automated decisions that produce legal or similarly significant effects. Recommendations do not constitute medical advice and are not a substitute for professional healthcare guidance.

8. Your Rights

• Access & Data Portability: Profile → "Download My Data" provides a full, machine-readable export of all stored data.
• Rectification: Profile → edit measurements, goals, and diary entries.
• Erasure (Deletion): Profile → "Delete Account". Immediate and permanent. If you cannot access the app — visit the account deletion page.
• Restriction & Objection: by email to the address in Section 1 (privacy@platesight.tech).
• Withdrawal of Consent: see Section 4.
• Lodge a Complaint: you have the right to lodge a complaint with your local data protection supervisory authority.

Response timeline for written requests: 30 calendar days.

9. Age Requirements

The service is not intended for individuals under 16 years of age, and we do not knowingly create accounts for them.

10. Changes to this Policy

Material changes to this policy will result in an incremented version number, and you will be asked for renewed consent upon your next app launch. Non-material cosmetic updates do not trigger renewed consent.

11. Operator Access and Technical Support

To assist with customer support inquiries and resolve technical incidents, authorized support personnel may view your account card (registration date, onboarding status, record count) and food diary strictly under the following safeguards:

• Strict Purpose Limitation: access is permitted only upon an explicit user support request or active system malfunction investigation.
• Mandatory Audit Logging: every access event is recorded in an immutable audit log with operator ID, reason, timestamp, and IP address.
• No Data Modification: support personnel have no technical ability to edit or forge food diary entries (database permissions are strictly read-only for support staff).