Last updated: September 2026
Service Level Agreement
How we look after Adoptest while it is in early access.
If you use Adoptest to check documentation before a release, our reliability affects your team. This page sets out what we aim for on availability, support, data handling and maintenance. These are targets we work to, not contractual guarantees. Written service commitments are available on Enterprise terms.
1. Availability
- Aim: we work to keep the Adoptest checking engine available at all times and to restore service quickly when something goes wrong.
- Designed not to block you: if Adoptest is unavailable, administrators can bypass a check so urgent fixes and releases are not held up.
2. Support response targets
We aim to respond according to the severity of the issue.
| Severity | Definition | We aim to respond |
|---|---|---|
| Urgent (L1) | Production blocker: Adoptest is blocking your team's releases. | Within 1 business day |
| High (L2) | Degraded service: Checks are failing or the interface is unavailable, but a workaround exists. | Within 2 business days |
| Normal (L3) | General support: Setup help, billing questions or feature requests. | Within 3 business days |
Business hours are Monday to Friday, 09:00 to 18:00 IST, excluding public holidays.
3. Data handling
- We read and compare your material to produce findings.
- We keep only what is needed for your records: findings, content hashes and approval details.
- Your material is never used to train external language models.
- See the Privacy policy for full details.
4. Scheduled maintenance
We try to deploy updates without interruption. If maintenance needs brief downtime, we aim to tell administrators in advance and schedule it outside busy hours.
5. Contacting support
Email us so we can track every request and respond to it properly.
We are committed to a better experience and service as Adoptest grows, and we will not take away anything described as a standard offering on this page.