Privacy Policy

What may stay local

• Daily logs, journal notes, medication setup and dose logs, rescue use, asthma event history, monthly check-ins, peak flow, pulse ox, app settings, and local insight summaries may be stored on your device/browser under the signed-in account profile.
• If more than one person uses the same phone, tablet, or browser, each person should use their own sign-in. Local data is kept under the signed-in account profile on that device.
• Environment snapshots, imported QA/restore data, local trigger-pattern summaries, sync queue state, and downloaded export files may also remain local unless a supported sync or cloud feature uses them.
• Older data created before sign-in was required is not automatically added to your account. My Asthma Life does not silently merge, upload, delete, or overwrite old local/device data.
• Exported CSV or report files are controlled by you after download or sharing. They can contain sensitive health information, so store and share them carefully.

What may leave your device

• Account and sync: when you sign in and enable eligible cloud-backed sync, supported records may be sent to Supabase for authentication, database storage, restore, sync, reminder infrastructure, and account support. Cloud backup/sync should be treated as active only when the app says it is enabled.
• Authentication: email sign-in uses Supabase auth. Google Sign-In and Apple Sign-In may be available when configured for the current build/platform, and those providers handle their own sign-in flow.
• Reminders: web/PWA background reminders may store reminder rules and a browser push subscription in Supabase. Browser/device notification permission and push delivery are handled by the browser/platform.
• Environment: ZIP/postal code or derived coordinates may be used to request AQI/weather from Open-Meteo. Trusted shared AQI/weather reference rows may be read from Supabase and cached locally. Premium pollen details, when available, are requested through a Supabase function that calls Google Pollen.
• Billing: web Premium checkout and billing portal flows go through Stripe. Native Android purchases are inactive for the current PWA/web launch. Billing providers process payment details separately from asthma tracking data.
• Ads: mobile builds may include banner ads through Google Mobile Ads / AdMob where that integration is active. Premium and Care Access hide the current mobile banner ad surface while access is active.
• Product telemetry: builds configured for optional product telemetry may send aggregate app usage and reliability counters to help improve My Asthma Life. These counters are event-name and bucket based, and are intended to exclude health journal content, notes, medication details, personal identifiers, session identifiers, device identifiers, raw URLs, and tokens.
• Crash reports: builds configured for crash reporting may send privacy-filtered technical error reports to Sentry. These reports are intended to exclude asthma journal payloads, user notes, medication details, account identifiers, request bodies, screenshots, session replay, and view hierarchy data.
• Support: if you email support, your email address and the details you choose to include are processed so we can respond. Please do not send passwords, card numbers, or unnecessary health details.

Service providers and processors

• Supabase for authentication, database, backend functions, sync, reminder rules, push subscription records, entitlement state, and support operations.
• Stripe for public web subscription checkout, billing portal, payment processing, invoices, and billing records.
• Google for Google Sign-In where enabled, Google Pollen provider data for Premium environmental details where available, and Google Mobile Ads / AdMob on mobile where active.
• Apple for Apple Sign-In where enabled and configured on the current platform.
• Open-Meteo for AQI/weather and location-based environment lookups.
• Sentry for privacy-filtered crash/error reporting in builds where crash reporting is configured.

Deletion and retention

• Deleting local device data removes data from that device/browser for the relevant signed-in local profile, but it may not delete cloud/account data, billing records, or copies on another device.
• Deleting cloud/account data is handled through the app where supported or by contacting support. It is separate from canceling billing.
• The in-app account-data deletion control clears local account/sync data on the initiating device, cancels local notifications, attempts supported cloud cleanup for the current user, records a deletion marker to prevent stale synced data from coming back, and signs out. It does not delete the Supabase auth user or Stripe billing records.
• Canceling a Stripe subscription does not delete app data. Deleting app data does not cancel Stripe billing.
• Some limited records may be retained or anonymized where needed for billing, fraud prevention, security, legal, tax, audit, dispute, or operational purposes.
• We aim to review and process account/data deletion requests within 30 days. Third-party processors may keep records under their own policies.

Your choices

You can use core Free Local tracking after sign-in without public checkout. If you use account-based sync, you can review account/data controls in the app or request account or cloud-data deletion through support. Billing cancellation is handled separately through Manage Billing in the app for Stripe-backed Premium subscriptions. See Account/Data Deletion.

For privacy questions, contact support@myasthmalife.com.

For plan details, see Pricing. For billing, account, Cloud Backup & Sync, or Care Access help, see Support.