Movenue
LAST UPDATED NOVEMBER 1, 2026

Privacy, in plain language.

Information you provide

Account details, workout preferences, onboarding answers, set logs, feedback, and support messages. Optional health context is stored only when you choose to provide it.

Optional Apple Health imports

In the iPhone app, you can choose to read workout summaries and optional activity and heart-rate summaries from Apple Health. First you grant permissions and review an on-device preview. Only when you separately confirm Save are those summaries sent securely to Movenue’s server, encrypted in storage, and associated with your account so you can view them across devices. We do not import workout routes, raw heart-rate samples, medical records, or sleep records. We do not write to Apple Health or sync in the background. Imported Health data is not sent to OpenAI or other AI services, used for advertising or product analytics, or stored by Movenue in iCloud.

Managing Health history

You can remove all imported Health history in All workouts → Apple Health → Privacy & remove imports. This removes Movenue’s active copy, not the original records in Apple Health. You can revoke read permissions in Apple Health; this does not remove previously saved imports. Removing a record in Apple Health does not automatically remove Movenue’s copy. Hosting-provider backups, if retained, expire according to the provider’s backup retention. Imports are optional and not required for other Movenue features. Summaries are for training history, not diagnosis or medical advice.

Camera and form companion

Camera access is optional. Live camera frames are processed in your browser for movement cues and are not uploaded or stored by Movenue. Form feedback is general fitness guidance, not medical advice or a diagnosis.

Payments and service providers

Stripe processes payment details; Movenue stores subscription status and Stripe identifiers, not complete card numbers. We also retain applied promotion codes and records of checkout agreement, including the accepted base price, policy version and time, to administer subscriptions and resolve billing questions. Authorized administrators can review billing context and changes. Hosting, email, database, and media providers process limited data needed to deliver the service.

Product analytics

We record a limited first-party funnel: CTA, account, verification, onboarding, workout, form companion, checkout, second-workout, and cancellation events. Events use random browser/session identifiers, page paths, and small non-sensitive properties. We do not include health free text, camera frames, passwords, or payment details.

HeyCatch website analytics

We also use HeyCatch to understand public website visits, campaign links and interactions, and whether visits lead to account, onboarding or subscription outcomes. The SDK uses browser storage for pseudonymous browser and session identifiers and attribution. We mask captured page text and element attributes, remove unapproved query values and URL fragments, retain approved campaign codes, keep only public same-site referrer paths or known external platform origins, and exclude private referrers. Browser events from account, member, administrator and camera-tool screens are filtered out, apart from minimal account-identity messages. Our servers report limited account and billing outcomes using an internal account identifier. We do not send account names or email addresses, Health imports, workout details, health answers, camera frames, passwords, authentication tokens or card details to HeyCatch. As with other external website requests, HeyCatch can receive connection metadata such as an IP address and browser information. Clear your browser site data to remove stored identifiers.

Campaign and creator links

Public campaign links can contain approved source, campaign, content, and creator codes so we can understand which links lead to useful activity. The first campaign is remembered in your browser for up to 30 days; the latest campaign is remembered for the browser session, with the same maximum age. Only approved public codes are added to first-party events. We do not record full referring URLs, advertising click identifiers, or arbitrary link text, and we do not send these events to an advertising network. Clear your browser site data to remove remembered codes. Blocking browser storage may limit attribution.

Account support and connection diagnostics

To troubleshoot sign-in and account issues, we record limited account-linked connection metadata: an IP address when supplied by our trusted hosting proxy, connection time, sign-in method, derived device/browser labels and a request identifier. Authorized administrators can see this alongside account and billing identifiers. Approximate city, region and country are estimated using a database on our server; we do not send your IP to an external geolocation lookup service or collect GPS location. VPNs and mobile networks can make these estimates inaccurate. We keep at most 50 sampled connections per account in a 30-day viewing window and remove expired records on the next diagnostics read or write. Hosting backups may retain older copies according to their retention policy. Diagnostics do not include Health imports, workout content, raw browser headers, passwords, session tokens or request bodies, and are not used for advertising.

Your choices

You can skip optional profile fields, deny camera access, update account details, cancel a subscription, or ask for access or deletion by emailing support@getmovenue.com.