Skip to content

Service Level Agreement

Last updatedNovember 9, 2026

1. Who this applies to

This Service Level Agreement ("SLA") applies to customers on the ZeroLeaks Enterprise plan whose signed order form or agreement with ZeroLeaks refers to it (the "Agreement"). It is part of that Agreement. Where the Agreement and this SLA differ, the Agreement wins.

Other plans have no SLA. For them, the Services are provided as described in the Terms of Service.

2. Uptime commitment

ZeroLeaks will make each Covered Service available with a Monthly Uptime Percentage of at least 99.8% in every calendar month. That allows about 86 minutes of downtime in a 30-day month.

The Covered Services are:

  • The ZeroLeaks web app and dashboard at zeroleaks.ai.
  • The ZeroLeaks API at api.zeroleaks.ai, including the Shield API for paid Shield models.

The following are not Covered Services: the free Shield model, the documentation site, the blog, the status page, features labelled beta or preview, and the SDKs and CLI running on your own systems. This SLA covers availability. It does not cover how long a scan takes or what a scan finds.

3. How uptime is measured

An external monitor that runs outside ZeroLeaks' hosting checks each Covered Service every five minutes. A check fails when the service returns a server error or does not answer within ten seconds.

"Downtime" starts at the first of two or more consecutive failed checks and ends at the next successful check. The "Monthly Uptime Percentage" is the number of minutes in the month minus the minutes of Downtime, divided by the number of minutes in the month, multiplied by 100. Downtime caused by an exclusion in section 4 is not counted.

If you saw Downtime that the monitor did not record, send your evidence with your claim. We will review it in good faith.

4. Exclusions

Downtime does not include unavailability caused by:

  • Scheduled maintenance announced on status.zeroleaks.ai at least 48 hours ahead, up to 4 hours in a calendar month. Maintenance beyond that counts as Downtime.
  • A region-wide or global outage of a hosting or infrastructure provider that ZeroLeaks uses, such as Cloudflare, Convex, or Amazon Web Services, that the provider reports on its own status page and that ZeroLeaks could not reasonably have avoided.
  • Your systems, including the AI agents and endpoints you ask ZeroLeaks to scan, your network, and model providers or credentials you supply.
  • Use that breaks the Agreement or the Terms of Service, including requests above your plan's rate limits, and suspension of your account under them.
  • Events outside ZeroLeaks' reasonable control, such as natural disasters, war, or government action.

5. Service credits

If a Covered Service misses the commitment in a month, you are entitled to a credit against the fees for that Covered Service for that month:

Monthly Uptime PercentageCredit
Below 99.8% but at least 99.0%10%
Below 99.0% but at least 95.0%25%
Below 95.0%50%

Credits in a month are capped at 50% of that month's fees for the affected Covered Service. They are applied to your next invoice. They are paid out only if the Agreement ends and no invoice follows.

6. How to claim a credit

Email support@zeroleaks.ai within 30 days after the end of the month. Include the Covered Service, the dates and times you were affected, and any evidence you have. We will reply within 10 business days with the monitor's records for that month and the credit, if one is due.

7. Support and incident response

Enterprise customers can report issues to support@zeroleaks.ai and security concerns to security@zeroleaks.ai. We aim to give a first response within these times:

  • Critical (a Covered Service is down, or a suspected security incident): 1 hour, at any time.
  • High (a major feature is not working): 4 business hours.
  • Normal (other issues and questions): 1 business day.

Business hours are 09:00 to 18:00 Central European Time, Monday to Friday. During an outage, we post to the status page within one hour of declaring the incident and update it at least every four hours until it is resolved. If we confirm that your data was exposed, we will email you without undue delay and within 72 hours of confirming it.

Response times are targets. Missing them does not earn a credit.

8. Repeated failures

If a Covered Service has a Monthly Uptime Percentage below 95% in two consecutive months, or in any three months of a twelve-month period, you may end the Enterprise subscription for that Covered Service by written notice within 30 days after the last of those months. We will refund the prepaid fees for the rest of the term.

9. Remedies and changes

The credits in section 5 and the right to end the subscription in section 8 are your only remedies for ZeroLeaks not meeting this SLA, unless the Agreement says otherwise.

ZeroLeaks may update this SLA. A change that lowers a commitment does not apply to you until your current Agreement term renews.