PlateWizPrivacy Policy
PlateWiz (“PlateWiz”, “we”, “us”) provides a calorie and nutrition tracking app (the “Service”). This policy explains what information the app collects, why, who receives it, and what controls you have. It should be read with our Terms of Service.
1. Information we collect
Account information
You sign in with Apple or Google through our authentication provider, Clerk. We receive and store a Clerk user ID and the email address on your account.
Body and goal information (health-related)
During onboarding and in your profile you give us your sex, birthdate, height, weight, activity level, goal, target weight and preferred pace. We use this to calculate your daily calorie and macro targets, and we store your targets (including any custom targets you set) over time. This is information about your health and body; please enter only what you are comfortable sharing.
Logs you create
- Meals: meal photos, text descriptions, manually entered values, barcodes you scan, the meal name and items, portion sizes, calories and nutrients, an AI health score, tip and confidence value, any clarifying question the AI asked about the meal, whether you marked it a favourite, and when and on what date you ate it.
- Corrections: when you use “Fix with AI” or answer the AI’s question about a meal, we keep what you wrote together with the estimate before and after the correction. We use these to measure and improve the accuracy of meal estimates.
- Weight and water: body-weight entries and daily water intake.
- AI weekly summaries: the recap text we generate for you.
- Usage counts: how many AI meal logs, coach messages and diet plans you used each day, to apply the daily limits.
Coach and diet plans
Messages you send to the in-app nutrition coach, and the food preferences you choose for a diet plan, are sent to our servers to generate a reply or plan. We don’t store coach conversations on our servers; the conversation stays in the app until you close it. Generated diet plans aren’t stored on our servers either, unless you log a meal from one.
Steps and activity (Apple Health / Health Connect)
If you connect Apple Health (iPhone) or Health Connect (Android), the app reads today’s step count and active calories to show them in the app and, if you turn it on, on your Lock Screen or in a notification. This data is read on your device and is not sent to our servers. The app does not write anything to Apple Health or Health Connect.
Settings and device information
Your unit preferences, notification settings and reminder times, your time zone (so dates and reminders match your local day), and, if you allow notifications, your Expo push token. Technical request details such as IP address and device or app information are processed by our hosting and service providers in the course of delivering the Service and in diagnostics (see Diagnostics).
Stored on your device
Your sign-in session token and basic account details are kept in your device’s secure storage by Clerk’s SDK. So that the app opens without a connection, it keeps a copy of the data it last showed you (such as today’s meals, your targets and profile) on your device for up to 24 hours; this copy is deleted when you sign out. The app also keeps small preferences on your device, such as appearance settings and which celebrations you have already seen. These stay on your device.
What we do not collect
The app does not request your location, contacts or microphone, and does not include advertising or marketing-analytics SDKs.
2. How we use it
- To provide the Service: analyse meals, calculate and show your targets, statistics, streaks and achievements, and sync your data to your account.
- To generate AI content for you, such as meal estimates and corrections, coach replies, diet plans, your targets and weekly summaries.
- To apply daily limits on AI features, so the Service stays available and affordable for everyone.
- To measure and improve the accuracy of meal estimates, using the corrections you make.
- To send reminders and weekly-summary notifications you have enabled.
- To keep the Service secure, fix bugs, monitor performance and prevent abuse.
- To respond to your requests and comply with the law.
We do not use your information for advertising, and we do not sell it or share it for cross-context behavioural advertising.
3. AI processing
Our servers send the following to Google’s Gemini API:
- Meal analysis: your photo (resized) or text description. When you correct a meal, also the previous estimate and your correction.
- Targets: your sex, age (derived from your birthdate), height, weight, activity level, goal and pace. For users under 18 we calculate targets with a standard formula instead and send nothing.
- Coach: your messages, plus your targets, body details and goal and the meals you logged today, so replies fit your plan.
- Diet plans: your targets, goal, activity level and the food preferences you chose.
- Weekly summary: your daily calorie and nutrient totals, calorie targets and weight entries for that week.
We do not send your name or email address to the AI provider. Google processes this data under its own terms and privacy policy. Meal estimates are stored with your meal, together with the model name and the raw response. AI estimates are approximate and are not medical advice.
4. Who receives your information
We use these service providers (processors) to run the Service. Each receives only what is needed for its role:
| Provider | Purpose | Data involved |
|---|---|---|
| Expo (EAS Hosting) | Hosting the app’s server (API) | All requests between the app and our servers |
| Clerk | Sign-in and account management; sign-in with Apple/Google | Account identifiers, email, session data |
| Neon (Postgres) | Database hosting | All account data and logs listed above |
| ImageKit | Storing and resizing meal photos (as private files) | Meal photos |
| Google (Gemini API) | AI meal analysis and corrections, coach, diet plans, targets and summaries | Meal photos/text, corrections, coach messages, body details, targets, weekly totals |
| Trigger.dev | Background jobs (meal analysis, plan generation, reminders, summaries, account deletion) | Job inputs such as meal and user IDs, correction text and the onboarding answers, plus run logs |
| Expo | Delivering push notifications | Push token, notification text |
| Sentry | Error, performance and diagnostic monitoring | See Diagnostics |
| Open Food Facts | Barcode product lookup | The barcode number, sent from our server |
| Apple / Google | Sign-in and app distribution | Per their own terms |
We may also disclose information if required by law or to protect rights and safety, and to a successor in a merger or sale of the business.
About photo links. Meal photos are stored with ImageKit as private files. The app shows them through signed links that our server creates for your account and that stop working within two days, so a copied link can’t be used to view your photo for long. Photos uploaded before October 16, 2026 were stored with links that didn’t expire; we are moving them to private storage. Please still avoid photographing sensitive documents or people who haven’t agreed.
5. Diagnostics and monitoring
The app uses Sentry to collect crash reports, error and performance traces, profiling data and app logs (for example, that a meal upload failed or that notification permission was declined). Sentry’s “send default PII” option is switched off, and performance traces are collected for a sample of sessions (about 1 in 5). When an error happens, the app may record a session replay (a reconstruction of the screens shortly before the error). Replays are not recorded for normal sessions, and in every replay all text, images and graphics are masked, so they show the layout of screens but not your meal photos, meal names, or nutrition and body details. Diagnostics are used only to find and fix problems.
6. Device permissions
- Camera: to photograph meals and scan barcodes. Photos you take are uploaded for analysis when you submit a meal.
- Photo library: only the images you choose to analyse.
- Notifications: to deliver reminders and summaries, and on Android the optional step-count notification; optional.
- Apple Health / Health Connect: read-only access to steps and active calories, only if you connect it. See Steps and activity.
- Network state (Android): to show when you’re offline and refresh your data when the connection returns.
You can change these at any time in your device settings. The app still works for manual and text logging without the camera.
7. Retention
We keep your account data and logs until you delete them or your account. Deleting a meal also deletes its photo. If you delete your account, we delete your data as described in Your choices. Copies may persist for a limited time in provider logs, backups and monitoring data (for example Sentry events and Trigger.dev run logs) according to those providers’ retention schedules: generally up to 30 days. Invalid push tokens are cleared automatically.
8. Your choices and controls
- Edit: update your height, birthdate, sex, targets, units and weight in the app, and edit or delete individual meals (deleting a meal removes its photo).
- Export: in the Profile screen you can export your meals, weight entries and water entries as a CSV file. The export does not include your profile details or photos.
- Delete your account: “Delete your account” in the Profile screen permanently deletes your sign-in account at Clerk straight away, then all your meal photos from our image storage and your profile, targets, meals, corrections, weight and water logs, summaries and usage records from our database. The photo and data clean-up runs in the background and retries until it completes, normally within minutes. This can’t be undone.
- Notifications: turn meal reminders and streak reminders off, or change their times, in the app, or disable notifications in your device settings.
- Permissions: revoke camera, photo, notification or Apple Health / Health Connect access in device settings.
9. Security
Requests from the app to our servers are authenticated with a signed Clerk session token that we verify on every request, and each request only accesses the signed-in user’s data. Our providers use industry-standard measures to protect data they host. Meal photos are private files shown through short-lived signed links, as explained in Who receives your information. No system is perfectly secure, and we cannot guarantee absolute security. If you believe your account is at risk, contact us.
10. International processing
Our service providers may process and store your information in the United States and other countries where they operate, which may have different data-protection laws than where you live. Our database is hosted with Neon in North America (south-east region).
11. Age requirement
PlateWiz is for people aged 16 and over. We do not knowingly collect information from anyone under 16. If you believe a child under 16 has an account, contact us and we will delete it.
12. Privacy rights
Depending on where you live (for example the EU/UK or certain US states), you may have rights to access, correct, delete, port or restrict the use of your personal information, to object to processing, and to withdraw consent, and to complain to your local data-protection authority. Most of these you can exercise directly in the app (see Your choices); for anything else, contact us and we will respond as required by law. We use your information to provide the Service you ask for, under our legitimate interests in running and securing it, and with your consent where required (for example for notifications and device permissions). Because we process health-related information, we rely on your explicit consent, which you give by entering it, and you can withdraw it by deleting the data or your account.
13. Changes to this policy
We may update this policy. If changes are material we will notify you in the app or by email before they take effect where practicable, and update the date above.
14. Contact
Questions or privacy requests: support@platewiz.app