eativa

Privacy Policy

Updated 2026-09-05

Your journal, your choices

This policy explains how Eativa handles data for food logging, workout tracking, weight check-ins, optional AI assistance and subscriptions. We do not sell health or journal data, use it for advertising, or track you across other companies’ apps and websites.

What we store and why

Account data includes your name, email, sign-in provider and account identifier. Your journal may include age, height, weight, goals, food and workout notes, nutrition estimates, exercise sets and loads, gym check-ins, and photos or videos you choose to save. These records provide the features you request and sync your journal between sessions.

An account-specific local copy is stored on your iPhone. Cloudflare stores synced profile, journal, weight and chat records. Supabase provides authentication, private journal media storage and server functions. Service providers may process connection information, such as an IP address and request metadata, to operate and secure the service.

Apple Health and device permissions

Connecting Apple Health is optional. Eativa reads step counts to display your daily steps and widget. It does not write HealthKit records or send HealthKit steps to AI providers. Health access can be changed in Apple Health or iOS Settings.

Microphone, speech recognition, camera, photo selection and notifications are used only for their related features. You can deny or later change permissions in iOS Settings. Basic typed logging does not require camera, microphone or Health access.

Optional AI processing

After you allow AI assistance, note text and spoken audio can be sent through Supabase to OpenAI for transcription and structured food or workout estimates. Apple Speech may process speech as a fallback. Snack suggestions can send the images you explicitly choose and your remaining-calorie budget to OpenAI. Ordinary saved journal photos and videos are not automatically sent to AI.

Meal photo scanning requests separate consent before sending the selected meal photo through Supabase to Google Gemini. The scan does not include your journal history, body measurements or Apple Health steps. Review the estimate before saving; a saved scan photo becomes private journal media.

Ory requests separate history consent. With that consent, relevant logged food, exercise, weight and goal records, your question and recent conversation may be sent to OpenAI to answer fitness questions. Ory does not receive saved media attachments or Apple Health steps. AI outputs may be inaccurate. They are not medical advice.

You can withdraw AI permissions in Settings or Ory’s menu. Withdrawal stops future processing under that permission; it cannot recall information already processed. Avoid including unrelated sensitive information in notes, photos or chat.

Purchases

Apple processes payments. RevenueCat receives your account identifier and purchase, subscription and entitlement information to verify and restore access, prevent purchase fraud, and provide subscription analytics such as purchase history and revenue reports. These analytics are not used to track you across other companies’ apps or websites for advertising. We do not send food notes, weights, gym responses or Apple Health data to RevenueCat. We do not receive your payment card number.

Storage, retention and deletion

We retain active journal and account records while you use the account, unless you delete them. Ory chat can be cleared separately; a daily usage count remains to enforce the 20-message allowance. That count is removed with account deletion.

Delete account is available in Settings and from the paywall’s Account menu. It removes your sign-in account, synced profile, weight records, journal, chat and private media. A minimal account-ID deletion marker remains to prevent delayed requests from recreating deleted data. Apple and RevenueCat purchase records are managed separately for purchase validation, restore and applicable retention obligations.

Local health files, widget values and onboarding drafts are stored with iOS data protection and excluded from device backup. Cloud hosting and AI providers may retain operational or backup copies according to their service settings and retention policies; deletion is not a promise that every provider backup vanishes immediately. We use these providers to deliver the service, not to advertise using your health data.

Signing out clears the active account from the interface and widget; it does not delete your cloud account. Deleting Eativa does not cancel an Apple subscription. Cancel subscriptions separately in App Store settings.

Your controls

You can edit your records, change targets, export your journal, withdraw optional permissions, clear chat or delete your account. For access, correction, deletion or other privacy requests you cannot complete in the app, contact us. Depending on where you live, additional privacy rights may apply. We may need to verify account ownership before acting on a request.

Our hosting and processing providers may handle data outside your country. If this policy changes, we will update its date and provide additional notice or consent where required.

Contact

Eativa is provided by ehmad.

ehmad@qluedental.xyz

For privacy requests, contact us from the email associated with your account. Never send passwords, sign-in codes or payment card details.