LifeHub HQ — Privacy Policy

LifeHub may collect the following information when you use the app:

• Account information — such as your email address and profile information used to create and manage your account.
• Calendar and schedule data — events, schedules, event details and availability needed to provide scheduling functionality.
• Connected account tokens — authentication tokens for services you choose to connect, such as Google, Apple, Microsoft, health providers or financial providers.
• Information from services you connect — for example email, calendar, task, financial obligation, pharmacy or health information you authorize LifeHub to read.
• Usage data — basic diagnostic information used to improve app performance and reliability.
• Subscription data — your purchasing platform, customer and subscription identifiers, payment status, renewal period and plan. LifeHub does not receive or store your full card number.
• User content — notes, tasks, files, preferences and any other information you choose to add inside the app.

Your information is used only to:

• Provide scheduling, inbox, task, financial-obligation, file and health-information features you enable.
• Keep connected accounts in sync.
• Maintain your account, preferences and subscription access.
• Improve app performance and reliability.
• Provide customer support.
• Protect the security and integrity of the platform.

LifeHub does not sell your personal data.

When you connect a third-party service — such as Google, Apple, Microsoft, a health provider or a financial provider — LifeHub only accesses the data needed to provide the features you enabled. We do not access unrelated information from your connected accounts.

You can disconnect any integration at any time inside LifeHub, and you can also revoke LifeHub's access directly from the provider's own account settings.

LifeHub uses Apple HealthKit's Clinical Health Records API only after a user opens the Health Records screen, chooses to connect Apple Health, and authorizes record categories in Apple's permission sheet. The integration is read-only: LifeHub never writes to Apple Health and does not use CareKit.

When the user starts an import, LifeHub reads the authorized clinical records available on that device and sends them through an authenticated connection to the user's private LifeHub account. The first import requests available records; later user-started imports request records since the last successful sync. LifeHub does not read or upload HealthKit records in the background.

Imported labs, medications, allergies, conditions, immunizations, procedures and related source data are stored in LifeHub's Supabase database and protected by account authentication and row-level access controls. They are shown in the user's private medical views. A connected AI app cannot read medical data unless the user separately enables its Read medical data permission in Settings; that permission starts off.

Tavena is LifeHub's assistant. Many LifeHub features are ordinary computation and involve no AI at all. When you use an AI-powered feature, the content needed for that request may be sent to a third-party AI provider for processing and a response.

Paid AI access is provider-neutral: LifeHub may use more than one AI provider, and the provider used for a given feature can change over time. AI providers process the content they receive to return a result; they are not given your connected-account credentials or authentication tokens.

AI output can be incomplete or incorrect and is meant to help you decide, not to decide for you. Consequential actions are prepared for your review rather than performed silently.

Mobile phone numbers, SMS consent and opt-in data are used only to provide the text-message features a user enables. Mobile information and SMS consent will not be shared with third parties or affiliates for marketing or promotional purposes. Service providers that help deliver messages may process this information only to provide that service.

All the above categories exclude text messaging originator opt-in data and consent; this information won’t be shared with any third parties.

We do not share your personal information with third parties except:

• When necessary to operate core app functionality — for example the providers you connect, our hosting and database infrastructure, Apple or Stripe for subscription purchases, and AI providers for AI features you use.
• To comply with legal obligations.
• To protect the security and integrity of the service.

Your information is retained only as long as necessary to provide the service and maintain your account. You may request deletion of your account and associated data at any time, and LifeHub also includes an in-app account deletion option.

Limited records may be retained where required to meet a legal, security or accounting obligation.

If you connect your own Google Drive, files you choose to save there remain in that account under its settings. LifeHub may keep file names and links to show them in your library. Files you choose to host in LifeHub use the app's private storage and count against the paid plan's storage limits. LifeHub does not automatically substitute its own storage when a Drive save fails.

We use reasonable technical and organizational safeguards to help protect information and connected-account credentials, including access controls that restrict credential access. No online service can promise absolute security.

You may:

• Disconnect any integration at any time.
• Delete data you added inside the app.
• Request deletion of your account and associated data.
• Choose not to use AI-powered features.
• Stop using the service at any time.

LifeHub is an organizational and decision-support tool. It does not provide medical, legal, financial, tax or investment advice, and it does not autonomously move money.

If you have questions about this Privacy Policy or your data, contact support@watsongrowthpartners.com.