Private-beta access
Service terms
Restor is not a public self-service product. This page is a plain-language service boundary, not click-wrap terms. Access is provided only after the customer and the Restor legal entity sign a beta agreement and DPA; those signed documents are the binding terms.
Last updated 18 July 2026 · private beta
Before access
The parties must identify the legal entities, designated operator, supported-data schedule, subprocessors and transfers, price, support contacts, incident contacts, retention, termination, and any measured service levels. Restor will not provision customer access while those items are incomplete.
Service boundary
The beta provides daily versioned observations of documented HubSpot surfaces, weekly association reconciliation, exports, and reviewed one-record restore for supported types. It is not an entire-portal backup, a continuous transaction log, bulk rollback, legal archive, or substitute for the customer's own access/security controls.
Customer responsibilities
- Authorize only a dedicated operator and protect that account, mailbox, HubSpot, and provider administrators with MFA.
- Have authority to process the connected portal data and approve every required scope and subprocessor.
- Review coverage, exclusions, restore plans, and restore outcomes; report suspected errors or incidents promptly.
- Keep independent business-continuity controls appropriate to the customer's risk until measured recovery commitments are signed.
Recovery and availability
A restore can modify or recreate HubSpot data. Restor applies the safeguards shown in the review flow, but provider availability, schema changes, permissions, and ambiguous network outcomes can require manual reconciliation. No RPO, RTO, availability promise, warranty, or liability term exists except as written in the signed beta agreement.
Contact
Request the binding beta agreement, DPA, and coverage schedule at hello@restor.eu.