Parties
Identify the legal names and contact details of the hosting provider and the customer, including billing and legal notice addresses and authorized signatories.
A well‑written Remote Hosting Agreement clarifies responsibilities, reduces ambiguity around uptime and backups, and documents security and compliance obligations such as HIPAA or industry standards. It limits operational risk, supports regulatory audits, and provides a contractual pathway for dispute resolution and data return or deletion after termination.
Organizations and providers across several functions rely on Remote Hosting Agreements to set expectations and legal responsibilities before production onboarding.
Depending on industry and data sensitivity, signatures may require authorized corporate signers, procurement approval, and, for some records, notarization or witness attestations.
Identify the legal names and contact details of the hosting provider and the customer, including billing and legal notice addresses and authorized signatories.
Define hosted systems, supported software versions, boundaries of responsibility (application vs. platform), and any excluded services such as custom integrations or third‑party licenses.
Specify uptime targets, scheduled maintenance windows, backup frequency, recovery time objectives (RTO) and recovery point objectives (RPO), and credits for SLA breaches.
List encryption standards, access controls, vulnerability management, penetration testing, logging and monitoring, and breach notification timelines and procedures.
Confirm customer ownership of data, permitted uses by the provider, permitted subcontractors, and procedures for data export, return, or secure deletion on termination.
Define termination rights, notice periods, data retrieval processes, fees for data export, and obligations to destroy or return copies, including timelines.
| Field | Configuration |
|---|---|
| Authentication Method | Email, SMS code, KBA, or SSO |
| File Format | PDF/A preferred for archiving |
| Retention Settings | Set retention period and export options |
| Notification Rules | Signer reminders and completion alerts |
Confirm platform support for document formats, integrations, and authentication required by your organization before eSubmission.
Choose a platform that offers audit trails, secure storage, and compliance certifications matching your regulatory needs; confirm BAA or PCI DSS if handling PHI or card data.
Date parties sign; obligations may start immediately.
Date services and SLAs begin (often post‑onboarding).
Specify response and resolution windows for incidents.
Typical 30–90 days before automatic renewal.
Timeframe for export after termination, often 30–90 days.
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7‑day free trial | Varies | Varies | Varies | Varies |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No cap | 100 envelopes/user/year | Varies | Varies | Varies |
Optica needed simple, mobile signing for investor and vendor paperwork to reduce turnaround time.
Xerox integrated hosted signatures with ERP workflows to automate approvals and reduce manual processing.