Privacy Policy

Last updated: September 6, 2026

FitVete ("we", "us") builds a fitness and nutrition app for iPhone. This policy explains what we collect, why, and the choices you have. We designed FitVete to keep as much of your data on your device as possible.

Information we collect

• Account data — email and authentication details used to sign you in and sync your data across devices.
• Profile & health inputs — age, height, weight, goals, body measurements, workouts, meals, sleep, and activity you log.
• Photos you provide — meal photos and body-scan photos you choose to capture. Body-scan photos are normalized on-device and processed to produce measurements.
• Support content — messages and ticket details you choose to send through the private in-app support chat.
• Purchase and eligibility signals — App Store transaction identifiers and status, plus Apple DeviceCheck state and keyed one-way server-side eligibility tokens used to enforce one free app-access trial.
• Diagnostics — anonymous aggregate MetricKit performance counters and crash-signal counts used to improve reliability. FitVete does not upload raw stack traces, exception reasons, file paths, health data, account IDs, or persistent device identifiers with these reports.

How we use it

• To provide core features: tracking, body composition estimates, plans, and coaching.
• To sync your data securely to your account so it's available on your devices.
• To answer support requests, verify subscription access, prevent repeated trial abuse, and protect the service from fraud.
• To improve app stability and feature quality.

On-device processing

Some FitVete features run on-device, including body-scan pose validation and local data summaries. Features that need cloud providers send only the data required for the request.

Third-party services

We use trusted providers strictly to deliver features you request — including authentication and database/storage (Supabase), purchases and device eligibility (Apple), nutrition lookups (USDA FoodData Central, licensed reference provider), AI meal analysis (Anthropic), and body-composition inference (Bodygram). Data shared with these providers is limited to what's needed to fulfill your request. We do not sell your personal data.

Optional food logging measurements, invitations and exports

You can enable “Help improve food logging” in Settings to share anonymous success, failure, correction and draft-recovery counts and timing ranges. These reports include app version, build and reporting day, but no account identifier, food names, photos or nutrition values. Authentication limits misuse; the account identifier is not stored with the report. Turning this off clears reports waiting on your device. Anonymous reports cannot later be located by account.

Invitations are shared only when you choose the system share action. Applying a code records the referring and invited accounts; it grants no discount or subscription benefit. Account deletion removes related referral records. PDF progress reports are generated on your device and shared only through destinations you choose.

When you enable the Apple Watch companion, your paired watch receives a limited account-scoped snapshot of calories remaining and water totals, and can queue water entries for your iPhone. Disabling the connection or signing out clears the next delivered snapshot. An offline watch can retain its previous snapshot until reconnection; the app displays the last sync date and hides snapshots older than a day.

Meal scan memory & corrections

Cloud meal and label scans can save structured food estimates, an image fingerprint, and your corrections in private memory linked to your app or developer account. This lets an identical rescan reuse your latest result. Raw images are not stored in this memory. Meal photos you separately confirm and save in your diary follow the account retention policy below; on-device scans are not automatically uploaded for learning.

Scan memory expires 30 days after creation and is excluded from retrieval and evaluation exports at expiry; an hourly cleanup removes expired records in bounded batches. Corrections are private by default. Optional contribution of corrected food facts requires explicit permission and review before inclusion in evaluation data. Images, account identifiers, and image fingerprints are excluded from these exports. Saving a scan does not automatically train a model or add your meal to the public food database.

Direct API customers can retrieve, correct, or remove scan memory through the scan management endpoints. Removing a scan or withdrawing contribution removes its eligibility for future evaluation exports. Contact privacy@fitvete.com for help. Deleting your account also removes its scan memory.

Photo-beta users can separately choose to save a private food-card photo and opt in to “Help improve scans.” With that additional consent, the photo, original prediction and corrected food/portion details enter a private review queue. They are not automatically used to train a model or added to the public food database. User-entered portions are not scale-verified measurements. You can withdraw sharing or remove saved photos in the iPhone app under Food > Saved food photos, including after beta enrollment ends. Withdrawing sharing removes eligibility for future review exports; deleting a photo also removes its card image and retained photo evidence. Saved photos remain until you remove them or delete your account.

Apple Health

With your permission, FitVete reads and writes data such as workouts, sleep, weight, body composition, and water to Apple Health. You control this access in the Health app and iOS Settings at any time.

Data retention & deletion

Your account data, synced fitness and nutrition records, support conversations, and owned cloud photos are retained while your account is active. You can delete them in FitVete under Profile > Settings > Delete Account, or request help by emailing privacy@fitvete.com.

Anonymous aggregate diagnostics are retained for up to 180 days and cannot be retrieved or deleted by account because FitVete does not store an account identifier with them. Apple may separately provide delayed, opt-in, privacy-thresholded diagnostics under its platform rules.

Account deletion removes the account, raw email/provider identifier, associated synced records, support content, and owned cloud files. To prevent repeated free-trial abuse, we retain a keyed one-way eligibility token that can only be matched server-side; the raw identity is not retained in that ledger. Apple separately retains the two-bit DeviceCheck state under its platform rules. Pseudonymous App Store transaction state and other financial, security, or legal records may be retained only to verify purchases, prevent fraud, handle refunds or disputes, or meet legal obligations.

Your rights

Depending on where you live, you may have rights to access, correct, export, or delete your data. Contact us and we'll help.

Children

FitVete is not directed to children under 13 (or the age required in your region), and we do not knowingly collect their data.

Changes

We'll post any updates here and revise the date above.

Contact

Questions? Email privacy@fitvete.com.