Last updated: October 2, 2026
Tempo is provided by Judge Dean LLC. This policy explains how Tempo handles information you provide. Features vary by app version and service availability. The AI Companion, account, and backup sections below describe the updated Tempo app; older chat features are covered under Earlier versions.
Profile information, episode logs, journals, daily check-ins, experiments, appointment questions, and conversation history save in app storage on your device. Tracking works without an account. Fonts are bundled and do not require a Google Fonts network request.
Local records use platform app storage protection. The app has not implemented a separate encrypted database or app lock. Starting with the updated iOS release, Tempo marks its local health-record storage for exclusion from device backups before opening records. This does not remove copies created by earlier versions or reports you have shared elsewhere.
Before sending a message, Tempo asks permission to share that message, recent conversation, and limited profile context (name, AFib type, treatment, and suspected triggers) through the Tempo service to Anthropic to generate a reply. Episode logs and journals are not automatically attached. Information you type into a conversation is included in that conversation.
Companion is AI, not a clinician or live support team. Conversations are not monitored by an emergency team. For an emergency, contact your local emergency service immediately.
The service uses Firebase authentication, Cloudflare hosting, and Anthropic processing. It stores generated replies and request IDs under your service account identifier to make retries reliable. These active records expire at midnight UTC and are removed by scheduled cleanup. Cloudflare's database recovery system can retain earlier copies for up to 30 days; expiry of an active record does not immediately erase those copies.
To limit abuse and enforce reply limits, the service uses an authenticated account identifier and a short-lived hash of your network IP address. The IP-based rate-limit counter expires after an hour; account reply counters expire at the end of the UTC day.
Anthropic normally deletes API inputs and outputs within 30 days. Longer retention may apply for safety investigations, legal requirements, or other exceptions described in Anthropic's retention policy. Service providers may also retain network and security records under their policies. Deleting local conversation history or withdrawing consent does not erase provider copies already retained.
We use information to provide the features you choose: storing and displaying records, generating Companion replies, handling account access and requested backups, verifying subscription access, and protecting the service against abuse. We do not sell your personal health data or use it for advertising.
Creating an email/password account is optional. Firebase processes account credentials. The app stores its refresh session using platform secure storage; it does not save your password as a preference.
Cloud backups upload only when you tap Back up now. A backup contains your profile, episodes, journals/check-ins, and experiments. It excludes conversation history and appointment questions. A new backup replaces the previous snapshot for your account. Signed-in users can restore, delete their cloud snapshot, or delete their cloud account in Account & backup.
The current cloud snapshot remains until you replace or delete it. Deleting your cloud account first deletes that snapshot and then requests deletion of the Firebase account. Firebase states that authentication IP logs are kept for a few weeks and other authentication information is removed from its live and backup systems within 180 days after account deletion. Provider backup and recovery copies may outlast deletion from the active service. See Firebase's privacy information.
Apple processes purchases. Tempo and its service verify subscription status and signed transaction data to establish current access. The app does not collect your payment card details.
PDF reports are generated on your device and previewed before you choose to share them. Sharing sends the report to the destination you select; that destination's privacy practices apply.
Daily check-in reminders are off by default. If you enable them, Tempo asks for notification permission and schedules reminders on your device. Reminder content includes no health record details. Your preferred time and quiet hours are stored locally. You can turn reminders off in Gentle reminders or manage permission in your device settings.
Product analytics is disabled in this update. No product analytics events are sent by the updated app. Any future optional analytics feature will ask for your consent before activation.
Earlier versions with Crisp chat process messages and limited profile context through Crisp, which may retain conversation data on its servers. See Crisp's privacy policy. Earlier versions may also load fonts through Google Fonts; see Google's privacy policy. The updated app uses AI Companion instead of Crisp and bundles its fonts.
For requests concerning an earlier chat conversation, contact the support email below. Removing local app data does not itself delete copies held by a chat provider.
Tempo is intended for adults aged 18 and over. We do not knowingly collect personal information from children. If you believe a child has provided information through a Tempo service, contact us.
We may update this policy as Tempo changes. The date at the top identifies the latest revision.
Tempo is not a medical device and does not provide medical advice. Records are self-reported. Missing logs are unknown, and observed patterns do not establish causes. Discuss medical decisions with your healthcare provider.
For privacy questions or requests about service-held information, contact judgedeanllc@gmail.com.