Your data stays in context.
Workspace records and activity files are private by default. Public pages contain the version you explicitly publish. Share example content until you have decided what can be made public.
MOVEPACKET / PUBLIC SECURITY OVERVIEW
MovePacket platform controls. Customer applications, connected provider accounts and coaching-business procedures have their own scope.
Controls described here are supported by implementation review and automated tests. No independent SOC 2 or ISO 27001 report is published here, and we make no HIPAA compliance claim. Provider certifications do not certify MovePacket or an individual coaching business.
Your account resolves to your own workspace. Requests check membership and ownership before returning private records.
Evidence and limits: Automated tests cover cross-workspace access, revoked membership and suspended accounts.
MovePacket provider credentials stay in server-side secret storage. Builder connections are scoped to one application and can be revoked.
Evidence and limits: Builder tests cover expiry, revocation and refusal of access to another application. Connection files belong in private local configuration, outside chat and Git.
Customer sign-in uses WorkOS AuthKit. MovePacket verifies identity and uses encrypted, secure, HttpOnly session cookies.
Evidence and limits: Tests cover modified cookies, sign-in state validation, workspace assignment and logout revocation. This does not claim that every customer or provider account enforces MFA.
Uploaded activity originals are stored privately, with checksums and a record of processing. Access is scoped to the workspace and, where assigned, the athlete.
Evidence and limits: Tests compare original file bytes and reject requests outside the authorised workspace or athlete. Archiving an athlete does not itself delete their files.
Generated first-project pages run in a restricted preview. Publishing creates an explicit public snapshot of the content you choose to share.
Evidence and limits: Preview controls restrict network access and access to the surrounding workspace. Public pages are not a place to put private athlete information or credentials.
Protection separates backup-file observations from restore-test results, with the date and the systems each check covers.
Evidence and limits: A successful job or an existing file is not a recovery guarantee. A restore result applies to the tested backup and systems, not automatically to all MovePacket storage.
Backup freshness and the last successful restore test belong to the project they cover. The private Protection area records available observations, dates, failures and exclusions.
The current reference-project restore evidence does not verify recovery of MovePacket’s separate workspace records, athlete files or every hosted application. Full-platform recovery has not been verified.
Workspace records and activity files are private by default. Public pages contain the version you explicitly publish. Share example content until you have decided what can be made public.
The first-project generator sends your description and current project to the configured AI provider. Keep private athlete and health information out of this flow. Your preferred external builder has its own account and data-handling terms.
Archiving stops an athlete being treated as active; it is not a deletion action or permission to retain upstream data. File deletion, backup retention and connected-platform permissions need to be considered separately.
| Provider | Purpose | Information involved |
|---|---|---|
| Cloudflare | Application delivery, database, private object storage and server secrets. | Workspace records, uploaded files, application content and operational request data. |
| WorkOS | Customer identity, hosted sign-in and account recovery. | Account identity and authentication information. |
| Anthropic | Generation and refinement of the first project. | The description and current project submitted for a generation request. Use example content in this flow. |
| Stripe | Hosted checkout and subscription management; currently connected in test mode. | Test billing and subscription records, and details entered into Stripe checkout. |
| GitHub | Source control and automated build or operations workflows. | Application source and workflow information; not a general athlete-data destination. |
This is an operational inventory, not a formal subprocessor register. Applicable contracts, locations and transfer arrangements must be reviewed separately.
This overview describes platform implementation. Your own business must supply its legal entity, data inventory, people and device controls, incident contacts, policies and relevant project evidence. It is not a completed insurance application, privacy notice, DPA or assurance of coverage.
Project reports are available to authorised users in Protection → Documents. Review their dates, scope and contents before sharing.