Know what is protected
Monitoring, saved versions, backups and exports do different jobs. Check the evidence for the project you are working on rather than assuming that a ready address means every protection is active.
Check the platform and your project#
The MovePacket status page reports platform, storage/monitoring and scheduled-backup signals checked by Better Stack. It describes those monitored services, not every interaction inside every customer application.
In your workspace, Monitor summarises your projects' saved states and lists your Hub Pages. A project state records setup, saved versions and whether a version is live at the project's address; it is not a functional health check. Check availability confirms that a Page's saved files are still available; it does not test how the Page behaves or whether its data is current.
Use Settings → Security & recovery for access information, and your project's Updates for its versions and recovery controls. A platform-wide green status is not proof that your individual project is enrolled in automatic backup.
Choose the right recovery tool#
| Tool | What it helps with | What it does not establish |
|---|---|---|
| Restore a published version | Return hosted application files to an earlier saved version | Reversing record changes, emails or payments |
| Project recovery package | Keep supported project setup, published files, saved releases and private app records together | A complete copy of the athlete library or every outside service |
| Off-site backup and restore verification | Independently store an encrypted snapshot and check its supported recovery path | Coverage for projects not enrolled, or a guarantee every feature works |
| Business or athlete export | Review and move the records included in a privacy package | A ready-to-run replacement for the whole platform |
Save a project recovery package#
The account owner can use Save a recovery package → Download recovery package in the project's recovery section. Store the file privately and independently of the live project. The download can contain private project data; it is not an encrypted vault merely because credentials are excluded.
The current package covers the supported setup, saved creation, hosted app, ready releases and private app records. It excludes the shared athlete library, original ride files, event analyses, analytics history, outside providers, credentials, DNS and unpublished local work.
Packages are bounded to 32 MiB, 200 ready releases and 100 private records. Missing files, incompatible athlete links, privacy restrictions or larger scopes require review; a partial package is not presented as complete recovery.
Automatic off-site backups#
New eligible paid hosted projects are enrolled automatically when their first production release becomes ready. Enrollment alone is not proof of protection: confirm your project's successful off-site upload and restore verification with MovePacket. Existing projects were not automatically backfilled, and preview-only or unpublished projects are not covered by this hosted-project policy.
A successful upload and a successful restore check are separate pieces of evidence. The current pilot does not offer a general recovery-time guarantee, complete workspace backup or immutable ransomware protection. Expiry, retention and wider rollout need explicit arrangements.
If something goes wrong#
For a broken interface after publication, review the last working version. For missing data, a suspected access problem or a broader recovery need, stop further changes and contact MovePacket. Include the project name, affected address and approximate time, without keys or private athlete records.
Restores must preserve current privacy restrictions and deletion decisions. An old backup is not permission to restore revoked access or reopen deleted information.
Taking your work elsewhere#
Keep your source and project downloads, and use Settings → Privacy & exports for supported business or athlete packages. Moving away also requires replacement hosting, configuration, service access and data migration. An export does not automatically provision a replacement service or carry provider credentials with it.
See Privacy operations and the trust centre for the current scope and limitations.
Supplier evidence#
In Settings → Security & recovery, choose Build your evidence pack under Supplier evidence to find official terms, privacy, data-processing and security sources in one place. The same links appear under Supplier documents on integration cards.
Select the providers you actually use and choose Download document index. The dated HTML file includes the selected public links, MovePacket information and a collection checklist. Open it in a browser or print it to PDF. It contains no account records, credentials or private project data.
This first version is a link index, not an archive: save permitted supplier documents separately and request restricted reports from the provider. Source review dates do not mean contracts are unchanged or apply to your plan. Missing sources are flagged. Selections are not stored when you leave the page.
Keep your accepted agreements and signed DPAs alongside the current public versions. Supplier certifications do not certify your application. The index supports collection for privacy and insurance reviews; it does not establish compliance or cover. MovePacket's guides explain current controls and are separate from contractual agreements.