Privacy Policy
Pali™ by Total Life Dynamics
Total Life Dynamics, Inc. · 4903 Bayard Blvd Bethesda, MD · totallifedynamics.com
Effective date: October 11, 2026 · Last updated: October 11, 2026
Total Life Dynamics, Inc. ("Total Life Dynamics," "we," "us") operates Pali™, an iOS application that helps people see their own physiological signals in plain language and reduce the daily burden of self-monitoring. This Privacy Policy explains what information Pali collects, how we use and protect it, and the choices you have. Pali is a general wellness product. It is not a medical device, does not provide medical advice or diagnosis, and does not replace your healthcare providers or your continuous glucose monitor's (CGM) own alerts.
1. Information we collect
We collect only the information needed to provide the service:
- Account information you provide, such as your name and email address when you sign in with Apple.
- Information you log in the app, such as meals, hydration, mood, activity, or notes.
- Ask Pali™ messages you send and Pali's replies, stored on your device so you can resume conversations across launches.
- Limited technical and diagnostic data needed to operate and secure the app (for example, crash and performance diagnostics).
- Optional Ask Pali helpfulness ratings you choose to submit (helpful or not helpful), and any optional note you attach to a rating.
- Product analytics about how you use the app, when you have agreed to them, as described under "Product analytics" below.
- If you turn on the weekly email, the weekly summary content described under "Weekly email" below.
- If you ask to hear from us by email (for example, to be notified about Pali), your name, your email address, and any optional details you choose to share.
Glucose data
Pali can connect to glucose data in three ways you choose in Settings → Connections (or during onboarding): (1) your Nightscout site — an open-source platform you set up and control; (2) Dexcom Share, using the email and password for a Dexcom Share account that can see the CGM readings; or (3) Libre Link Up, using the email and password for a Libre Link Up follower account that has been shared a sensor. Only one of these live sources is active at a time. There is no Apple Health glucose connection in onboarding or in Settings → Connections, and Apple Health cannot be used in place of a live source. When you connect Nightscout, you provide the site URL and, if required, an access token. When you connect Dexcom Share or Libre Link Up, you must be signed in with Apple; Pali sends those credentials to our servers only to authenticate with Dexcom or Abbott on your behalf and retrieve glucose readings.
Glucose readings already in Apple Health. If you have granted Pali access to Apple Health and have not connected a live glucose source, Pali may read glucose samples already stored in Apple Health to show glucose history on the Trends screen. These readings are not a connected glucose source: they do not drive your Home screen, Live Activity, or the live adaptive baseline. Trends may still show and classify that history. Values from this history may be included in the scoped context Pali sends when you use Ask Pali or generate insights, as described below. You can revoke Health access at any time in the Health app or iOS Settings.
- Manufacturer follower accounts (optional). Pali is not affiliated with Dexcom or Abbott and is not a partner integration. When you choose Dexcom Share or Libre Link Up, you enter Share / Link Up account credentials so Pali can read glucose as that follower. Medtronic CareLink is not offered. Official Dexcom partner OAuth is not used.
- You control the source. You can disconnect Nightscout, Dexcom Share, or Libre Link Up at any time in Settings → Connections. Disconnecting deletes the encrypted server-side session for that source when you are signed in.
- What we retrieve: glucose values in mg/dL, timestamps, and trend when the source provides them. Pali does not write data back to Nightscout, Dexcom, or Abbott.
- What we store on your device: recent glucose readings and related display state. Nightscout URL and access token stay in the device Keychain. Dexcom Share and Libre Link Up passwords are not stored on the device after you submit the form.
- What we store in the cloud when you are signed in: an encrypted copy of the connection session so background refresh and Live Activity updates can continue. For Dexcom Share, that session retains the Share password (encrypted with AWS KMS) because Share sessions expire quickly. For Libre Link Up, the session retains a long-lived JWT only — not your password after the first successful login. We do not store a separate copy of your full glucose history in the cloud for this feature.
Heart rate variability and activity data (via Apple Health)
With your permission, Pali reads heart rate variability (HRV), heart rate, sleep, activity, and related metrics from Apple Health, including data collected by your Apple Watch. Pali requests only the Health categories it uses, and you can review or revoke this access at any time in the Health app or iOS Settings. Apple Health data is governed by Apple's own privacy protections. Pali processes HealthKit data on your device to generate wellness views and insights. We do not upload raw HealthKit sample streams to our servers or store a copy of your Health history in the cloud. Limited values derived from that data may leave your device in three situations: when you use Ask Pali™ or generate insights, as described below; as small status indicators — for example, whether your personal baseline has been established, or the current wellness label shown on your Lock Screen — which our servers use to deliver those features; and, if you have agreed to product analytics, as the plain-language wellness label recorded with certain product analytics events.
What Pali writes back. With your permission, Pali can save completed recovery sessions to Apple Health — mindful minutes from Breathe easy, and walking workouts from Take a walk. Pali writes only sessions you complete in the app. You can revoke write access at any time in the Health app or iOS Settings.
Cycle data (via Apple Health)
With your permission, and only when Cycle Intelligence™ is enabled, Pali can read menstrual flow entries from Apple Health to show cycle information alongside your other signals. This processing happens on your device. You can turn Cycle Intelligence™ off at any time in Pali's settings, or revoke Health access in the Health app or iOS Settings. Cycle information in Pali is observational and is not intended for contraception, fertility planning, or detecting or monitoring pregnancy.
Voice input
With your permission, Pali can turn speech into text for logging a meal or a drink and for writing an Ask Pali™ message. Speech recognition runs on your device when the device supports on-device recognition. Listening stops after a few seconds of silence. Pali does not save the audio. If recognition creates a temporary audio file, Pali deletes it immediately.
If this device cannot recognize speech on the device, that request may use Apple's speech recognition service. Apple then processes the audio under Apple's privacy policy. Pali still does not receive or store the recording, and Pali does not upload voice recordings to our servers.
The text that results is handled like text you type. If you send a dictated Ask Pali™ message, that message text — not the audio — is sent to our cloud AI provider only to generate the reply, as described under Ask Pali™. Product analytics do not include voice recordings or speech transcripts.
Ask Pali™
When you use Ask Pali™, your messages and recent conversation context are sent to our cloud AI provider only to generate that reply for the request. Pali stores your Ask Pali conversation history on your device (not as a separate chat archive on our servers). Pali also includes scoped context in that request so the reply can be grounded in your own data. Depending on what you have connected, what Health access you have granted, and what you ask, this may include recent numeric values derived from your health data — such as a heart-rate-variability reading in milliseconds, your personal baseline range, or a recent glucose value — along with how fresh those readings are and the plain-language wellness labels Pali has assigned. If you ask about how you feel, this can also include entries you logged in Pali in the last 24 hours — mood, symptoms, a short note, and, when Cycle Intelligence™ is on, the flow level you logged. This context is used only to generate your reply for that turn. It is not sold, not used for advertising, and not used to train third-party models.
If you optionally rate whether an Ask Pali reply was helpful, we store that rating together with a message identifier, conversation identifier, timestamp, and platform. If you choose to add an optional note with your rating, we store that note with the rating. We do not store the text of your question or Pali's reply with that feedback. We use this feedback to improve Pali's responses and reliability. This feedback is not sold and is not used to train third-party models.
Spoken replies
When you use Ask Pali™ after saying "Hey Pali" or dictating a question, Pali may read the reply aloud with an AI-generated voice. This is not a live person. You can stop a spoken reply at any time. To generate that voice, Pali sends the same reply text you see on screen, which may include your first name, to a third-party speech provider (ElevenLabs) solely to create that audio for your request. We do not send continuous glucose monitor (CGM) data, heart-rate or HRV readings, or other biometric streams to that provider — only the guard-approved reply text shown in the chat. We do not send reply text to the speech provider when you type a question or tap a suggestion chip (those replies are not read with the neural voice). ElevenLabs processes and may retain that request data under its own terms and privacy policy. Pali does not keep provider audio as a lasting archive after playback, other than a short-lived on-device cache so you can replay that reply. Crisis-support audio is stored in the app and is not sent to the speech provider.
Product analytics
When you have agreed to product analytics, Pali records a limited set of events describing how you use the app, so we can understand which parts of Pali are useful, find problems, and improve the product.
- What an event records. Each event is a small record containing the type of event, the date and time it happened, and basic app and device context such as the app version and platform. For events about the wellness state Pali is showing you, the event also records the plain-language state label displayed at that moment — for example, Balanced, Shifting, Unbalanced, or Establishing Baseline — and, for a change of state, the label before and after.
- Which events we record. Opening the app, sending the app to the background, viewing your current state, a change in the state Pali displays, and manually refreshing your data.
- What an event does not contain. Product analytics events do not contain your glucose values, your heart-rate-variability or heart-rate values, your personal baseline range, your Nightscout address or token, your logs, your notes, your Ask Pali messages, your voice recordings, or your speech transcripts.
- How events are identified. When an event reaches our servers, our servers attach your account identifier and a record of the consent that was in effect. The app does not send these; they are added on receipt. This means product analytics events are linked to your account.
- How events are stored. Product analytics events are written to a separate store that the Pali app cannot read back. There is no feature in Pali that retrieves or displays your analytics events, and Pali's wellness experience is not driven by them.
- Your choice. Product analytics are collected only under the consent you give. You can review and change your choice at any time in Pali's settings. Turning product analytics off stops the collection of new events.
Product analytics are used by Total Life Dynamics to operate and improve Pali. They are not sold, not shared with advertisers, and not used to train third-party models. We do not track you across other companies' apps or websites.
Weekly email
Pali can send you an optional weekly email that summarizes your week. It is off by default, and you choose whether to turn it on in Pali's settings.
- What it contains. The date range for the week; a short, plain-language summary of your patterns for the week; wins you logged in Pali that week; progress on the My Focus areas you chose; and the plain-language wellness label for your glucose and for your rest and recovery (for example, Balanced or Shifting). It does not contain glucose values, heart-rate-variability or heart-rate readings, or other raw health data.
- How it is made. Pali prepares the weekly summary on your device and sends only the finished content listed above to our servers. Writing the patterns summary works the same way as when you ask Pali to show your patterns in the app: Pali sends scoped context to our cloud AI provider, as described under Ask Pali™, and that context is used only to write your summary.
- Who receives it. We store your most recent weekly summary on our servers and send it, with your name and email address, to our email service provider, MailerLite, which stores it on your subscriber record in order to deliver the email. Each week's content replaces the previous week's.
- Email is not a private channel. Once delivered, the email can be read by anyone with access to your inbox. Turn the weekly email off if you do not want this summary in your email.
- Turning it off. You can turn the weekly email off at any time in Pali's settings or with the unsubscribe link in any weekly email. When you do, we stop sending it and delete your weekly summary content from our servers and from your MailerLite subscriber record.
Weekly email content is not sold, not used for advertising, and not used to train third-party models.
We do not collect more health data than is necessary to deliver Pali's features.
2. How Pali connects to your data
Pali is built on a simple principle: you bring your own data, and you stay in control of it.
- Optional manufacturer follower accounts. In addition to Nightscout, you may connect Dexcom Share or Libre Link Up using credentials you type. Those credentials are sent to Total Life Dynamics servers to authenticate with Dexcom or Abbott on your behalf. There is no OAuth partner sign-in to Dexcom inside Pali, and no manufacturer receives information from Pali about you beyond what their own Share / Link Up APIs require for the login you initiate.
- Read-only access. Pali reads glucose; it does not modify your Nightscout settings, Dexcom account, or Libre Link Up account, and it does not post treatment or alert data back.
- How fetches work. Nightscout is usually read on your device (with an optional encrypted tunnel through our API gateway). Dexcom Share and Libre Link Up readings are retrieved by our servers using your encrypted session, then delivered to the app and, when enabled, to Live Activity push updates.
- Disconnection. Disconnecting a glucose source in Settings → Connections stops new retrieval and deletes that encrypted registration from our servers when you are signed in. Previously retrieved glucose readings may remain in the app until you delete the app or clear its data.
- Signing out. Signing out of Pali clears your app session tokens from the device Keychain. It does not by itself remove Nightscout credentials or glucose history stored locally on the device.
3. How we use your information
- To generate Pali's wellness views, including your overall state and the plain-language summaries Pali surfaces.
- To operate, secure, maintain, and improve the service.
- To understand how Pali is used and to improve its features and reliability, using the product analytics described above and the diagnostic data Pali collects.
- Where you direct it, to generate a standards-based (FHIR) summary for a healthcare team recipient you choose.
We do not sell your personal or health information, share it with advertisers, or use it to train third parties' models.
4. How we share information
We share information only in limited circumstances:
- With service providers that process data on our behalf under contract, including cloud infrastructure and AI model providers engaged under appropriate data-protection terms (for example, when you send a message to Ask Pali, or when a dictated reply is read aloud with the neural voice), and our email service provider (MailerLite) when you turn on the weekly email or ask to hear from us by email.
- With healthcare team recipients that you specifically authorize and direct.
- When required by law, or to protect the safety of a user or the public.
- In connection with a corporate transaction, subject to the protections in this policy.
5. Data security
We protect your information using administrative, technical, and physical safeguards. Data is encrypted in transit (TLS). Nightscout access tokens on your device are stored in the iOS Keychain. When you are signed in, encrypted Nightscout connection credentials are stored server-side; they are not embedded in the app binary. Product analytics events are written to a store that the app has no ability to read, query, or modify. Access to data within Total Life Dynamics is limited to what is necessary to operate the service.
6. Data retention and deletion
We retain your information only for as long as needed to provide the service or as required by law, then delete or de-identify it.
You can disconnect Nightscout, Dexcom Share, or Libre Link Up, or revoke HealthKit access, at any time. Disconnecting a live glucose source removes that encrypted server-side session when you are signed in and stops new retrieval from that source. Revoking Health access stops new Apple Health glucose reads. Glucose history already stored on the device, including history read from Apple Health, may remain until you remove it or delete the app. Locally stored Nightscout credentials may persist on your device until you remove them or delete the app. Dexcom Share and Libre Link Up passwords are not kept on the device after you submit the form.
When you close your account or request deletion, we stop retrieving new data and delete the personal data associated with your account from our systems, including your Nightscout, Dexcom Share, and Libre Link Up registrations, your push and session records, your product analytics events, and any weekly email content held by us or by our email service provider, on the schedule described in our internal Record Retention Policy. Data stored only on your device is removed when you delete the app. Deleting your account does not cancel an App Store subscription; manage billing in Settings → Apple Account → Subscriptions.
7. Your choices and rights
- Connect or disconnect Nightscout, Dexcom Share, or Libre Link Up, and Apple Health, at any time.
- Deny Microphone or Speech Recognition access in iOS Settings. Pali cannot dictate without that access; you can still type.
- Enable or disable Cycle Intelligence™ at any time in Pali's settings.
- Turn product analytics on or off at any time in Pali's settings.
- Turn the weekly email on or off at any time in Pali's settings, or unsubscribe from any weekly email.
- Unsubscribe from any other email from us using the link in that email.
- Change or revoke your Nightscout access token on your own Nightscout site.
- Request access to, correction of, or deletion of your personal information.
- Close your account, which triggers cloud deletion as described above.
To exercise any of these, contact us using the details below.
8. Age and children's privacy
Pali is intended for adults. You must be at least 18 years old to create an account or use Pali. Pali is not directed to children, and we do not knowingly collect personal information from anyone under 18. If we learn that we have collected information from a person under 18, we will delete it.
9. Changes to this policy
We may update this policy from time to time. We will post the updated version with a new effective date and, where appropriate, notify you in the app.
10. Contact us
Andy Tiedeman
Privacy Officer, Total Life Dynamics, Inc.
Email: andy@totallifedynamics.com · Address: 4903 Bayard Blvd Bethesda, MD, USA