Data Usage

Eleviy uses data only for product, security, support, analytics with consent, billing, legal, and user-requested workflows. We do not sell, rent, trade, broker, or provide personal or sensitive user data to third parties for their independent use.

This page summarizes the main feature-by-feature data flows. The Privacy Policy remains the controlling privacy document, and the Data Deletion page explains how to request deletion.

Account data is used to create and secure your account, verify email, support Google or Apple sign-in, rotate sessions, restore access, apply region and unit preferences, manage subscription tier, and process export or deletion requests.

Profile data is used to personalize targets, meal guidance, workouts, reminders, AI coach context, reports, and progress summaries. This can include goals, weight, height, biological sex, age, activity level, fitness level, allergies, dietary preference, equipment, training schedule, coaching mode, and custom instructions.

Meal logging can use text, photos, voice, barcode scans, manual corrections, and saved foods. Eleviy uses this data to estimate ingredients, calories, macros, meal timing, food source confidence, and daily nutrition totals.

Meal photos and voice clips may be sent to AI or transcription services when you choose those features. Barcodes may be checked against first-party records or third-party food databases. You should review AI estimates before saving them.

Workout and progress features use workout plans, completed sessions, sets, reps, weights, exercise choices, body metrics, progress photos, personal records, fatigue scores, TDEE estimates, and weekly activity summaries to support planning and progress review.

Progress photos are used for visual progress tracking and AI analysis when enabled. They are sensitive personal data; use the feature only if you are comfortable storing those images in your account.

Cycle sync is optional and available only for eligible profiles. It can use Health Connect or Apple Health menstrual-flow data, manually entered last period date, and average cycle length to calculate phase-aware coaching notes.

Cycle data may influence workout intensity notes, nutrition notes, reminders, AI coach context, and dashboard cards. On Android, Eleviy currently limits health-platform sync to optional cycle data and does not import steps, sleep, or active calories.

AI features use your prompts, messages, meal inputs, workout context, recent nutrition context, profile settings, cycle context if enabled, readiness context if enabled, and prior conversation context to generate responses and reports.

AI output is educational support and can be wrong. Eleviy may store prompts, AI outputs, token metadata, and report content to provide history, regenerate messages, support safety review, debug errors, and improve product reliability.

Family and corporate features use invite tokens, group membership, shared meals, challenge progress, challenge results, and limited member summaries to provide shared dashboards, challenges, and admin workflows.

Only join a family or corporate space if you understand that selected activity, meal, challenge, or progress information may be visible to other members or administrators in that space.

Eleviy uses Firebase Cloud Messaging tokens and notification preferences to send reminders and app updates you enable. Firebase Crashlytics may receive crash and diagnostic information so we can investigate crashes and reliability issues.

The app uses RevenueCat and app-store billing systems for subscription purchase status, entitlement activation, restoration, renewal, cancellation state, refunds, and fraud prevention. Eleviy does not store full card details.

The website collects only the information you submit in forms or allow through consent controls. Contact, waitlist, newsletter, and partnership forms may store email, name, message, source page, consent text, and anti-spam signals.

Website analytics are consent-gated where enabled. Analytics validation blocks obvious sensitive fields such as health, meal, workout, email, password, token, IP, and message content from event payloads.

Camera access is used for meal scans, menu/fridge scans, and progress photos. Microphone or speech access is used for voice meal logging and voice input. Photo or media access is used when you pick images for meal or progress features. Health permission is used for optional cycle sync. Notifications are used for reminders and account-relevant app messages.

If you deny a permission, the related feature may not work, but other app features should remain available where technically possible. You can change permissions through the app settings or device settings.

You can request export from the app, request account deletion from the app or /data-deletion, disable cycle sync, delete individual progress photos, update notification preferences, unsubscribe from emails, revoke OS permissions, and manage app-store subscriptions through the store subscription center.

The Play Console Data safety form should stay synchronized with this page, the Privacy Policy, app permissions, SDK behavior, and backend deletion/export behavior for every release.