Privacy Policy
Proposed draft, not final or adopted. Legal entity and governing jurisdiction are pending legal confirmation. Retention requires legal review. This is not a certification or a statement of legal compliance or store readiness.
Proposed effective date: November 1, 2026 · Policy version: 1.2-proposed-draft
This policy covers the AERO//PULSE Velo athlete service and early-access signup. Early-access emails are one part of this broader policy.
Operator and contact
Brand: AERO//PULSE VELO
Legal entity / data controller: Pending legal confirmation — AERO//PULSE VELO is a brand, not a separately registered legal entity
Proposed governing jurisdiction: Chicago, Illinois — proposed; pending legal confirmation
Address: [Not configured: VITE_LEGAL_ADDRESS]
Support and privacy contact: spicelabs@consultant.com
Accounts and information you provide
Account information includes your email address, profile preferences, timezone, training goals, availability, baselines and answers you choose to provide. Training information includes plans, workout versions, completion history, feedback, strength logs and coaching decisions.
Ride and performance data
Authorized imports may include activity dates, duration, distance, power, heart rate, cadence, elevation, route coordinates and activity streams, when available from your connected service. Routes can reveal sensitive locations. Missing data is not treated as measured data. Calculated metrics and estimates are distinguished from recorded measurements.
Connected services
Strava supplies authorized activities and streams. WHOOP supplies authorized recovery, sleep, heart-rate variability, resting heart rate and strain information. Intervals.icu supplies authorized activity information and receives structured workouts when you request delivery. Available data depends on your permissions and the provider. Each provider also operates under its own privacy terms.
Disconnecting is separate from deleting imported data or deleting your APV account. Disconnect stops future access through the stored connection; retained history and records already sent to a provider are not automatically erased. Provider-side deletion or key revocation must be handled with that provider.
Purposes and coaching analysis
Data is used to operate accounts, present training history, calculate available performance metrics, prescribe workouts, support athlete-reviewed adjustments and troubleshoot service problems. Coaching and ride debrief features may generate explanatory text from athlete context. AI output may be wrong and is not medical advice or a substitute for professional judgment.
Approved AI processing details, categories sent to each processor, processing locations and contractual safeguards: [Not configured: VITE_LEGAL_PROCESSORS — approved processor details, hosting regions and AI provider]. These details are not yet verified; no claim about AI training use or data residency is made here.
Authentication, storage and processors
The service uses Supabase for authentication, application records and stored activity streams. Connected services process the information needed for authorized integration actions. The complete owner-approved processor list, hosting details and international-transfer information are pending: [Not configured: VITE_LEGAL_PROCESSORS — approved processor details, hosting regions and AI provider].
The owner must confirm the applicable legal bases for each purpose before adopting this policy. Connection authorization and marketing consent do not substitute for that review.
Retention and deletion
Owner-supplied proposed retention policy (requires legal review): Proposed draft, pending qualified legal review: provider tokens, OAuth state and provider account identifiers are removed when disconnection or account deletion begins. Account identifiers and imported training data are retained while active. After deletion, only necessary deidentified safety, security, dispute and audit records may remain, with original user/provider/activity/session identifiers, location, photos, device identifiers, personal notes and identifying text removed. Coaching records must also remove health and recovery details and linked activities. Deletion/support evidence may be retained for up to seven years when necessary; security/access logs for up to twelve months with unnecessary IP/device identifiers removed or rotated. Proposed encrypted-backup maximum is ninety days before overwrite; this is a policy requirement, not a verified backup setting. Future billing/tax information is retained only where legally required. Audit retention must be reviewed regularly and limited to reasonable necessity..
Training versions and calculation history are preserved during ordinary use. Profile → Account & privacy offers a confirmed account-deletion request, not instant erasure. Accepted requests remove local provider credentials and connection identifiers, block new account writes and sign you out. Remote revocation is attempted; unconfirmed revocation and protected-history cleanup are reported in your private receipt. Protected history and final identity erasure require verified coordinated cleanup; blocked records remain identifiable and are not described as anonymous. No completion time is promised.
Provider-imported data removal is only available where supported. It may affect measured history and linked analysis; plans and generated coaching are not automatically rewritten. Early-access signup is separate from your account and must be included explicitly in a removal request.
Export and your privacy choices
Profile → Account & privacy provides an authenticated JSON export of supported account, training, performance and coaching records, with private stored power streams where available. Credentials are excluded. Data held only by providers and separately consented early-access submissions are not included. Large exports may require operator assistance rather than returning an incomplete file.
Depending on your location and applicable law, you may have rights to access, correction, deletion, portability, objection, restriction or withdrawal of consent, and to complain to your local authority. Contact the operator to request assistance; identity verification may be needed. Use connected-service settings to manage permissions and sharing. No universal legal-rights guarantee is made.
Early-access updates
The email-only signup records email, signup time, source and consent version. Consent is for launch news, previews and testing opportunities, not guaranteed access, dates or discounts. The signup itself does not send update emails. Any future marketing delivery needs a separate setup and an unsubscribe method. Contact the operator to withdraw consent or remove the signup.
Changes and unresolved facts
Material policy changes should be communicated before taking effect. The effective date, operator details, support contact, lawful bases, processor disclosures and retention schedule must be reviewed and completed before store release.
