Gathering your Lyfe
Effective date: October 26, 2026
This policy describes how Lyfe handles information in its iPhone app, Lyfe Web, and related services. Contact support@lyfecoach.app for privacy questions and requests. Lyfe is the public-facing brand; this policy does not identify an unconfirmed legal entity.
Account information includes your email, authentication credentials and sessions, account identifier, display name, date of birth, and wellness preferences. Date of birth determines eligibility and safety restrictions; it is not automatically included in AI context or disclosed to coaches. Digital Lyfe is for people 13 and older; direct human coaching, messaging, training, and video are restricted to adults 18 and older. Please contact support to correct a birth date. We do not knowingly permit accounts for children under 13; contact us if you believe one exists.
Fitness information includes plans, templates, scheduled and completed workouts, exercises, and sets. Nutrition information includes targets, meal entries, ingredients, recipes, and information submitted for food estimation. Mind includes check-ins and private Journal entries. Purpose includes chapters, milestones, tasks, and progress. Lyfe Level, pillar levels, Momentum, and Journey events reflect activity within the product. We use these records to provide the features you request, synchronize your account, and show progress; they are not medical assessments.
If you choose Connect Google Calendar or Connect Microsoft in Planner, Lyfe asks the provider to let Lyfe read the calendars you select. Lyfe uses the provider account identifier, account email, calendar identifiers and your calendar selection to maintain the connection. For your rolling seven-day Planner agenda, Lyfe requests event titles, start and end times, all-day status, and event locations when available. Google event creation is an optional additional permission: after you explicitly enable it, Lyfe can create a new event only in a Google calendar you own and choose. Lyfe does not edit or delete existing provider events or invite guests. Microsoft calendar access remains read-only.
Calendar event details are fetched when Planner loads or refreshes and are returned to your signed-in Lyfe app or website. Lyfe does not save the fetched event records in its database, use them for advertising, or share their contents with coaches. Calendar details are not automatically used for AI. If you explicitly request a Planner AI feature and confirm its one-time disclosure, the selected content is sent to OpenAI for that request only: meeting preparation uses the event title, notes you entered, and up to three matching saved Lyfe meeting notes; schedule suggestions use up to 20 unscheduled task titles, priority levels, due dates and durations; scheduled Lyfe task titles and times; up to 15 calendar event titles and times; your configured work hours; and your timezone. Lyfe does not send attendee email addresses or use Health data for these Planner requests. AI results are reviewable suggestions; Lyfe does not save a task, send a message, or change a calendar event until you confirm the relevant action. When you choose to add a Google event, Lyfe sends the new event title, start and end times, and any location or description you entered to Google Calendar; Lyfe does not store a copy of that provider event. To keep the provider connection working, Lyfe stores OAuth tokens encrypted on its server. Calendar connection records are limited to your Lyfe account and are not available to other members.
You can decline provider access and continue using other Lyfe features. You can disconnect an account in Planner; Lyfe then removes its stored connection and encrypted tokens. You can also revoke Lyfe's access in your Google or Microsoft account settings. A provider may retain records according to its own policies. Google calendar access is subject to Google's API Services User Data Policy and Microsoft access is subject to Microsoft Graph and account terms.
When Gmail sync is available and you choose Connect Gmail in Planner, Lyfe requests read-only Gmail access. Lyfe uses the connected account email and encrypted OAuth tokens to maintain your connection. Your Gmail search runs only when you submit a query; Lyfe retrieves up to 12 matching message subjects, senders, dates and short snippets. The full plain-text content of a message is fetched only after you select that message and request task extraction. Message content is not stored in Lyfe, shown to coaches, or used for advertising. If you confirm the one-time AI disclosure for task extraction, the selected message’s subject, sender, sent date and plain-text content are sent to OpenAI for that request only. Lyfeline returns editable task suggestions; Lyfe saves none until you choose to add a suggestion to your Planner. Lyfe never sends, modifies, archives or deletes email. You can disconnect Gmail in Planner or revoke Lyfe’s access in Google settings; disconnecting removes the encrypted token and connection record. Gmail access is subject to Google’s API Services User Data Policy.
Journal titles and bodies are private to your account by default. They are not automatically included in coach overviews, Ask Lyfe context, coaching escalations, or progression descriptions. Generic activity events can record that an entry was made without its content. This privacy boundary is not a claim of end-to-end encryption: Lyfe’s hosting providers process stored data to operate the service.
Ask Lyfe conversations, requests, action proposals, and limited conversation memory are stored with your account. Coaches do not automatically receive your Ask Lyfe transcript. If you explicitly choose to send a summary to your coach, the summary you approve is shared through the coaching conversation. This feature is available only to adults. Information you deliberately type into a message or summary is included in what you send.
OpenAI powers Ask Lily and requested AI guidance, meal estimates, selected journal analysis, journal-photo transcription, and optional Planner assistance. Planner capture, meeting organization, schedule-priority suggestions, and follow-up drafts send the chosen commitment, due date and project when present, and recipient name, and your timezone only after you request that feature and confirm its one-time disclosure in Planner. Each request sends only its stated text and the bounded context described above; the results are previews you can edit. Planner AI does not send messages or change connected calendars. The iPhone app asks for permission before sending information for these features. Permission is separate from account creation and can be declined while continuing to use non-AI Lyfe features. You can review or withdraw the choice in Settings → Privacy & safety. The accepted provider, disclosure version, choice and date are stored securely in the device Keychain for your Lyfe account. A changed disclosure requires renewed permission. Withdrawing permission stops new requests; it does not recall data already processed or automatically delete saved conversations.
Depending on the feature and question, OpenAI requests may include your message, bounded conversation history and compact conversation memory; age eligibility; time/timezone; wellness preferences and onboarding priorities, goals and challenges; relevant workout schedules, completion history, logged weights/reps, equipment and travel preferences; food entries, nutrition targets, saved recipe/ingredient details and adult height, weight, sex at birth and activity level for nutrition guidance; mood check-ins; Purpose goals, steps and progress; coaching schedules and assignments; and approved personal observations or selected journal-derived insights. Coach message bodies and exact birth dates are not automatic AI context. Information you deliberately type into a message or submit in a photo is included in that submission.
Food descriptions, food photos and clarification answers are sent when you request meal estimation. Selected journal writing or journal photos are sent only for the feature you choose, with existing entry-specific controls in addition to AI permission. Current meal-photo and journal-photo processing does not save those uploaded images in a Lyfe storage bucket. AI output may be inaccurate and is general wellness support, not medical diagnosis, treatment or emergency care.
Lyfe's reviewed OpenAI Responses API calls set store: false. This controls response storage and does not promise zero provider retention. OpenAI's API handling is governed by its applicable services agreement and data-processing terms, including security and confidentiality protections. See https://openai.com/policies/services-agreement/ and https://developers.openai.com/api/docs/guides/your-data for provider terms and data controls. No zero-retention guarantee is made.
Apple Health connects through the iPhone/iPad app's read-only HealthKit integration. Apple's system authorization controls which data types Lyfe can read; Lyfe cannot determine which individual read permissions were declined. Requested types are steps, active energy, workouts, sleep, resting heart rate and VO₂ max. Lyfe does not write to Apple Health and does not request clinical records. Recent normalized summaries and workout imports, including provenance/deduplication source information, sync to your private Lyfe account in Supabase for activity, nutrition-energy estimates and wellness features. Web does not connect directly to HealthKit.
Apple Health authorization is not permission to send Health information to OpenAI. The separate “Personalize Lyfe with your health data” disclosure appears in the Connect Apple Health flow and can also be reviewed from Apple Health settings. Only after express permission and authorized data being available may relevant, compact summaries be shared with OpenAI to provide personalized wellness/fitness responses and explore possible connections across lifestyle areas. The verified automatic context is up to three recent daily summaries from the last seven days—steps, active energy, sleep duration/stages, resting heart rate and VO₂ max when available—and up to three recent workouts' type, date and duration. Context is included for relevant questions and kept within the request's byte budget. Raw samples, device identifiers, clinical records and full Health history are not sent as automatic context.
You can decline Health-to-OpenAI sharing and still use Apple Health inside Lyfe's non-AI features. You can withdraw this choice in Settings → Privacy & safety or Apple Health. Your coach does not receive these Health metrics. Disconnecting stops syncing and removes Lyfe's stored Health summaries/imports when server cleanup succeeds; it does not delete Apple Health records, earned Lyfe levels or existing conversations. Offline cleanup may remain pending until reconnection. Change read permissions in the Health app → profile → Apps → Lyfe.
For connected adult clients, authorized coaches can access the limited overview, assignments, sessions, goals shared for coach discovery, and messages needed to provide coaching. The overview contains selected fitness, nutrition-activity, check-in, and Purpose facts; it is not unrestricted access to your account. Private Journal and Health summaries are excluded. Shared messages and approved escalations are visible to participants while access is authorized.
Training bookings store participant identifiers, times, duration, booking state, and payment/refund information. Daily provides private live-video rooms and receives session identifiers, participant identifiers/display labels, and audio/video necessary for the call. The current integration does not enable session recording. Provider operational metadata may still be processed. Room access requires server authorization and time-limited tokens.
Apple handles App Store payment details. Lyfe stores verified subscription identifiers, account ownership, product, environment, expiry, and status to determine access and prevent a purchase being assigned to another account. AWS infrastructure supports Apple transaction verification and server notifications.
Stripe handles web membership and Lyfe-paid training payment details. Lyfe stores customer/subscription or payment/refund identifiers, price, amount, currency, billing environment, and status. Card details are submitted to Stripe rather than stored in Lyfe’s application database. A checkout return page does not itself grant membership; access is verified on the server. Authorized test billing is separated from live billing. Manual access grants are separately authorized server records, not fabricated purchases.
If you choose notifications, Lyfe stores installation identifiers, APNs tokens, environment, preferences, and delivery-job information. Coaching notifications use generic lock-screen copy rather than message text or sensitive wellness details. Personal reminders are opt-in. Sign-out deactivates the account’s device association.
Support communications are received at support@lyfecoach.app through Cloudflare Email Routing and forwarded to an owner-managed Gmail inbox. Your email address, message, and attachments are processed to respond. Avoid sending passwords, full payment details, or unnecessary health information. Technical providers may process network information, request metadata, error and security logs to deliver and protect the service. Authentication uses necessary session cookies on web and secure session storage on iPhone. If you open a creator referral link, Lyfe uses a necessary first-party, HttpOnly cookie for up to 30 days to carry that referral to account creation. You may also enter a creator code yourself. Affiliate click and attribution records do not contain IP addresses, device fingerprints, or wellness information. A referral is attached only to a newly created account after the code and eligibility are checked; you can continue creating your account without a referral.
The current architecture uses Supabase for authentication, database and backend services; Vercel for web hosting; Google Calendar and Microsoft Graph for optional calendars you connect; OpenAI for requested AI processing; Apple for StoreKit, HealthKit and push delivery; Stripe for payments; Daily for live video; AWS for Apple verification and password recovery infrastructure; Resend for authentication email delivery; and Cloudflare and Google Gmail for support-email routing and receipt. Providers process information needed for their roles under their own applicable terms and policies. Data may be processed in the United States and other locations used by these providers.
We do not sell your wellness or Health data, and the reviewed implementation does not use it for targeted advertising. We may disclose necessary information to comply with law, respond to lawful requests, prevent fraud or abuse, protect people or systems, or support a business transfer subject to applicable protections. This does not grant coaches general access to private records.
Personal records remain available to provide your account’s features until deleted through available controls or account deletion, subject to operational and legal needs. Successful Health sync prunes summaries/imports older than 30 days; inactive accounts may retain their last records until cleanup or deletion. No fixed universal retention period is promised for provider logs, backups, support messages, or required financial records.
Both clients use the same authenticated account-deletion service. It marks the account for deletion, deactivates push associations and jobs, handles linked Stripe subscription cancellation and session cleanup, and removes the Auth account and dependent personal records. Provider failures can leave deletion pending for retry. The service retains limited detached payment/refund and transaction-ownership records for reconciliation, disputes, fraud prevention, and legal obligations, rather than retaining copied wellness or message content for those purposes. Provider backups and operational logs are not necessarily erased immediately.
Deleting Lyfe does not automatically cancel an Apple subscription; manage it through Apple. Linked Stripe web subscriptions are cancelled before final account deletion. Deleting Lyfe does not delete data held independently in Apple Health or your Apple, Stripe, Google, or other provider accounts.
You can update supported profile fields, manage notification preferences, disconnect Health, control Health-to-AI sharing, delete supported content, and request account deletion in Settings. Contact support@lyfecoach.app for access, correction, deletion, or other privacy requests. We may need to verify account ownership. Depending on applicable law, you may have additional rights regarding your information; we will handle requests under that law and will not require a new purchase to submit one. Do not send a password to prove identity.
Lyfe uses account authentication, server authorization, row-level access controls, and protected service credentials. No online service can guarantee perfect security. We may update this policy as the product changes and provide notice where required. The effective date identifies this version.
If you request student pricing, we send the name you enter and your student-ID image to OpenAI for automated image screening, with your consent. You may cover your photo, student number, barcode, address and birth date; keep your name, school and any expiration date visible. We do not perform facial recognition or confirm enrollment with your school. The check can make mistakes; contact support@lyfecoach.app for help. Lyfe does not save the submitted image or name from this check. We retain the eligibility result, approval dates and attempt counts on your account to administer the discount and limit abuse. OpenAI API abuse-monitoring retention may apply for up to 30 days; we request no stored model response. Stripe retains the subscription and discount records needed for billing. Existing account deletion and privacy request options apply.