Introduction
RepPlate is an iOS app published by FroggyHub. This policy describes how information is handled when you use RepPlate. It covers RepPlate specifically — other FroggyHub apps have their own policies describing their own behaviour.
RepPlate is a fitness and nutrition tracking tool. It is not a medical device, a clinical nutrition service, a replacement for a dietitian, or a treatment product for disordered eating. Nutrition results are estimates, and you can correct them.
Information we process
Anonymous identifiers
RepPlate does not ask you to create an account before it is useful. When you first use the app you are represented by an internal anonymous user identifier and an authentication token for your session. On supported devices that token is held in the operating system’s secure storage.
RepPlate does not ask for your name or email address. If optional account features such as Sign in with Apple are added later, this policy will be updated before they ship.
Nutrition preferences and goals
If you set them, RepPlate stores your optional daily calorie target, your optional daily protein target, and the fitness or nutrition goal you selected.
Meal and nutrition data
When you save a meal, RepPlate stores the structured record of it so your history and daily totals work. For each meal item this can include:
- the food description and the canonical search term derived from it
- the FoodData Central identifier, description, and data type used for the match
- calories, protein, carbohydrates, and fat per 100 g
- the originally estimated quantity and any quantity you corrected
- the resulting nutrition totals for the meal
- recognition confidence and nutrition-match confidence
- which AI provider and model produced the recognition
- the timestamp of the meal
Food photographs
When you photograph a meal or pick an existing photo from your library, that image is sent for analysis. See Food images and AI processing below for what happens to it.
App and subscription information
RepPlate processes the identifiers and entitlement information needed to know whether your subscription is active. Payment card details are handled by Apple and are never sent to or stored by RepPlate.
Technical and usage information
RepPlate processes operational information such as request and error records, timing data, and app and device characteristics needed to run the service, diagnose faults, and prevent abuse.
Support correspondence
If you email us, we receive your email address and whatever you choose to put in the message, and we keep the exchange so we can answer you and follow it up.
A deletion request is the one case where we actively ask for more. Because we cannot yet identify you from an in-app ID, we ask for roughly when you started using RepPlate, the Apple Account any subscription was purchased with, and details of recent saved meals. You choose what to send; we use it only to locate your records and to answer the request.
How we use information
We use the information above to:
- analyse the meals you photograph and identify the foods in them
- calculate calories and macronutrients for those foods
- save your meals and show your history and daily totals
- apply the calorie and protein targets you set
- determine whether your subscription entitles you to unlimited scanning
- improve the accuracy and reliability of food recognition and nutrition matching
- diagnose technical problems and keep the service running
- detect and prevent abuse of the service
Food images and AI processing
To analyse a meal, RepPlate transmits your food photo — or information derived from it — to the AI processing infrastructure that performs the recognition. RepPlate currently reaches a vision-capable model, Google Gemini, through OpenRouter on Replit-managed infrastructure.
The AI step is used to:
- identify the foods visible in the photo
- produce a canonical search term for each food
- identify the relevant preparation style
- estimate approximate portion size
- return a confidence score for the recognition
The AI model is not the authoritative source of your calorie or macronutrient numbers. Those come from the nutrition data described in the next section, calculated deterministically from the food match and the portion.
RepPlate is built so that your original food photograph is not retained as part of your permanent meal history by default. A saved meal keeps the structured nutrition record rather than the picture. We cannot describe this as an absolute guarantee: transmitting an image over a network and having it analysed necessarily involves it passing through, and being temporarily processed by, the infrastructure and providers required to perform the analysis you asked for.
We do not make claims here about how the AI provider retains or uses data on its own systems. Those behaviours are governed by that provider’s own terms and by the configuration in place, and we would rather point you at the provider than summarise it inaccurately.
Nutrition data
RepPlate uses USDA FoodData Central as its nutrition reference. Once a food has been recognised and normalised into a canonical description, RepPlate looks it up in its own known-food cache and, where needed, queries FoodData Central. The nutrient values are then applied deterministically to the estimated or corrected portion.
When you save a meal, RepPlate stores a snapshot of the nutrition values used, so your history stays stable even if the underlying reference data changes later.
Payments and subscriptions
RepPlate offers a limited free experience, and a Pro subscription for unlimited scanning. Purchases are made through the App Store, and Apple processes the payment. Neither RepPlate nor FroggyHub receives or stores your full payment card details.
RepPlate uses RevenueCat to manage subscription products and entitlement status. RevenueCat may process the information needed to determine whether your subscription is active, associate and restore App Store purchases, provide localised product information, and support subscription management.
Analytics
RepPlate records product events so we can tell whether the app works — for example: app opened, onboarding completed, scan started, scan completed, scan failed, meal saved, paywall viewed, and subscription purchased.
These events can carry non-sensitive operational properties such as processing time, the number of items detected, which recognition model ran, the calorie and protein totals of a meal, and where in the app a paywall was shown.
Raw food-photo image data and authentication tokens are not sent to analytics.
This policy does not name a third-party analytics provider. If RepPlate begins sending analytics events to one, we will name it in the list of service providers below and update this policy before that happens.
Service providers
RepPlate relies on the following third parties to operate. Each processes only what it needs for its role:
- Apple
- App distribution and App Store payment processing for subscriptions.
- RevenueCat
- Subscription product management, entitlement status, and purchase restoration.
- OpenRouter, on Replit-managed infrastructure
- Routes meal-analysis requests to the AI model.
- Google Gemini
- The vision model that identifies foods and estimates portions from your meal photo.
- USDA FoodData Central
- Public nutrition reference data used to calculate calories and macronutrients.
Sharing information with a service provider so it can perform one of these functions for RepPlate is not the same thing as selling personal information. These providers act on our instructions for the purposes described here.
Data retention
- Original food photographs
- Designed to be discarded after processing rather than kept. They are not retained as part of your permanent meal history by default.
- Saved meals and nutrition records
- Kept while you use RepPlate, because they are your meal history and daily totals. They are removed when you ask us to delete your data. Because RepPlate identifies you by an anonymous identifier rather than an account, we first need enough detail to be confident which records are yours — see Your choices and data deletion.
- Support correspondence
- Kept while we handle your request and for a reasonable period afterwards, so we have a record of what was asked and what we did — including for a deletion request, where the record of having actioned it is the evidence that we did.
- Technical and operational records
- Kept for as long as reasonably necessary for security, fraud prevention, debugging, service reliability, and any legal obligations that apply — and no longer.
Data security
We take reasonable technical and organisational measures to protect the information RepPlate handles. Traffic between the app and our service is encrypted in transit, and on supported devices your session token is held in the operating system’s secure storage rather than in ordinary app storage.
No service can promise perfect security, and we will not claim otherwise. If we become aware of a breach affecting your information, we will act on it and notify you where we are required to.
Your choices and data deletion
You control what you put into RepPlate. You can edit the quantity of any detected food, delete foods that were identified incorrectly, and decline to save a meal at all. Camera and photo library access are granted through iOS and can be changed at any time in the iOS Settings app.
To request deletion of your RepPlate data, email hello@froggyhub.com and tell us you want your data deleted.
If deletion becomes available directly inside the app, this section will be updated to say so.
Children's privacy
RepPlate is a strength-training nutrition tool built for a general adult audience. It is not directed at young children, and we do not knowingly seek or collect personal information from them.
If you believe a child has provided information to RepPlate, contact us at hello@froggyhub.com and we will delete it. Because RepPlate identifies you by an anonymous identifier rather than an account, we first need enough detail to be confident which records are yours — see Your choices and data deletion.
International users
RepPlate is available in more than one country, and the service providers listed above operate infrastructure in more than one country. Information handled by RepPlate may therefore be processed outside the country you are in, including in countries whose data protection rules differ from your own.
By using RepPlate you understand that your information may be processed in this way. If you have questions about where a particular piece of processing happens, ask us and we will tell you what we know.
Changes to this policy
We update this policy when RepPlate changes — when a new service provider is introduced, when data handling changes, or when we can be more specific than we are today. When we do, the effective date at the top of this page changes. Material changes will be surfaced in the app.
Contact
Questions about this policy, or about how RepPlate handles your information: email hello@froggyhub.com.
RepPlate is published by FroggyHub.
See also RepPlate Terms of Use and RepPlate Support.