How MovePacket keeps your athletes’ data safe.
Who can see your work, where your information goes and what you can recover.
Your workspace
is private.
Only you can see your workspace. New projects start private, and making one public is a separate choice.
Athlete logins and individual rider sharing aren’t available yet.
How access is protected
Separate customer workspaces
Your account resolves to your own workspace. Requests check membership and ownership before returning private records.
Automated tests cover cross-workspace access, revoked membership and suspended accounts.
Technical detail →Protected account sessions
Customer sign-in uses WorkOS AuthKit. MovePacket verifies identity and uses encrypted, secure, HttpOnly session cookies.
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.
Technical detail →Isolated project previews
Generated first-project pages run in a restricted preview. Publishing creates an explicit public snapshot of the content you choose to share.
Preview controls restrict network access and access to the surrounding workspace. Public pages are not a place to put private athlete information or credentials.
Technical detail →Hosted project updates and public page snapshots are different sharing flows. Read the sharing guide →
Passwords and keys
stay on our servers.
Keys are the passwords software uses to reach a service. MovePacket keeps them on its servers, never in your pages.
Your AI builder gets limited access to one project, and you can revoke it any time.
What this covers
Credentials kept out of the browser
MovePacket provider credentials stay in server-side secret storage. Builder connections are scoped to one application and can be revoked.
Builder tests cover expiry, revocation and refusal of access to another application. Connection files belong in private local configuration, outside chat and Git.
Technical detail →This covers MovePacket’s infrastructure credentials. A general vault for your own service keys is not available yet. Keep keys out of AI chat and use only a supported connection flow.
Explore connections →Where your
information goes.
Your records and ride files are stored privately in MovePacket’s Cloudflare database and file storage, encrypted with AES-256.
When you build with AI, your description and current project are sent to an AI provider. Use example content while you build, and bring in real athlete data through authorised connections.
Storage, AI and data handling
Private files with provenance
Uploaded activity originals are stored privately, with checksums and a record of processing. Access is scoped to the workspace and, where assigned, the athlete.
Tests compare original file bytes and reject requests outside the authorised workspace or athlete. Archiving an athlete does not itself delete their files.
Technical detail →Your external AI builder has its own terms. Archiving an athlete does not delete their files; retention and deletion need separate decisions.
Read the privacy policy →Undo changes and
export your work.
Restore a previous published version to undo a change. Download a recovery package of your project’s files and records.
Automatic off-site backups are rolling out and aren’t on every project yet.
Backup coverage and recovery limits
Restoring a published version does not reverse data changes, emails or payments. Recovery packages do not include the shared athlete library, original ride files or external services.
Recovery evidence with a scope
Protection separates backup-file observations from restore-test results, with the date and the systems each check covers.
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.
Technical detail →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.
Check the recovery guide →Full details.
For your own checks, a client question or a conversation with your insurance broker.
Which services handle my information?
This is the reviewed platform inventory. Your own connected services are listed separately in your workspace.
| 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. |
Reviewed . This is an operational inventory, not a formal subprocessor register. Applicable contracts, locations and transfers need their own review.
Current service status
Not checked yetA current API reachability check runs when this page opens.