Privacy and collection notice

Who is collecting it

Aerithm operates this five-person private beta under the trading name Aerithm and controls the beta account and product data. Aerithm is not represented here as an incorporated company. Send privacy, access, correction, deletion, support, or complaint requests to wqiaan@gmail.com. Formal legal-entity verification remains required before a public or paid launch.

What is collected

• Invitation, email, authentication, consent version, and security/audit events.
• Display name, required birth month and physiological reference sex, and optional height and weight.
• Training availability, typical weekly distance, constraints, goals, target-time intent, and recent athlete-confirmed performance evidence.
• Running and health records only when a supported import or connection is deliberately used. Current Garmin-specific consent may include precise ten-day GPS routes, maximum-cadence activity signals, original files, detailed health streams, and Garmin-supplied personal records, running VO₂-max estimates, threshold evidence, and race predictions.
• Minimal product feedback and operational records needed to support and secure the beta.

Why it is collected

The data is used to authenticate your account, resume setup, describe your personal history, compare eligible runs, present source-labelled Garmin estimates, check plan eligibility, generate the exact preview you review, provide running analysis and planning, secure the service, and support the beta. Garmin estimates never silently replace athlete-verified records or alter an accepted plan. If required profile or consent data is not provided, the first-five setup cannot activate.

Disclosure and location

The hosted beta uses Railway application processing in Singapore and Supabase authentication and PostgreSQL data services in Sydney, Australia. Personal information may therefore be processed outside Australia in Singapore. Provider security, administration, and support systems may operate internationally under their own service terms. Aerithm does not use beta health data for advertising or sell it.

Access, export, correction, deletion, and complaints

You can correct onboarding answers before accepting a plan. After authentication, the Data controls provide a JSON account export and an account-deletion request. Deletion first closes beta access, then removes the authentication identity and tenant-owned product records; a completed receipt retains a one-way pseudonymous digest but no email, authentication subject, training, profile, or health data. Aerithm's operator-managed logical database backups are isolated from ordinary use and retained for no more than 30 days. Before a restored copy may serve traffic, the operator must reconcile deletion records and remove any account deleted after that backup was created. Send access, correction, deletion, or privacy complaints to wqiaan@gmail.com; Aerithm will acknowledge them within two business days and aim to resolve them within 30 calendar days.

Security and limits

Hosted controls use authenticated tenant boundaries, least-privilege database access, request rate limits, and minimized operational logs. Uploaded CSV/JSON content is parsed for a short-lived preview and is not retained as a raw file by the application; normalized running records remain until deletion. No system can promise absolute security. Do not include credentials, precise home locations, or unnecessary medical detail in free-text fields.