Service Level Agreement
Last updated: 2026-11-08
This Service Level Agreement (SLA) sets out the support and availability targets for paid SentinelPanda subscriptions. It forms part of the Terms of Service. It is deliberately modest: it states what we can deliver reliably today.
1. Scope
This SLA forms part of the Terms of Service and covers paid subscriptions to the production application at app.sentinelpanda.com. It does not cover free trials, the free self-assessment tools, the marketing website, or features labelled beta or preview.
2. How to reach support
Raise a ticket from the Tickets page in the application; that is the fastest route and keeps the history in one place. If you cannot sign in, email sales@sentinelpanda.com. Report suspected security incidents or vulnerabilities to security@sentinelpanda.com.
Support hours are 9:00 to 17:00 US Eastern Time, Monday to Friday, excluding US federal holidays ("business hours").
3. Response targets
We aim to send a first response from a person within these times, counted in business hours:
- Severity 1: the service is unavailable, or you suspect a security incident affecting your data. Within 4 business hours.
- Severity 2: a major feature does not work and there is no workaround. Within 1 business day.
- Severity 3: a minor problem, or a workaround exists. Within 2 business days.
- Severity 4: questions and feature requests. Within 5 business days.
These are targets for a first response, not for resolution. We will agree the severity with you and keep you updated until the issue is closed.
4. Availability target
We target 99.5% monthly availability for the production application, measured by our external checks of the application's health endpoint. That allows roughly 3.6 hours of downtime in a 30-day month. Scheduled maintenance and the exclusions in section 7 do not count as downtime.
This is a target, not a guarantee, and no service credits apply. If we miss it in a month, we will tell your account administrators what happened and what we are changing, and send a written incident summary on request.
5. Scheduled maintenance
Most updates are deployed without downtime. When maintenance does need downtime, we announce it at least 48 hours in advance by email to account administrators, schedule it outside business hours where possible, and keep it under 4 hours in total per month. Urgent security fixes may be applied with shorter notice.
6. Incident communication
If the service is unavailable or seriously degraded for more than 30 minutes, we email account administrators when we confirm the problem and again when it is resolved. Personal data breaches are handled under our data processing agreement, which sets the notification commitments.
7. Exclusions
The availability target and response targets do not apply to problems caused by:
- events outside our reasonable control, including failures of the wider internet or of hosting and network providers beyond our infrastructure;
- your own systems, networks, browsers, or identity provider (for example an SSO outage at your provider);
- third-party services you connect, such as integration vendors' APIs;
- suspension of your account under the Terms of Service, or use that breaks the acceptable use section;
- features labelled beta or preview.
8. Changes
We may update this SLA. We will give at least 30 days' notice by email or in the product before any change that reduces these targets, in line with section 13 of the Terms of Service. A separately signed order form takes precedence over this SLA where they differ.