Data Byte Limited

Legal Service Level Agreement (SLA)

Service Level Agreement (SLA)

This Service Level Agreement (“SLA”) describes the support, response targets, and service standards provided by Data Byte Limited (“we”, “us”, “our”) for eligible services and support plans.

CompanyData Byte Limited
Address18 Stanley Rd, London, E12 6RJ, UK
Last updated21 January 2026

1. Overview

This SLA applies to clients who have an active support/maintenance plan or a written agreement stating that SLA coverage is included. Unless stated otherwise in your contract, this SLA is a best-practice framework with target response and resolution times (not guarantees).

2. Scope and eligibility

Covered services may include (as per your plan): website uptime monitoring, incident triage, bug fixes, performance checks, security hardening guidance, backups/restores, and small content or configuration changes.

  • SLA coverage begins once the support plan is active and access details are provided.
  • SLA coverage may require that the system is maintained on supported versions and follows baseline security practices.
  • For new builds, SLA coverage typically starts after launch sign-off or handover.

3. Support hours

Standard support hours: [Monday–Friday], [09:00–18:00] (UK time), excluding UK public holidays. If you have a premium plan with extended coverage, your contract terms will apply.

Critical incidents may be triaged outside standard hours where feasible, depending on your plan tier and the nature of the incident.

4. Severity levels

Severity Description Examples
Sev 1 — Critical Production system down or a security incident with active impact. Site unavailable, checkout/payment broken, active compromise
Sev 2 — High Major functionality impaired; no immediate workaround. Core pages broken, major integration failure, severe performance degradation
Sev 3 — Medium Partial functionality issue or workaround available. Minor feature broken, layout issue on specific devices, non-critical plugin conflict
Sev 4 — Low General request, small changes, cosmetic issues, questions. Content updates, small UI tweak, “how-to” request

5. Response and resolution targets

“Response time” means the time to acknowledge the request and begin triage. “Resolution time” means the time to restore service or provide a fix/workaround, where feasible, based on complexity and third-party dependencies.

Severity Target response Target resolution / workaround
Sev 1 — Critical [1 hour] [4–8 hours] (workaround ASAP, fix as soon as practicable)
Sev 2 — High [4 hours] [1–2 business days]
Sev 3 — Medium [1 business day] [3–5 business days]
Sev 4 — Low [2 business days] [Next scheduled cycle] or as agreed

Resolution targets may be impacted by waiting for client approvals, credentials, or third-party platform actions.

6. Support channels

For faster triage, include: affected URL/system, screenshots, error logs (if available), steps to reproduce, and whether the issue is new or recurring.

7. Maintenance and planned downtime

We may perform planned maintenance (e.g., updates, patches, infrastructure changes). Where maintenance could cause downtime, we aim to provide notice (typically [48–72 hours]) and schedule during low-traffic windows where possible.

  • Emergency maintenance (security patches, urgent stability fixes) may occur with limited notice.
  • Third-party provider outages or maintenance are outside our control.

8. Client responsibilities

  • Provide and maintain accurate access credentials and approvals in a timely manner.
  • Ensure licensed use of themes/plugins/tools and keep subscriptions current where needed.
  • Do not make untracked changes directly on production without coordination (to avoid breaking changes).
  • Follow recommended security practices (strong passwords, MFA/2FA, least-privilege access).

9. Exclusions

Unless explicitly included in your plan, the SLA does not cover:

  • New feature development, major redesigns, or large content migrations
  • Issues caused by unauthorised third-party changes, malware from compromised credentials, or unsupported plugins/themes
  • Third-party platform failures (hosting provider outages, payment gateway downtime, social/ads platform changes)
  • On-site hardware/network issues outside the hosted environment

10. Service credits

If service credits apply, they must be defined in your contract (plan tier, eligibility, and calculation method). Unless otherwise agreed, service credits (if any) are applied as account credits against future invoices and are the sole remedy for SLA-related claims.

Service credits are not available where downtime or failure is caused by client actions, third-party providers, force majeure events, or scheduled maintenance.

11. Security and backups

Security and backup coverage depends on your plan and hosting setup. Where included:

  • Backups: scheduled backups with a defined retention window (e.g., [7–30 days]).
  • Restores: best-effort restores from available backups, subject to integrity and provider limitations.
  • Security: patching guidance, monitoring, and incident triage. No system is 100% secure; we cannot guarantee prevention of all attacks.

12. Changes to this SLA

We may update this SLA from time to time. Updates will be posted on this page and reflected in the “Last updated” date. If you have a signed contract, contract terms take precedence for the duration of that agreement.