On this page
Privacy policy
Nutreps is not yet released; this page describes the app at launch and distinguishes current website processing. This is a draft, not confirmation that every launch control is already operational.
The short version
Your health records are private by default. Health consent and cloud-AI consent are separate. You can choose manual logging instead of cloud AI. We do not sell your data; sharing with service providers to run a requested feature is described below. Website demonstrations use fixed fictional data.
Who is responsible
Nutreps is the product brand. The operator’s full legal identity, country and correspondence address are not yet published. Contact privacy@nutreps.com for privacy and support@nutreps.com for support.
Scope, eligibility and age
The app is intended only for people 18 and over, including its AI features. This policy covers the app and nutreps.com. Do not submit another person’s information without authority. If an underage account is identified, contact us so we can investigate and remove it as appropriate.
Data we collect and why
The table describes intended launch processing. Under GDPR, the listed Article 6 basis and, for health data, Article 9 condition must both apply. Other markets require their own assessment. Retention figures labelled targets are not verified current deletion guarantees. “Backend” means our Supabase service.
| Data | Purpose | Intended basis | Processing location | Retention target |
|---|---|---|---|---|
| Account ID and linked sign-in identity | Account access and recovery | Contract, Art. 6(1)(b) | Backend; Apple/Google for linked login | Until account deletion |
| Apple sign-in tokens | Manage and revoke sign-in | Contract | Backend and Apple | Until revocation/deletion |
| Language, units, theme, reminders | Preferences and local reminders | Contract | Device; backend when synced | Until reset/deletion |
| Body profile, weight, goals, measurements, food/training logs | Tracking and target estimates | Explicit consent, 6(1)(a) + 9(2)(a) | Device and backend | Until deletion or health-consent withdrawal |
| Saved meal and progress photos | Private diary | Explicit health consent | Device and private backend storage | Until photo/meal/account deletion; file-cleanup schedule below |
| Meal-scan photo/text and temporary response | Suggest foods and portions | Separate AI consent; explicit health consent where applicable | Backend → paid Gemini API | Scan session deleted on save or within 7 days; Google’s schedule separately |
| Scan corrections and ratings | Evaluate and improve scan quality | Separate optional improvement consent | Backend | Target 90 days; earlier on consent withdrawal |
| Kilo messages and selected health/workout context | Contextual answers | AI consent plus explicit health consent for health context | Backend → paid Gemini API | Messages up to 30 days; Google’s schedule separately |
| Nutrition-label images | Read label text | Requested feature; health consent if saved as health records | On-device OCR | Temporary memory for OCR; no image upload for this step |
| Barcodes and shared products | Look up and maintain catalog | Contract; content permission in Terms | Backend; Open Food Facts receives barcode only | Personal links until deletion; genuinely non-personal catalog information may remain |
| Handle, avatar, posts, follows and reports | Optional community | Contract; separate consent for any publication of health data | Backend and permitted viewers | Until deletion/leaving community; justified moderation exceptions separately |
| Attestation, install ID, security logs | Prevent abuse | Legitimate interests, 6(1)(f), subject to assessment | Backend, Apple/Google | Ordinary logs target 30 days; incident records separately |
| Subscription status and transaction references | Premium entitlement and support | Contract; specific legal record duties | Apple/Google and purchase-verification backend | Entitlement until deletion; required receipts under applicable law |
| Rewarded-ad SDK data and viewing events | Optional rewards and fraud prevention | SDK/market-specific basis; consent where required | Selected provider and backend | Provider schedule not yet selected; no health data sent |
| Website IP/access logs, traffic metrics and consent choices | Operate and measure website | Legitimate interests where appropriate; consent where required | Cloudflare; Umami if configured | Log target 30 days, event target 90 days; deployment/provider schedules to verify |
| Support emails, rights requests and consent evidence | Resolve requests and prove compliance | Contract, legitimate interests or a specific legal duty | Email service and request records | Support target 90 days after closure; legal evidence on a separate justified schedule |
| Form frames, pose landmarks and equipment images | Form feedback and equipment identification | Requested optional feature; health consent where relevant | On-device | Transient processing; any saved local video remains under your control |
Photos, AI and on-device processing
Meal photos and typed descriptions go through our backend to Google’s paid Gemini API, with separate AI consent. We do not attach your name or email. Photos and free text may themselves identify you, so avoid unnecessary identifying details. Food and portion suggestions can be wrong; calories use database matches where available and AI-only values are labelled estimates.
Kilo (Premium) sends your message and the context selected for the answer: profile information, goal, calorie target, recent weight/workout history and recent conversation. Review the sharing explanation before use.
Google’s paid-service terms say prompts and responses are not used to improve Google’s products. This does not mean zero retention: Google’s abuse-monitoring policy currently describes 55-day retention of prompts, context and outputs, with restricted human review for flagged content. Processing may occur outside your country.
Form-check frames and pose analysis use Google’s on-device pose library; video is not uploaded for analysis. Equipment recognition runs on-device after a one-time model download; equipment photos are not uploaded. Nutrition-label OCR also runs on-device. Model downloads involve network traffic without uploading your image.
Consent, optional features and withdrawal
Health storage, cloud AI and optional use of scan feedback for improvement require separate choices. Refusing improvement consent must not prevent ordinary AI use. Withdraw health or AI consent in Settings → Your data; health withdrawal removes associated health records while keeping the account. Stop cloud AI by withdrawing AI consent and use manual entry. Withdrawal does not undo lawful prior processing; explain provider retention and deletion limits when responding.
Apple Health and Health Connect
Connecting Apple Health (iPhone) or Health Connect (Android) is optional and needs its own consent, separate from health storage and AI. You choose each group and the system asks for permission per data type.
- What we receive: weight, body fat percentage, steps and active calories, workouts recorded by other apps, and sleep. What we send: weight, body fat percentage, meals (calories, macros and up to four micronutrients), water and Nutreps workouts.
- Why: to fill your logs without retyping and keep your health app up to date with what you log in Nutreps. Entries you make by hand always come first.
- Where it is stored: received data is stored in your Nutreps account on our servers, including guest accounts. We import at most the last 30 days and send only from the moment you turn a group on.
- What we never do: health-app data is never sold, never used for advertising or ad measurement, and never stored in iCloud by Nutreps.
- Kilo: the AI coach uses only a short summary (for example average steps or sleep) and only if you have also given AI consent.
- Stopping and deleting: stop syncing on one device, revoke permissions at any time in the Health app or Health Connect settings, delete imported data per group, or withdraw the connection consent in Settings → Your data, which stops every device and deletes everything received. When deleting your account you can also delete the samples Nutreps sent from that device; samples already sent otherwise stay in the health app until you delete them there.
- Health Connect Limited Use: data obtained through Health Connect is used only to provide the features described above, in line with the Health Connect Permissions Policy and its Limited Use requirements; it is not transferred to third parties except as needed for those features, for legal reasons or as part of a merger, and humans do not read it except with your consent, for security or as required by law.
Community and shared product information
Community participation is optional and needs a linked account and community terms. Your handle, avatar and permitted posts can be visible to other members. The designed feed uses an allowlist that excludes weight, calorie totals, body measurements, gym and training maxes. Leaving deletes your community profile and linked social records. Reports may be retained only under a documented moderation need.
Shared barcode product facts can be used by other people without publishing your name. Remove personal links on deletion; retain catalog facts only if genuinely non-personal.
Providers, processing locations and international transfers
We do not sell personal data. Providers receive information needed to supply the requested service; they are not all acting in the same legal role. See AI & data for the feature map.
- Supabase: authentication, database, private storage and functions. Frankfurt, Germany is the intended project region, not a verified claim for every subservice or subprocessor.
- Google Gemini API: paid cloud AI, potentially international processing.
- Apple/Google: linked login, device checks, app distribution and store purchases.
- Open Food Facts: barcode lookup; only the barcode is sent.
- Cloudflare: website delivery, optional Web Analytics and email routing.
- Umami: optional website traffic measurement, currently configured to use Umami Cloud when an ID is supplied.
- Rewarded-ad and subscription-management providers: not yet selected.
International transfers require the safeguards applicable to the launch market. Contact privacy@nutreps.com to request information about applicable safeguards; we will not claim all processing remains in the EU.
Website analytics, cookies and advertising
The website does not ask for health records. Umami loads only when configured; Meta/TikTok pixels, if configured, load only after Allow in the consent banner. Change your choice using Cookie settings below the page when pixels are configured. Cloudflare hosting processes connection data; Cloudflare Web Analytics may be enabled separately. Cookie-free measurement can still involve personal-data processing. The site stores consent choices and session campaign attribution in browser storage.
The launch app plans optional rewarded advertisements for free users. No health data will be sent to advertising providers or used for ad targeting. The provider, device identifiers, retention and market-specific consent will be disclosed before ads are enabled.
Retention, deletion and backups
Keep records only for their stated purpose. Account-linked data normally remains until deleted or consent is withdrawn. Operational deletion targets after verification: active database 24 hours, stored files/caches 7 days, backups no more than 30 days if the selected infrastructure supports this. These targets need implementation checks before launch. Backups are isolated from ordinary use and deletions must be reapplied after recovery. Provider retention is separate; account deletion does not instantly erase Google’s security logs or store records. See deletion details.
Your rights and how to make a request
- Export my data: Settings → Your data → Export my data.
- Delete your account: Settings → Your data → Delete account, or request help by email.
- Ask privacy@nutreps.com for access, correction, deletion, portability, restriction, objection or consent withdrawal as available under your law. We verify ownership proportionately; do not email passwords or full payment details.
- For EU/UK requests, respond without undue delay, normally within one month; explain any lawful extension. These legal response periods differ from backend-cleanup targets. See UK government guidance.
- You may complain to your competent data-protection authority.
Security
Encrypted transport, account-scoped access rules, private storage and server-side AI keys are part of the design. No system is risk-free. Report suspected exposure to privacy@nutreps.com. Access to sensitive records should be limited and logged; incident notices will follow applicable law.
Changes and contact
Version 1.0, updated 2026-10-25. Material changes will be explained before they take effect where required; new purposes requiring consent need a new choice. English and Vietnamese are draft language versions awaiting legal review. Contact: Nutreps — privacy@nutreps.com (privacy), support@nutreps.com (support).