PostureSense
Menu

Privacy Policy

PostureSense Privacy Policy

This policy explains what PostureSense collects, how the app uses AirPods motion-based posture data, and how to contact us about your account or data.

Effective date: October 23, 2026

contact.posturesense@gmail.com

Overview

Posture awareness, not advertising

PostureSense provides posture awareness and habit tracking on supported iOS and macOS devices. The initial Android companion beta provides account access and synced history; it does not record posture sessions, provide live alerts, or support Galaxy Buds monitoring. We use information to provide account access, AirPods motion-based posture sessions, history, goals, settings, reminders, and support. We do not sell personal information, and we do not use personal information for third-party advertising or cross-app tracking.

PostureSense is not a medical device and does not diagnose, treat, cure, or prevent any medical condition.

Information we collect

Data used by the app

  • Account information (when you sign in): email address, authentication provider, account identifier, language, timezone, account status, and secure authentication tokens.
  • Posture session information: session start and end times, posture score, posture event type, event timestamp, and motion-derived angle values saved with your account history.
  • Summaries, goals, and settings: daily and monthly posture summaries, measurement duration, pose counts and durations, goals, streak-related progress, alert timing, sensitivity, and alert delivery preferences.
  • Device and permission information: AirPods motion availability, local notification permission state, and a notification token if server-side notifications are configured for your account.
  • Operational error diagnostics: production releases automatically send sanitized Dart exceptions and backend crashes to PostHog US Cloud to find and fix reliability problems. Reports include exception type, code locations, service, environment, app version and build. The SDK also supplies randomly generated anonymous installation and session identifiers and device metadata such as model, operating system, locale, and screen dimensions. These identifiers are not linked to your account. Raw exception messages, email addresses, credentials, request bodies, posture measurements, and camera data are removed. Person profiles and IP/geolocation enrichment are disabled. Error diagnostics are always enabled in production and have no in-app opt-out. This is separate from product analytics or feedback details. Native iOS/Android crash capture and session replay are disabled.
  • Usage analytics: enabled automatically in supported app releases, with no in-app opt-out. The app sends app openings, screen visits, sign-in and registration outcomes, calibration outcomes, monitoring requests, starts, saved completions, interruptions, save failures, measured monitoring duration, platform, and app version/build to PostHog US Cloud. A random installation identifier connects these events across visits; separate random attempt identifiers connect steps in monitoring, sign-in, registration, or calibration. From app version 1.0.14, when you start monitoring while signed in, the start event also includes your account identifier for private operational notifications. Updated releases also include your account email address when available. Guest starts do not include an account identifier or email address. This allows related usage events with the same installation or run identifier to be associated with your account. Email is included only on identified monitoring-start events, not other usage events. We do not send posture scores, angles, camera data, or free-text messages. Person profiles and IP/geolocation enrichment are disabled. Historical sessions are not replayed. Pending events are kept on device for up to seven days, with a maximum of 200 events. The random installation identifier remains on your device until app data is erased; it is separate from error-diagnostic identifiers.
  • Support information: the email address and details you choose to send when contacting support.
  • In-app feedback (when you submit it): your account identifier, feedback topic, optional message, and submission time. You may include app version, detector, AirPods connection, Camera Assist status, and posture classification details, or turn those details off before sending. Feedback never attaches camera images, audio, or raw motion recordings. We use reports to investigate problems and improve the app. Feedback may be delivered to our configured support notification service. Reports stored in our app database are removed when you delete your account.

PostureSense uses AirPods motion data to detect posture states while a session is active. The app does not collect precise location, contacts, photos, camera recordings, or microphone recordings.

Use

How we use information

  • Subscription and payment information: subscription provider, product and transaction identifiers, verification status, access expiry, trial and cancellation history, and billing account association. Paddle processes web payment authorization, payment card information and applicable tax; Apple and Google process native-store payments. We do not receive or store your full payment card number. Providers retain payment records under their own policies and applicable obligations. Server verification links purchases to your account and prevents a purchase from being claimed by another account.
  • Authenticate your account and keep you signed in securely.
  • Run posture monitoring sessions and show live posture feedback.
  • Save posture history, summaries, goals, and settings locally, and sync them when you choose to sign in.
  • Send local posture reminders or alerts when enabled.
  • Provide customer support and maintain app security.
  • Improve app reliability and understand whether core features are working.

Sharing

Service providers and sign-in partners

We share information only as needed to operate PostureSense. Service providers may process account, authentication, hosting, database, and app infrastructure data on our behalf. If you sign in with Apple, Google, or another supported provider through Supabase authentication, those providers process the information required for that sign-in flow under their own terms and privacy policies.

PostHog processes sanitized error diagnostics in the United States. Our operational Slack and email notifications contain diagnostic summaries and links to issues. We do not use these diagnostics for advertising or cross-app tracking.

Our private operational Slack channel also receives account-created summaries containing the sign-in method, time, account identifier, and account email address when available. For releases with usage analytics enabled, monitoring-start summaries may be delivered through PostHog to this channel, including start time, platform, app version/build, and a random run identifier. From app version 1.0.14, starts from signed-in accounts also include the account identifier; updated releases additionally include the account email when available. Apple private relay addresses are used when that is the email supplied for the account. Guest starts remain anonymous. These summaries do not include posture measurements. Delivered notifications follow Slack's retention settings.

We may also disclose information if required by law, to protect users, or to protect the security and integrity of PostureSense.

Retention

How long we keep information

We keep account and posture history information for as long as needed to provide the app, maintain security, comply with legal obligations, resolve disputes, and enforce agreements. If information is no longer needed, we delete it or de-identify it where practical.

Choices

Your controls

  • Current app releases require sign-in. Guest sessions, goals, and detection settings saved by older versions remain stored locally on your device.
  • You can stop a posture session at any time.
  • You can control notification permissions in your device settings.
  • You can sign out from the app to remove local session access.
  • You can request that we delete your account and associated data through support-managed account deletion. In the Android beta, Settings → Request account deletion opens these instructions.
  • You can contact support if you cannot access the app or need help with a data request.

Children

Children's privacy

PostureSense is not directed to children under 13. If you believe a child provided personal information to PostureSense, contact us so we can review the request.

Updates

Changes to this policy

We may update this policy as PostureSense changes. The effective date above shows when the current policy became effective.