Your data should stay yours.

1. Scope and who to contact

This policy applies to the IZEM mobile app and IZEM’s public legal and support pages. IZEM provides adult-only, AI-assisted fitness and general wellness coaching. When this policy says “IZEM,” “we,” or “us,” it means the IZEM service identified in the app and on this site.

For a privacy request, account-deletion issue, or question about this policy, email support@youraicoach.life from the address associated with your account when possible. We may need to verify account ownership before acting on a request.

2. Information IZEM processes

We receive information directly from you; from Apple, Google, or another sign-in provider you choose; from the App Store, Google Play, and RevenueCat for purchases; and from your device for permissions, notifications, calls, and diagnostics. If you connect Apple Health, the app reads selected categories locally for the on-device dashboard. The dashboard is not uploaded. A separate, default-off, versioned category choice is required before a smaller summary can support coaching. Our infrastructure providers may also process ordinary network information such as IP address and request timing to deliver and secure the service.

We use these categories to authenticate accounts, enforce adult and consent requirements, provide and personalize features you request, validate membership, deliver calls and notifications, maintain continuity, respond to support, secure the service, prevent fraud and duplicate use, measure service cost and reliability, and comply with law. We do not sell personal information, use it for cross-app tracking, run advertising in IZEM, or use personal information for targeted advertising.

IZEM may use observable workout-completion patterns and coarse call-engagement signals—such as call duration, turn balance, or an early end—to make coaching less repetitive and lower pressure when an approach is not landing. These signals are not used to diagnose you or treated as proof of your mood, personality, motive, or intent, and they are never used for advertising or cross-app tracking.

3. AI coaching, voice, and visual analysis

When you grant the separate in-app AI-processing permission and use an AI feature, relevant information—such as your coaching profile, prompt, selected photo, live voice audio, or plan context—is sent to a paid third-party AI API service. IZEM uses this service to create and adjust workout or meal plans at your request, answer coach chats, power live voice coaching, and analyze photos you select for meal, equipment, movement, chat, or body-progress features.

IZEM uses paid production API credentials for all release traffic. Google Gemini’s paid-service terms say prompts and outputs are not used to improve its products, while its current abuse-monitoring policy says prompts, context, and outputs may be retained for up to 55 days for safety, security, and required legal or regulatory disclosures; flagged content may be reviewed by authorized personnel. IZEM does not opt into sharing AI logs, datasets, or feedback for provider product improvement.

Raw photos are transmitted for the selected analysis but are not retained in IZEM’s database or cloud storage. The resulting estimates and coaching analysis may remain in your account until you delete the available record or your account. Meal-photo estimates cannot verify ingredients, allergens, cross-contact, dietary or religious compliance, or food safety. Body and movement results are approximate visual estimates—not identity, diagnosis, body-composition measurement, injury assessment, or proof of health or ability.

Live coach audio is sent after you answer or start a call. Every answered live voice call uses Inworld through IZEM’s managed worker. There is no fallback voice provider. IZEM does not retain a raw voice recording on its servers. For ordinary calls, IZEM may retain a bounded coaching summary or validated memory, call-continuity state, aggregate engagement, usage, and safety records. Voice calls do not receive Apple Health context in this release.

IZEM stores account data needed to make the product work, including plans, conversation records, scan analyses, bounded thread summaries, and carefully validated coaching memories. Raw selected photos and raw voice recordings are not retained by IZEM servers. A normal assistant reply may reflect a minimized Health pattern and remain in chat. If you directly ask what Apple Health shows, that saved reply may repeat the single relevant rounded aggregate with uncertainty. A workout change remains only after you explicitly request and confirm it; Health-marked turns are excluded from future model history, thread summaries, and coach memory. Before membership or analysis, you may choose to keep one optional front-and-side body-scan pair encrypted in the app’s backup-excluded private storage on your device with an account-scoped, non-migrating device key. That pair is not uploaded or analyzed until membership is active and you separately choose “Analyze saved photos.” Temporary decrypted files are removed after each attempt; the encrypted pair is removed after successful analysis, when you delete it, when you sign out, or when you delete the account.

To show a photo or voice note back inside its chat, the app may keep an account-scoped copy in the device’s non-backed-up cache; those copies may be evicted by the operating system and are removed when you sign out or delete the account. If you use Sign in with Apple, IZEM stores a server-only Apple refresh credential solely so the app can revoke its Apple authorization when you delete the account; the credential is never exposed to the app and is removed with the account.

4. Apple Health is optional and separately controlled

If you connect Apple Health, IZEM requests read-only access to the categories you select, which may include steps, Apple Exercise Time, sleep analysis, workouts, resting heart rate, heart-rate variability (SDNN), and body mass. The dashboard is built on your iPhone from bounded recent aggregates. IZEM does not upload or retain the dashboard, use it for ads or analytics, or write to Apple Health. Missing data is shown as unavailable—not as zero.

“Use Health with my coach”

This is a separate, default-off permission governed by policy version health-coaching-2026-09-v4. If you explicitly enable it, IZEM creates a minimized coaching summary on your iPhone using only the categories you select. It can contain rounded seven-day activity, exercise, sleep, and workout patterns; sample coverage and freshness; qualitative resting-heart-rate and HRV bands compared with your own baseline; a rounded latest recorded sleep duration; and, only if separately enabled, a coarse body-weight range. It does not contain raw samples, routes, source devices, identifiers, exact measurement timestamps, exact heart-rate/HRV/weight values, HealthKit permission states, or a readiness score.

The coach may use this summary only for relevant coach chats you start or a workout suggestion or adjustment you explicitly request. Voice calls do not receive Apple Health context in this release. The summary is never used for the one-time onboarding test call, while any call is ringing, for nutrition changes, or to change a plan automatically.

For a user-initiated coach chat or an explicitly requested workout suggestion or adjustment, an IZEM Firebase Cloud Function rechecks the current account, membership, AI permission, Health-coaching permission, selected categories, rollout, and paid-AI configuration, converts the summary into bounded coaching context in memory, and sends it to the paid third-party AI service. The server-managed Inworld voice path does not accept this Health summary in this release. IZEM does not write the summary, its snapshot identifier, or a content hash to its database, request receipts, logs, analytics, crash reports, support exports, thread summaries, or coach memory. IZEM stores only the versioned category authorization and coarse provenance—a boolean indicating that an otherwise ordinary reply or confirmed plan change used Health context.

IZEM may keep only the minimized summary in encrypted, device-only Keychain storage so it is ready without delaying a request or an answered scheduled call. A summary up to 12 hours old is treated as current; a summary more than 12 and no more than 36 hours old is explicitly treated as stale; after 36 hours it is never used and is deleted the next time IZEM checks it. Turning off Health coaching blocks new process-local use immediately and attempts to remove both the server permission and encrypted cache. Disconnecting Apple Health, signing out, and deleting your account also trigger this cleanup. If every cleanup step cannot be confirmed, the app tells you to reopen the Health screen and retry rather than claiming completion.

The paid third-party AI service processes chat and requested workout context; its paid-service terms say prompts and outputs are not used to improve its products, and its abuse-monitoring policy permits retention for up to 55 days. Answered calls use Inworld for live audio, but Inworld does not receive the selected Apple Health summary in this release. Provider processing and retention are separate from the on-device dashboard. Turning Health coaching off blocks future Health use once the server and encrypted-storage cleanup is confirmed. It cannot undo a provider’s disclosed retention, remove an existing Health-influenced chat reply, or reverse a workout change you already confirmed. Apple Health context is for general fitness and wellness guidance—not diagnosis, a readiness score, medical clearance, emergency care, or a replacement for a clinician. Apple controls the underlying HealthKit permission in the Health app. Revoking or disconnecting IZEM does not delete records held by Apple Health.

5. Membership, trials, restores, and the onboarding test call

After onboarding, IZEM is a members-only service except for account, purchase, privacy, support, and other controls that must remain accessible. If offered, an eligible adult may choose one complimentary onboarding test call instead of immediately starting a membership. It is not a free tier. IZEM records the test-call eligibility, schedule, delivery, answer, connection, completion, and retry state needed to enforce one connected test per eligible account and prevent bypass. Every connected test session is hard-limited to exactly three minutes by the server, regardless of country; an unanswered ring may remain retryable under the product rules. The authorized duration, provider, and actual duration may be kept as content-free test-call funnel records; audio and conversation content are not included in those records.

Membership purchases are processed by Apple or Google. RevenueCat supplies storefront presentation and entitlement events, and IZEM’s server independently validates the entitlement before opening protected features. We may process product identifier, store, environment, purchase and expiration time, renewal or grace state, transaction/application-user identifiers, restore result, refund, cancellation, billing issue, and transfer events. We do not receive your full payment-card number. Deleting your IZEM account does not cancel an App Store or Google Play subscription.

6. Calls, notifications, and device delivery

If you enable coach calls or notifications, IZEM processes your preferences, schedule and time zone, device ownership marker, push or VoIP token, delivery attempts, answer/end state, and limited call diagnostics. On iOS, Apple Push Notification service, PushKit, and CallKit deliver and present eligible calls. On Android, Google Firebase Cloud Messaging and Twilio may act as parallel call-delivery channels; Twilio supplies a short account-and-device-bound ringing connection and is not the AI media relay once the coaching session begins. Microphone content is processed only after you answer or initiate the coaching session.

You can change eligible notification and call preferences in the app and can also revoke system permissions in device settings. Delivery is not guaranteed and may fail because of connectivity, device state, provider availability, operating-system policy, or revoked permissions. IZEM is not an emergency communication service.

7. Service providers

IZEM requires service providers that receive personal information to handle it consistently with this policy and provide the same or equivalent protection.

• Google Firebase and Google Cloud: Google account sign-in if selected, authentication, Firestore data storage, Cloud Functions and Tasks, Android push delivery, abuse protection, security, and service reliability. IZEM does not use Firebase Analytics in the release app.
• Google Gemini paid API: relevant profile, chat, selected photo, and plan content for the non-voice AI features you permit. The paid-service and abuse-monitoring terms above apply to this processor.
• Inworld: live audio after answer, selected voice, bounded coaching and session context, generated speech, and content-free usage diagnostics for every live coach call. IZEM connects through its server-managed worker and does not retain a raw call recording.
• RevenueCat and Apple / Google Play: subscription presentation, purchase processing, entitlement validation, restores, and billing management. IZEM does not receive your full payment card number.
• Apple: Sign in with Apple if selected, App Store billing, iOS push/VoIP delivery and call presentation, and the optional on-device HealthKit access you control.
• Twilio: Android voice registration and short call-delivery signaling used to ring the account-and-device-bound app. The substantive AI coaching audio uses the separate AI connection described above.
• Sentry: limited crash and performance diagnostics, configured to avoid message, photo, audio, Health, and direct prompt content.
• YouTube: optional embedded and external exercise or cooking videos. If you choose to play or open one, YouTube may receive network, device, and video-interaction information under Google’s own privacy terms. IZEM uses privacy-enhanced embeds where available and does not use video activity for advertising or cross-app tracking.

8. Why we process information

Where applicable law requires a legal basis, IZEM processes information as needed to perform the service you request and administer membership; with your consent for personal AI processing, local Apple Health access, the separate Apple Health coaching disclosure, camera, microphone, and notifications; for legitimate interests in securing, debugging, and improving a members-only service without advertising or tracking; and as needed to meet legal obligations or protect users, IZEM, and providers. Withdrawing consent stops the future feature that depends on it but does not make prior lawful processing invalid.

9. Retention and deletion

We keep account and coaching records while your account is active or until you remove them through available product controls. Older conversation content may be summarized into a bounded thread summary and the older raw messages may be pruned as part of storage controls. Confirmed workouts, meals, plans, progress, scan analyses, and ordinary coaching records remain until removed through an available control, replaced under the feature’s normal lifecycle, or deleted with the account.

Scrubbed crash diagnostics retained directly by IZEM expire after 30 days. Content-free AI operational telemetry retained directly by IZEM also expires after 30 days. Message-feedback receipts and the corresponding bounded safety/quality record expire after 180 days. Short-lived request locks, idempotency receipts, notification jobs, and session records expire or are deleted under their operational lifecycle. Security, purchase, tax, fraud-prevention, dispute, or legal records may be retained longer only where reasonably necessary or required by law. To prevent deletion-and-recreation from resetting a one-time complimentary call or introductory-trial benefit, IZEM retains the minimum durable benefit tombstone while that anti-abuse purpose remains necessary. On account deletion, the raw Firebase user ID is removed from those tombstones; complimentary-call tombstones retain only the already-pseudonymous claim key and consumption state, and trial tombstones retain the store period key and claimed state.

Account deletion creates a server-side barrier against new account writes, revokes linked Sign in with Apple authorization where applicable, removes IZEM-held account records and server-owned device/call identifiers, and clears account-scoped sensitive local caches. Some deletion work completes asynchronously and is retried if interrupted. If a server-managed voice session already started immediately before deletion, IZEM keeps only the bounded account and call-control records needed to stop and account for that session until its fixed window closes—no more than the current 15-minute member-call limit, and exactly three minutes for an onboarding test call. Cleanup then retries automatically. This delay does not issue or extend a session or copy Health, transcript, photo, or other coaching content into the cleanup record. IZEM rejects any replacement voice session during that interval. Deletion cannot remove information already held temporarily by a provider under its disclosed retention rules, cancel storefront billing, or delete records held by Apple Health.

10. Your choices and privacy rights

You can (a) revoke AI processing in Profile, (b) turn off “Use Health with my coach” without disconnecting the local dashboard, (c) disconnect Apple Health, (d) start a new chat thread, and (e) restore or manage purchases through the storefront. You can delete your IZEM account from Profile. Revocation stops future processing but cannot recall information already within a provider’s disclosed retention period, remove an existing chat reply, or reverse a workout change you confirmed. Deleting an IZEM account does not cancel an App Store or Google Play subscription; manage that separately in the storefront. It also cannot delete Apple Health records.

Depending on where you live, you may have rights to request access, correction, deletion, restriction, portability, or an explanation of personal information we hold; object to certain processing; withdraw consent; appeal a denied request; or complain to your local privacy authority. These rights can have lawful exceptions. Email support@youraicoach.life to make a request. We will verify identity, respond under the law that applies, and will not discriminate against you for exercising a privacy right.

To report an unsafe response, use the message report action or contact support. The public legal and support pages do not include advertising or analytics scripts.

11. Security and international processing

IZEM uses Firebase security rules, App Check, server-side entitlement and consent checks, encrypted device storage for sensitive local tokens, and transport encryption. No online service can promise absolute security. Data may be processed in countries where our providers operate, subject to their safeguards and applicable law.

12. Age limit and policy changes

IZEM is not directed to children. You must be 18 or older to create an account or use its personal AI features. If we learn that an ineligible minor created an account, contact support so we can investigate and remove the account as appropriate.

We may update this policy when the product or law changes. The in-app AI disclosure is versioned; material changes require a new choice before AI processing resumes. The effective date above identifies the current policy.