Privacy Policy

Controller

The controller responsible for MealSync is Magdalena Bachinger, Fuerstallergasse 7, 5020 Salzburg, Austria. For privacy requests or questions, contact info@getmealsync.app.

Data MealSync may process

• Account details such as email address and authentication identifiers.
• Meal inputs such as photos, audio recordings, transcripts, menus, receipts, and typed notes.
• Nutrition estimates, user edits, meal history, sync status, and deletion status.
• Payment and subscription status from the payment provider.
• Basic technical data needed for security, abuse prevention, debugging, and service operation.

How data is used

MealSync uses data to estimate nutrition, show reviewable results, save user-approved meal history, support Google Health / Health Connect workflows where available, manage subscriptions, prevent abuse, and improve reliability. MealSync does not sell health or meal data or use it for advertising.

Health data and consent

Meal and nutrition data can be sensitive. MealSync requests explicit user consent before processing meal inputs for nutrition estimation and before any connection to or write into Health Connect. Users can review and edit estimates before any health-data write.

Sharing and processors

MealSync uses service providers only where needed to operate the product. Current planned providers are Cloudflare for hosting, D1 database, R2 object storage, and security; OpenAI for nutrition estimation; Google OAuth for passwordless authentication; and Polar for subscription billing, invoices, and the customer portal. MealSync does not sell meal or health-adjacent data.

International transfers

Some providers may process data outside Austria or the European Economic Area. Where this happens, MealSync should rely on appropriate safeguards such as EU Standard Contractual Clauses, adequacy decisions, or another valid transfer mechanism required by data protection law.

Retention

Demo estimates are not intentionally stored as meal history, but technical abuse-prevention records such as hashed demo rate-limit entries may be retained for operational protection. Paid account records, meal history, source metadata, subscription status, and privacy request audit records are kept while the account is active and as long as needed for product operation, legal obligations, security, and dispute handling. Account deletion anonymizes the MealSync profile and removes saved meals from normal history; billing records remain with Polar according to Polar and legal retention requirements.

Cookies, analytics, and tracking

MealSync does not currently use advertising cookies or behavioral advertising analytics. Authentication, security, payment, and platform providers may use strictly necessary cookies or similar technologies to keep the service working. If product analytics are added later, health-input content should not be sent to analytics tools and this policy should be updated first.

Security

MealSync uses access-controlled accounts, Cloudflare platform protections, signed webhook verification, rate limiting for the free demo, object-storage checks for uploads, and global security/privacy headers. No internet service can be perfectly secure, so users should avoid uploading content they do not want processed for meal estimation.

User controls

Users can delete MealSync meal history, cancel subscriptions through the billing portal, delete the MealSync account, request data export, or download an in-app JSON export. If Health Connect connection is enabled, users can also manage Health Connect permissions on their Android device. Users can contact the support email to exercise GDPR rights such as access, correction, deletion, restriction, objection, portability, or complaint rights with a supervisory authority.

Not medical advice

MealSync provides nutrition estimates for self-tracking; it is not medical advice. It does not diagnose, treat, or provide medical advice. Users should speak with a qualified professional for medical or dietetic decisions.