Privacy Policy

Effective date: 16 Sep 2026

• 1. Who we are
• 2. What the app stores on your device
• 3. Where it is stored
• 4. When data leaves your device (only on your action)
• 5. Apple Health and Health Connect
• 6. Permissions
• 7. What we do not do
• 8. Security
• 9. Retention and deletion
• 10. Children
• 11. Changes to this policy
• 12. Contact

1. Who we are

Ayuvo ("the app") is published by Yaara Tech, Karauli, Rajasthan, India ("we", "us"). You can reach us at yaaratech@gmail.com. The app is built on the MIT-licensed "Fud AI" open-source code base; the original licence notice is reproduced in the app under Settings → Legal → Licenses.

This policy applies to the Ayuvo apps for iPhone, Apple Watch and Android and to this website. The website is a static site that sets no cookies and loads nothing from third parties.

2. What the app stores on your device

Everything below is kept in the app's private storage on your phone. We cannot access any of it.

• Profile: gender, date of birth, height, weight, body fat percentage, activity level, goals, target weight, weekly rate, custom meal times, units and appearance preferences.
• Food diary: entries, nutrition values, ingredients, serving details, meal photos and thumbnails, saved meals, notes.
• Body: weight and body-fat history.
• Water and fasting: water entries and goal; fasting sessions you explicitly start, with goal, start/end times and completion status.
• Workouts: plans, logged sets (reps, weight, RPE), completed sessions, calculated calorie burn, library preferences.
• Health data hub: a local SQLite mirror of the Apple Health / Health Connect data types you granted (see section 5).
• Health records: the documents you add — lab reports, prescriptions, consultation notes, discharge summaries, imaging reports, bills, photos, scans and text notes — kept as the original files, plus the text read from them, the details and test values extracted from them, highlights, your notes, tags and the links between records.
• Coach: your chat history with the AI coach, kept locally so the conversation has memory.
• API keys: the AI and speech-to-text provider keys you enter, stored in the iOS Keychain or in Android EncryptedSharedPreferences (AES-256, backed by the Android Keystore).
• Widget and Watch snapshots: today's totals and goals, written to the app group container so widgets and the Watch app can show them.

3. Where it is stored

4. When data leaves your device (only on your action)

Ayuvo makes no network request on its own behalf. Each flow below happens only when you trigger it, and it goes directly from your phone to the service named.

4.1 AI providers you configure (bring your own key)

When you analyse a meal, ask the coach, request a nutrient-goal estimate or a "What if?" suggestion, the app sends the request directly to the provider you selected: Google Gemini, OpenAI, Anthropic, xAI, OpenRouter, Together AI, Groq, Hugging Face, Fireworks AI, DeepInfra, Mistral, DeepSeek, Cerebras, Ollama, or a custom OpenAI-compatible endpoint you enter. What is sent depends on the action: meal photos and notes, text descriptions, voice transcripts, coach messages, and the context the coach requests (profile, targets, food log, workouts, weight trend, explicitly logged fasts). Your Health data hub is included only while the "Let Coach use my health data" toggle is on, and your health records only as described in 4.9; the toggle is shown at every connect step and in Settings → Health & Data. Apple Intelligence (iPhone) and the on-device Gemma 4 E2B model process on your phone and send nothing anywhere. Each provider's own privacy policy governs what it does with your request: Google, OpenAI, Anthropic, xAI, OpenRouter, Together AI, Groq, Hugging Face, Fireworks AI, DeepInfra, Mistral, DeepSeek, Cerebras.

4.2 Speech-to-text providers

Voice input uses on-device recognition by default (Native iOS / Native Android, or the on-device Whisper Base model). If you choose a cloud provider — Gemini, OpenAI, Groq, Mistral, Deepgram or AssemblyAI — the audio clip is sent to that provider with your key (Deepgram, AssemblyAI).

4.3 Open Food Facts (barcodes)

When you scan a barcode, the barcode number — and nothing else — is sent to the public Open Food Facts database to look up the product (their privacy notice). Product data is licensed under the Open Database License.

4.4 Exercise images

When you open the Workouts library, exercise thumbnails and animations are fetched from raw.githubusercontent.com (the open exercises-dataset repository; media © Gym visual). This is a plain image request with no account or identifier; GitHub sees your IP address, as any web request would.

4.5 On-device model downloads

Tapping Download fetches the Gemma 4 E2B or Whisper Base model files from Hugging Face (anonymous, checksum-verified). Hugging Face sees your IP address. The models then run entirely on your phone.

4.6 Optional iCloud / Google Drive backup

Off by default. If you turn it on in Settings → Data Management, iPhone stores an archive in your private iCloud (CloudKit) database and Android stores it in your Google Drive app folder after you sign in at that toggle. The archive contains your logs, saved meals, photos, water, fasts, workouts, goals and preferences. It never contains the Health data hub database or the coach chat history, on either platform. Apple or Google process the archive under their own terms; we cannot access it.

4.7 App update checks and review prompts

iPhone asks Apple's public App Store lookup service for the current listing of Ayuvo's App Store ID; Android asks the Google Play In-App Update API. Store review prompts are handled by the operating system. Nothing from your logs is sent.

4.8 Operating-system backups

Apple and Google device backups and device-to-device transfers may include eligible app data according to your OS settings. The Health data hub and the coach chat are explicitly excluded from those backups. Keychain items may survive an uninstall on iPhone.

4.9 Health records: AI processing, sharing and backup

AI processing. When you add a document, Ayuvo saves the original and reads it on your phone — the text layer of a PDF, or on-device text recognition for photos and scans. Details such as the doctor, hospital, dates and test values are found by rules that run entirely on your phone. You choose how AI may help, during setup and in Settings → Health Records → AI processing: Local AI (the on-device model only), Cloud AI (your configured provider), Ask me (asked per document) or Skip AI (no AI at all). With Cloud AI, the text read from the document is sent to the provider you chose with your own key; pages with no readable text may be sent as images. The status on each record says whether it was processed on this device, processed with online AI (naming the provider), or not processed by AI.

Coach. Coach can read your records only after you allow it ("Let Coach read your health records", off by default). When you select records for a conversation, Coach can read only those. Patient name, address, phone numbers and ID numbers are never included in what Coach receives. With an on-device Coach model, nothing leaves your phone.

Sharing. Sharing happens only when you tap Share. You choose which records, which pages and which details go out, and you can black out name, address, phone, patient ID, insurance ID and other identifiers; blacked-out pages are shared as images so covered text cannot be recovered. The final screen lists every file before anything is sent, and where it goes is entirely up to the app you pick.

Backup. Health records are never part of the normal iCloud or Google Drive backup in 4.6. You can export an archive of your records and save it wherever you choose; on Android you can additionally turn on "Include Health Records in Google Drive backup", which uploads that archive to your own Google Drive app folder. Both are off until you act.

5. Apple Health and Health Connect

Purpose. With your permission, Ayuvo reads the Health / Health Connect data types you grant so it can show them in the Health Data hub — Home tiles, category lists, detail charts and history — and keep that local history in sync on this phone. It writes only the nutrition, body measurements (weight, height, body fat) and calculated workout calories that you log in Ayuvo.

Read types (each requested separately; grant only what you want): activity (steps, distance, energy, floors, exercise sessions), body measurements, heart (heart rate, resting heart rate, heart rate variability, blood pressure, VO2 max), sleep, vitals (blood glucose, body temperature, oxygen saturation, respiratory rate), mobility, hearing, cycle tracking, mindfulness, symptoms, nutrition and hydration. Write types: nutrition, weight, height, body fat, active calories burned. Fasting and water are never written to Health.

Storage and sharing. Health data is kept on this device, in the app's local hub database. It is never stored in iCloud or Google Drive backups, never used for advertising, never sold, and never shared with anyone except your chosen AI provider through the coach — and only while the "Let Coach use my health data" toggle is on.

Revoking access. iPhone: Settings → Health → Data Access & Devices → Ayuvo, or the Health app → Sharing → Apps. Android: Health Connect → App permissions → Ayuvo. When you revoke a type, the hub stops syncing it; the mirrored history stays until you use "Clear synced health data" or Delete All Data in Ayuvo.

6. Permissions

• Camera — photographing meals, scanning barcodes, and photographing or scanning health records.
• Photos and files — only the images and documents you pick, or that you send to Ayuvo from another app, to add them to Health Records.
• Microphone and speech recognition — voice meal input.
• Photos — picking existing meal photos through the system picker (no library access) and, on iPhone, saving a photo when you tap Save.
• Notifications — meal, streak, daily-summary, weight, water and fasting reminders you enable; all scheduled locally.
• Health — only if you enable Apple Health or Health Connect (section 5).
• Local network (iPhone) — only if you point the app at an Ollama server on your network.
• Internet — for the flows in section 4.
• Battery optimisation exemption (Android, optional) — so scheduled reminders fire on time.

7. What we do not do

• No analytics, crash-reporting or advertising SDKs of any kind.
• No account, sign-in, cloud sync or Ayuvo-operated servers.
• No tracking of your behaviour, location or browsing.
• No selling, renting or sharing of personal data.
• We never see your API keys, your health data, your photos or your conversations.

8. Security

All app-initiated requests use HTTPS with modern TLS. The only exception is a local-network endpoint you enter yourself (for example an Ollama server), which may use plain HTTP within your own network. API keys are stored in the iOS Keychain or Android EncryptedSharedPreferences and never transmitted anywhere except, as part of the request, to the provider that issued them.

9. Retention and deletion

• Your data stays on your device until you delete it.
• Delete All Data (Settings) wipes food, weight, body fat, water, fasting, workouts, the Health data hub database, health records (originals and everything read from them), coach history, saved meals, keys and preferences on this device.
• You can delete a single health record at any time from the record itself; that removes its original file, its extracted details and values, and its links. Archives you exported earlier are yours to delete wherever you saved them.
• It does not delete Apple Health / Health Connect samples (manage those in Health or Health Connect), logs kept by your AI provider under its own policy, or backups you keep in iCloud / Google Drive (delete those from Settings → Data Management → Cloud Backup).
• You can export the food diary (JSON, CSV, Markdown) and the Health data hub (zip) from Settings → Data Management, and your health records (zip, with the original files) from Settings → Health Records → Backup.
• Uninstalling removes the app's sandbox; Keychain items on iPhone and OS backups may persist according to your device settings.

10. Children

Ayuvo is not directed at children under 13 and is listed for ages 13 and over. We do not knowingly collect personal information from children; since the app has no account and no server, we hold no personal information from anyone.

11. Changes to this policy

We may update this policy as the app evolves. The effective date at the top changes with every revision, and material changes are noted in the app's release notes.

12. Contact

Questions or requests: yaaratech@gmail.com · Yaara Tech, Karauli, Rajasthan, India.