Success message
Error message
Effective date: September 25, 2026
Last updated: October 5, 2026
This policy covers PlateWise only (Google Play package com.rork.platewise), published by Ocean Digital Group LLC. It does not cover other Ocean Digital Group apps.
Contact: Ocean Digital Group LLC, 349 Valley St, Willimantic, CT 06226-2119, United States. Email: support@oceandigitalgroup.com
PlateWise estimates the calories and macronutrients (carbohydrates, protein, fat and fiber) in a meal from a photo. You can save results to a meal diary on your device, set daily goals, and view carbs, optionally as net carbs.
PlateWise has no user accounts. You get a limited number of free meal analyses (currently 3). After that, meal scanning requires a PlateWise subscription sold through Google Play. Subscriptions are subject to a fair-use limit (currently 60 analyses per day) to prevent abuse.
How a meal scan works:
You take a photo with the camera or pick one from your gallery.
On your device, PlateWise shrinks the photo and re-saves it as a new JPEG. This removes embedded photo metadata such as GPS location and camera details.
The photo is sent over HTTPS to the PlateWise backend, together with a random install ID and whether you have a subscription. The backend checks your free or fair-use limit and forwards the photo to an AI service (see "Who receives data"). Estimated food items and nutrition values are sent back to the app.
Nothing is saved to your diary unless you choose to log the meal.
PlateWise is for general information only. Calorie, carb and other nutrition values are AI estimates and can be wrong. PlateWise is not a medical device and does not give medical advice, diagnosis or treatment. It does not give insulin or other medication dosing advice. Do not use PlateWise to make insulin or medication decisions. If you have diabetes or any other medical condition, talk to your doctor or a qualified health professional before changing your diet or treatment.
Meal photos:each photo you scan is sent to the PlateWise backend for AI analysis (see "Who receives data"). The backend does not store the photo; it passes it to the AI service and returns the result. Your device's IP address is visible to these services as part of any normal internet connection. A copy of the photo is kept in the app's private cache on your device and shown with meals you log.
Install ID: when you first scan a meal, PlateWise creates a random ID for this installation. It is sent with each scan so the backend can count free analyses and apply rate and fair-use limits. It is not linked to your name, email or Google account. The backend keeps a usage count for each install ID.
Meal diary and goals:logged meals (meal name, food items, calories, carbs, protein, fat, fiber, the photo's location in the app cache, and timestamps), your daily calorie and macro goals, and a scan counter. These are storedonly on your device and are not sent to the PlateWise backend or to us.
First name (optional): if you enter it during onboarding, it is stored on your device and used only to greet you in the app.
Device backup:if Android backup is turned on for your device, Android may include PlateWise's app settings (diary, goals, first name, scan counter and install ID) in your Google account backup and in device-to-device transfers, like other app data. Cached meal photos are not included. You control this in your device's backup settings.
Subscription information: RevenueCat, our subscription service, receives an anonymous app user ID that its SDK generates, device and app information (such as device type, OS version and app version), your IP address, Google Play purchase tokens, and your purchase and subscription history. The app contacts RevenueCat each time it starts, even if you never buy anything, so it can check whether you have an active subscription.
Payments: Google Play handles all payments. We do not receive your payment card number.
Diagnostics:PlateWise does not include any analytics or crash-reporting SDK.
Camera: used only to take meal photos for scanning. Camera access is optional; you can pick a photo from your gallery instead.
Gallery: PlateWise uses the Android Photo Picker. You pick one photo at a time, and the app does not need permission to read your photo library.
Internet, network state and Google Play billing:used to send photos for analysis, check your subscription and process purchases.
PlateWise does not request location, contacts, microphone, notifications, storage/media library, health data (Health Connect) or advertising ID permissions.
Require an account, sell your information, share your information for advertising, show ads, include any advertising or analytics SDK, collect your advertising ID, or collect your location.
PlateWise backend (hosted by Rork) — receives your meal photo, the install ID and your subscription status, applies usage limits, and keeps a usage count per install ID. It does not store photos.
Rork (AI toolkit) — the backend sends your meal photo and a fixed instruction prompt to Rork's AI toolkit at toolkit.rork.com, which forwards them throughVercel (AI Gateway) to an AI model.
Google (Gemini models) and OpenAI (GPT models) — process the photo to produce the nutrition estimate. Google's model is used first; OpenAI's is a fallback.
Rork, Vercel, Google and OpenAI act as service providers for this feature. We do not control how long they keep data. Their processing is governed by their own terms and privacy policies. Do not scan photos that show people or other personal information.
RevenueCat — anonymous app user ID, device and app information, and purchase and subscription history, used to manage subscriptions.
Google Play — payment processing and subscription management for purchases. Google's billing library may also send Google technical data about the purchase process.
Rork's content network (r2-pub.rork.com) — the app downloads onboarding and sample images from it. This is a standard web request that shows your IP address; no personal data is uploaded.
We do not sell or rent user data.
When you use PlateWise Pro features (such as AI meal analysis beyond the free allowance), the app sends your RevenueCat app user ID to the PlateWise backend so we can confirm that your Pro subscription is active. We use this identifier only to verify entitlement status and enforce scan limits; we do not sell it or use it for advertising.
On your device: deleting a meal removes it from your diary. Clearing PlateWise's storage in Android Settings, or uninstalling the app, removes all local data (diary, goals, first name and cached photos). Deleting a meal may leave its cached photo in the app's private storage until you clear the app's storage or uninstall.
Device backup: a copy may remain in your Google account backup until Android replaces or deletes it. You can manage or delete backups in your device or Google account settings.
Backend: the PlateWise backend does not store meal photos. Usage counts linked to an install ID are kept only to enforce limits. Email us if you want the count for your install ID deleted.
AI providers: we do not keep your meal photos on any server of ours. Any copies kept by Rork, Vercel, Google or OpenAI are handled under their policies. Email us if you need help with a request to them.
Subscription records: to ask us to delete the RevenueCat record linked to your purchases, email us at support@oceandigitalgroup.com with your purchase date and your Google Play order number (it starts with "GPA."), and we'll locate your record. Deleting this record does not cancel your subscription. Cancel in Google Play (Payments & subscriptions → Subscriptions). Google keeps its own purchase records under Google's privacy policy.
Email support@oceandigitalgroup.com for deletion requests about anything we hold.
Data sent off the device uses HTTPS. Data on your device is stored in PlateWise's private app storage. No method of transmission or storage is perfectly secure.
PlateWise is not directed at children under 13. We do not knowingly collect personal information from children under 13.
We may update this policy. The “Last updated” date will change. Continued use after a change means you accept the updated policy.