Orbital Training Pretty Strong Training Adaptive performance system Your personalized training studio Open beta
Adaptive training Personalized training

Last updated August 27, 2026

Privacy notice

Orbital Training uses the information you provide to create and adapt training programs, save workouts, operate your account, and improve the beta. It does not sell your personal information.

Information the app stores

  • Your account email and authentication records.
  • Profile, questionnaire, training-goal, availability, equipment, and program information.
  • Workout logs, performance and effort entries, movement check-ins, weekly reviews, and pain or limitation information you choose to enter.
  • If you opt into a fitness connection: the provider, granted categories, consent events, daily steps and recovery summaries, workout summaries, and five-minute heart-rate buckets used for retrospective weekly-review charts. Some device-import paths may briefly retain detailed samples while normalizing them, but the web app does not use them for live workout feedback.
  • Beta feedback. A report includes its message, category, current page, app version, screen dimensions, installed-app status, and a broad browser family. Your email is included in the administrator digest only when you permit contact.
  • Operational logs needed for security, reliability, abuse prevention, and cost monitoring. Application logs are designed not to contain passwords or complete training records.

How the information is used

Information is used to provide the requested training service, preserve training history, personalize recommendations, respond to feedback, prevent abuse, diagnose failures, and maintain the security and performance of the service. Training and pain information is not used as medical diagnosis or treatment. Connected steps can satisfy a movement target without manual entry. Simplified recovery trends can conservatively pause an otherwise supported progression, but wearable data does not reduce training or make a health inference by itself.

Service providers

Supabase provides authentication and database services. Cloudflare provides application hosting, delivery, and security services. Resend delivers administrator feedback digests and may deliver account email after production email setup is completed. If you connect it, Google provides the categories you authorize. Apple Health or Health Connect data is read by the optional mobile companion and sent to Orbital only after device permission and account authentication. These providers process information under their own terms and privacy practices.

Retention and your choices

Account and training information is retained while your account remains active. Beta feedback is automatically deleted 90 days after submission, whether or not it has been reviewed. Any detailed heart-rate samples from a supported import path are automatically deleted after seven days; five-minute heart-rate buckets are retained for up to 400 days. Private provider audit events are retained for up to 365 days; consent history is retained with your account. Limited provider backups and security logs may persist for their normal backup or abuse-prevention periods. From Account, you can disconnect a provider, optionally delete its uploaded health data, download your account data, or permanently delete your account and associated application data.

Security and health connections

The app uses authenticated access and database row-level controls to keep each user’s records separate. Cloud-provider access and refresh tokens are encrypted before storage and are never sent to the browser or mobile companion. Raw heart-rate rows are not directly readable by browser clients. Each connection is optional and requires clear provider or device authorization; disconnecting stops future sync, and selecting deletion removes that connection’s uploaded health data. Reconnecting begins a new connection generation and clears retained data for that provider before importing again, which prevents records from different upstream accounts from being combined.

Contact

For privacy questions or requests that cannot be completed from Account, signed-in users can use the in-app Beta feedback form and allow a reply. Do not include health information or other sensitive details in a public GitHub issue.