Effective Date: May 31, 2026 | Last Updated: May 31, 2026
Legal Notice
This SLA is a template and should be reviewed by qualified legal counsel before being shown to enterprise customers. Any availability, response-time, or credit commitments should reflect actual infrastructure capabilities and support resources.
Guaranteed service availability
Continuous system monitoring
Compensation for downtime
ContractLab is committed to providing reliable, high-quality service to all customers. This Service Level Agreement (SLA) outlines our commitments regarding system availability, performance, and support.
| Service Tier | Uptime Commitment | Max Downtime/Month |
|---|---|---|
| Free | 99.0% | 7.2 hours |
| Professional | 99.9% | 43.2 minutes |
| Team | 99.95% | 21.6 minutes |
| Enterprise | 99.99% | 4.3 minutes |
API Response Time
95th percentile response time under 500ms for all API calls
Contract Analysis Speed
Standard contracts analyzed within 5 minutes; Complex contracts within 15 minutes
File Upload Time
Files up to 50MB upload within 30 seconds on standard connections
Dashboard Load Time
Initial dashboard load under 2 seconds
| Priority Level | Description | Response Time |
|---|---|---|
P1 - Critical | Service completely unavailable | 15 minutes |
P2 - High | Major feature unavailable | 1 hour |
P3 - Medium | Minor feature issue | 4 hours |
P4 - Low | General questions, requests | 24 hours |
If we fail to meet our uptime commitment, you may be eligible for service credits:
| Monthly Uptime % | Service Credit |
|---|---|
| 99.0% - 99.89% | 10% of monthly fee |
| 95.0% - 98.99% | 25% of monthly fee |
| Below 95.0% | 50% of monthly fee |
* Service credits are your exclusive remedy for SLA breaches. Credits must be requested within 30 days of the incident and will be applied to future invoices.
Automated Backups
Daily automated backups of all customer data
Backup Retention
30-day retention for Professional; 90-day for Team/Enterprise
Recovery Time Objective (RTO)
4 hours for full system recovery
Recovery Point Objective (RPO)
Maximum 1 hour of data loss in disaster scenarios
The following are not covered by this SLA:
We continuously monitor our services using:
In the event of a service incident:
We may update this SLA from time to time. Material changes will be communicated via email at least 30 days before taking effect. Continued use of the service after changes become effective constitutes acceptance of the revised SLA.
For SLA-related inquiries or to request service credits: