Arkynox Legal
Service Level Agreement
Our measurable commitments for ArkyDesk availability and support responsiveness, and your remedies if we miss them.
1.Scope and Incorporation
This Service Level Agreement (“SLA”) forms part of, and is incorporated into, the Terms and Conditions between you and Arkynox. It sets out the service levels that apply to the ArkyDesk support platform (the “Service”), how we measure them, and the credits available if we fail to meet them.
This SLA applies to all workspaces on paid plans. Free-tier workspaces receive best-efforts support and are not eligible for service credits, though we apply the same operational standards to them internally.
2.Definitions
- Business Hours means 09:00–18:00 India Standard Time (IST, UTC+5:30), Monday to Friday, excluding Indian public holidays notified on our status page.
- Monthly Uptime Percentage means the total minutes in a calendar month, minus Unplanned Downtime, divided by the total minutes in that month, expressed as a percentage.
- Unplanned Downtime means minutes in which the Service is unavailable to perform its core function (creating, viewing and updating tickets), excluding Excluded Downtime under Clause 10.
- First Response means the first substantive, human reply to a ticket — automated acknowledgements do not count.
- Resolution means the ticket is closed with a fix, a workaround accepted by you, or a documented answer to your question.
3.Support Hours and Channels
Standard support operates during Business Hours, anchored to IST. Follow-the-sun coverage across our support locations extends effective coverage to approximately 05:30–22:30 IST on business days. Critical (P1) issues are handled 24×7, including weekends and holidays, for paid plans.
Support is provided through:
- the in-product ticket system (primary channel, and the only channel to which the response targets in Clause 4 apply);
- the support email address displayed in your workspace, which is converted into a ticket; and
- the emergency contact route shown inside your workspace for Critical (P1) issues on enterprise plans.
4.Priority Levels and Response Targets
Every ticket is assigned a priority by our support team based on the definitions below. Response targets are measured during Business Hours except for Critical issues, which are measured around the clock.
| Priority | Definition | First response | Resolution target |
|---|---|---|---|
| Critical (P1) | Service down or core function unusable for all users; no workaround; or a confirmed security incident affecting your data | 2 hours, 24×7 | Continuous effort until resolved |
| High (P2) | Core function severely degraded, or a major feature unusable, with no reasonable workaround | 4 Business Hours | 1 business day |
| Normal (P3) | Standard product issue with a workaround; general product questions | 24 Business Hours | 5 business days |
| Low (P4) | Minor issues, cosmetic defects, documentation requests, feature requests | 72 Business Hours | Scheduled with our product roadmap |
5.Service Availability
We commit to a Monthly Uptime Percentage of at least 99.9% for the Service, measured per calendar month and excluding Excluded Downtime. We publish real-time and historical availability on our status page, and we report the previous month’s figures inside the Service.
Our standing internal performance indicators are:
- at least 95% of first responses within the Clause 4 targets;
- at least 90% of tickets resolved within their resolution target; and
- a customer satisfaction score of at least 4.5 out of 5, measured on closed tickets.
6.Maintenance
6.1Planned maintenance
We schedule planned maintenance outside Business Hours wherever practicable and give at least 72 hours’ advance notice on the status page and, for disruptive maintenance, by email. Planned maintenance windows never exceed four (4) hours and are excluded from the uptime calculation.
6.2Emergency maintenance
Where urgent action is needed to protect the Service or your data — for example, deploying a security patch — we may perform maintenance without prior notice. We will notify you as soon as practicable and keep the disruption as short as possible.
7.Escalation
Tickets move through a defined escalation path:
- Level 1 — Support Agent: first response within the Clause 4 target; triage, known-issue resolution, documentation.
- Level 2 — Support Specialist: engaged automatically when an L1 target is at risk, or on request; deeper technical investigation.
- Level 3 — Subject-Matter Expert: product or infrastructure specialists for complex defects.
- Engineering: code-level fixes, with a workaround provided wherever one exists while the fix is developed.
You may request escalation at any time by replying to the ticket. Escalation does not reset the applicable response or resolution clocks.
8.Service Credits
If Monthly Uptime Percentage falls below 99.9% in a calendar month, you are entitled to a credit against your next invoice, calculated as a percentage of the monthly fee for the affected workspace:
| Monthly uptime | Service credit |
|---|---|
| 99.0% – 99.89% | 10% of the monthly fee |
| 95.0% – 98.99% | 25% of the monthly fee |
| Below 95.0% | 50% of the monthly fee |
To claim a credit, open a ticket referencing this SLA within thirty (30) days of the end of the affected month. Credits are verified against our monitoring records, are applied to future invoices, and are not redeemable for cash. Service credits are capped at 50% of the monthly fee for the affected workspace in any month.
9.Security Incident Notification
If we confirm a personal data breach affecting your data, we will notify you without undue delay and, where the law of your jurisdiction sets a deadline, within that deadline — including the 72-hour windows under the GDPR, UK GDPR and India’s Digital Personal Data Protection Rules, 2025 (which additionally require us to give affected users at least 48 hours’ notice before erasure-related steps where applicable). Our handling of security events follows our ISO/IEC 27001:2022-aligned incident management process, as described in Clause 6 of the Privacy Policy.
10.Exclusions
This SLA does not apply to, and no downtime or delay counts towards a breach of it, where caused by:
- planned or emergency maintenance carried out in accordance with Clause 6;
- factors outside our reasonable control, including internet backbone failures, force majeure events, war, epidemics, or government-ordered network restrictions;
- your equipment, software, network configuration or connectivity;
- third-party services or integrations not operated by Arkynox;
- your breach of the Terms or the Acceptable Use Policy, or suspension under Clause 13.3 of the Terms; or
- beta, preview or trial features identified as such.
11.Remedies and Consumer Rights
Service credits under Clause 8 are your primary financial remedy for availability failures. Where uptime falls below 95.0% in three (3) consecutive months, you may additionally terminate the affected paid plan for material breach and receive a pro-rata refund of prepaid, unused fees.
12.Review, Changes and Contact
We review this SLA at least annually as part of our management review process. Changes follow the notice procedure in Clause 16 of the Terms and will never reduce the commitments applicable to a paid plan during its current billing term.
Questions about this SLA, credit claims, or escalation requests: open a ticket in your workspace or email legal@arkynox.com.

ArkyDesk