Service Level Agreement
1. Scope and Contractual Status
This Service Level Agreement ("SLA") describes availability, support handling and service-credit commitments for the paid KumoBunker email backup service supplied by Kumify Pte. Ltd. ("Kumify", "we", "us" or "our"). It covers personal, household and business Customers whose accepted Order includes this SLA.
The Terms of Service ("TOS"), accepted Order, Acceptable Use Policy ("AUP"), Privacy Policy and any executed data processing agreement ("DPA"), business associate agreement ("BAA") or transfer instrument continue to apply. Capitalised terms not defined here have the meanings in the TOS.
This SLA governs its specific service-level commitments and service-credit calculation. It does not override mandatory law, required data protection safeguards or an expressly negotiated superior commitment in a signed agreement. No service-level commitment is activated merely because this draft has been prepared or shared for review.
2. Service-Level Summary
| Item | Commitment or scope |
|---|---|
| Monthly Availability Commitment | At least 99.5% of Eligible Minutes for the covered paid Service |
| Availability measurement | Across all hours of the applicable calendar month, measured for the affected Customer's covered Service |
| Standard staffed support | Monday to Friday, 9:00 a.m. to 6:00 p.m., Singapore time, excluding Singapore public holidays |
| Critical incident initial response | Within four Business Hours after receipt through a designated support channel |
| Planned maintenance exclusion | Up to 120 minutes per calendar month for the affected Service, with at least 48 hours' advance notice |
| Availability remedy | Service credit according to Section 8, subject to verification and the applicable exclusions |
| Recovery time and recoverable-data age | No fixed guarantee unless expressly agreed in the Order |
| Emergency Mail start-up target | Standby mailboxes ready for sign-in within 4 Business Hours after we acknowledge an Emergency Mail request (Section 6) |
| Trials and unpaid preview features | No availability-credit entitlement under this SLA |
"Business Hour" means an hour falling within the staffed support window above. Support-response times are not elapsed-clock-hour promises outside that window. Availability measurement and automated scheduled functions operate independently of staffed support hours.
3. Covered Service and Availability
3.1 Covered functions
The covered Service consists of the production functions included in the Customer's paid Order:
- Authorised access to the account dashboard and its essential account/backup controls.
- The backup platform's ability to accept and process eligible scheduled or manually requested backups from supported, correctly configured mailboxes.
- Access to retained backup data for supported browsing, search, download or restoration, according to the mailbox type and user permissions.
- Where purchased, the platform functions required to produce and manage the optional Immutable Backup & Recovery protection copies. Assisted recovery follows Section 6 and does not carry an unagreed completion-time guarantee.
The public marketing website, non-production previews and a function not included in the Order are not covered production functions. An advertised but unsupported connection method is not made supported by this SLA; compatibility remains as disclosed in the TOS and product documentation.
3.2 What counts as Unavailability
"Unavailability" means a failure within the covered Service or Kumify's contracted service infrastructure that prevents the affected Customer from using a covered essential function, including a platform failure that prevents an otherwise eligible backup or restore job from being accepted or processed. It is not limited to whether the public website responds.
A material Customer-specific or mailbox-specific failure can count even if other Customers can use the Service. The same interval is counted once for a given affected fee component, rather than separately for each user, mailbox or overlapping symptom. We do not average a failed Customer's experience across unaffected Customers to remove that failure.
Ordinary processing time for a valid large backup or restore is not itself Unavailability, but a platform outage or failure to provide the processing function cannot be excluded merely by labelling it a queue or a long-running job. A cosmetic issue that does not prevent an essential covered function is handled as a support issue.
The intended restrictions of private mailboxes and active immutable locks are not Unavailability. Private mailboxes do not offer browsing, search, opening or downloads; supported restoration is of the whole mailbox into itself. This does not excuse an actual failure to provide their included backup or restore functions.
4. Measurement and Calculation
We assess availability for each calendar month using Singapore time (UTC+8), limited to the interval during which the Customer has an active paid entitlement covered by this SLA.
- Covered Minutes: Minutes in that active entitlement interval.
- Excluded Minutes: Only the minutes properly excluded under Section 5, without overlapping double-counting.
- Eligible Minutes: Covered Minutes minus Excluded Minutes.
- Downtime Minutes: Unavailability during Eligible Minutes.
The formula is:
Monthly Availability (%) = 100 x (Eligible Minutes - Downtime Minutes) / Eligible Minutes.
Where no Eligible Minutes exist, no monthly availability percentage or availability credit is calculated for that interval. This does not remove any refund or other right available under the Agreement or law.
We measure incident start and restoration using available monitoring, operational and job logs, authenticated functional checks where used, and relevant Customer evidence. We use actual timestamps and minute-equivalent durations where available rather than ignoring a verified outage because it was not reported immediately. Overlapping outage intervals are combined before calculation. We do not round the calculated availability upward to avoid an earned credit.
Customers may provide relevant evidence to challenge a calculation. Our records are important evidence but are not declared conclusive regardless of other reliable information. We will reasonably investigate discrepancies and explain material exclusions.
Illustration: In a full 30-day month with no exclusions, Eligible Minutes equal 43,200. Downtime of 216 minutes gives exactly 99.5% availability. The calculation changes with the month length, partial-month entitlement and valid exclusions.
5. Limited Exclusions
The following are excluded only to the extent they actually cause the affected interruption:
- Planned maintenance: Up to 120 minutes per calendar month for the affected Service, provided we give at least 48 hours' advance notice identifying the expected window and affected functions. Time outside the notified window, maintenance beyond the monthly allowance, or maintenance lacking the required notice counts as eligible downtime unless a separate exclusion genuinely applies. We seek to schedule disruptive work during lower-usage periods.
- Customer-controlled causes: Invalid or revoked credentials, a disconnected source mailbox, unsupported configuration, Customer-selected folder exclusions, Customer network/device failure, or actions by the Customer or persons acting under its authority, where that cause prevents the relevant operation. Unrelated failures remain measurable.
- Source or destination mail-provider limits: Unavailability, rate limiting, changed authentication or rejection by a mail provider selected by the Customer, to the extent outside Kumify's responsibility and actually causing the failure. A failure within Kumify's own connection implementation is not excluded merely because a mail provider is involved.
- Capacity and authorised restrictions: Backup pauses caused solely by the Customer's purchased storage allowance being exhausted, a Customer-requested pause, or a lawful and proportionate restriction permitted by the TOS/AUP. An erroneous suspension or incorrect storage calculation attributable to Kumify is not automatically excluded.
- Qualifying force majeure: An event meeting the full conditions of TOS Section 20.2, including causation, reasonable control, notice and mitigation. Hosting, storage, power or network failures at our own providers are not automatically excluded just because a third party is involved.
Emergency maintenance and a cyber incident are not standalone blanket exclusions. They count unless another listed exclusion, such as a qualifying force majeure event, actually applies. None of these exclusions waives mandatory PDPA duties or a more protective binding commitment.
6. Backup and Recovery Commitments
We provide the agreed backup and recovery functions with reasonable care and skill. We retain recovery points under the supported Customer settings, the TOS and Privacy Policy; monitor relevant operational failures; and provide supported status information and failure alerts. The Customer must maintain valid mailbox access, sufficient storage, appropriate permissions and a suitable schedule and retention configuration.
Backup frequency is not a guarantee that every message becomes recoverable within exactly that interval. A daily schedule does not by itself guarantee a 24-hour recovery-point objective, nor does an hourly schedule guarantee that every initial or incremental job finishes within one hour. The age of the latest usable backup depends on completed successful runs.
Likewise, the time required to complete a restore depends on data volume, retained points, destination limits, connectivity and the recovery method. No fixed recovery-time objective, data-transfer speed, success percentage for every individual message or immutable-copy completion deadline is promised unless expressly documented in the Order.
Private mailbox restrictions, encrypted summaries and same-mailbox restoration remain as described in the TOS and Privacy Policy. Immutable protection copies use the separately disclosed UK/Netherlands workflow and active lock periods; this SLA does not alter their data locations or deletion timing.
Emergency Mail start-up target. Emergency Mail is a separately charged, per-incident service for backup Customers whose own mail system is unavailable. When we acknowledge a Customer's Emergency Mail request in writing, confirming the affected mailboxes, the last-known-good time and the emergency contact, we aim to have the temporary standby mailboxes created and their sign-in details issued to the emergency contact within 4 Business Hours of that acknowledgement. The target starts on our acknowledgement, not on receipt of the request; acknowledging a critical request is covered by the P1 initial-response target in Section 7.
The start-up target does not include: the time for the Customer, its IT provider or its DNS provider to make the required DNS changes (MX, SPF and DKIM) and for those changes to take effect; the time to copy recent mail into the standby mailboxes, which depends on volume and continues after sign-in is available; returning mail to the Customer's own mailboxes after the incident; or delays caused by missing or incorrect information, the Customer's mail provider, or an event described in Section 5. It is a support-handling target, not an availability-credit trigger under Section 8, and the standby mail server is not part of the Monthly Availability Commitment. Mailboxes marked private receive an empty standby mailbox for new mail only.
These limitations define the agreed metrics. They do not excuse negligent handling, an agreed security failure, failure to retain a promised recovery point, or another breach simply because the availability percentage was achieved. Such issues are assessed under the TOS, DPA and applicable law in addition to any relevant availability claim.
7. Support Priorities and Initial Response
Submit incidents through the account support channel or https://www.kumobunker.com/contact. Mark urgent reports with the account identifier and priority sought. Provide timestamps, affected functions, job identifiers and a safe description; do not send passwords, private keys, unnecessary sensitive data or copies of unlawful material.
| Priority | Typical impact | Initial response target |
|---|---|---|
| P1 - Critical | Covered Service broadly unavailable; an essential restore is blocked during an active incident; or a suspected serious security event | Within 4 Business Hours |
| P2 - High | A material backup or recovery function is impaired for multiple mailboxes, with limited workaround | Within 9 Business Hours |
| P3 - Normal | A limited operational issue, single-mailbox problem or general technical support request | Within 18 Business Hours |
| P4 - Low | Product questions, non-urgent configuration advice or feature requests | Within 27 Business Hours |
"Initial response" means a human response that acknowledges the issue and provides an initial assessment, next action or a relevant request for information. An automated receipt alone does not meet this target. The clock starts on receipt; time outside staffed support hours does not accrue as Business Hours. For example, an otherwise qualifying P1 report received on a Saturday starts accruing Business Hours at 9:00 a.m. on the next Singapore business day.
We may reasonably adjust priority to match actual impact and will explain a material change. A temporary workaround may reduce priority, but does not retrospectively erase an initial response miss. We investigate and provide reasonable progress updates according to impact. Resolution time is not guaranteed by an initial-response target.
The numerical response times are support-handling targets, not separate availability-credit triggers. A missed target can be escalated and may be relevant to a broader contractual breach; it does not automatically earn an extra credit under Section 8.
Standard support is not a promise of a 24-hour staffed helpdesk. This support clock does not delay or limit notification or response duties under the Singapore PDPA, a DPA, BAA or another applicable law. In particular, any required data-intermediary notice to a Customer remains due without undue delay, independently of business hours or ticket priority.
8. Availability Service Credits
If the Monthly Availability Commitment is not met, an eligible Customer may request the following credit:
| Verified Monthly Availability | Credit percentage of the Eligible Monthly Fee |
|---|---|
| 99.5% or higher | No availability credit |
| 99.0% or higher but below 99.5% | 10% |
| 95.0% or higher but below 99.0% | 25% |
| Below 95.0% | 50% |
The Eligible Monthly Fee is the net subscription fee attributable to the affected covered Service for that measurement month, after applicable discounts and excluding taxes, unrelated services, one-off fees and refunded amounts. For an annual subscription, the monthly equivalent is the annual fee divided by 12. For a partial measurement month, the fee basis is proportionately reduced to the paid entitlement interval within that calendar month.
If only the paid Immutable Add-on is affected, the credit basis is the applicable add-on fee. If the base Service and purchased add-on are both affected, their relevant fees may be included, but no fee component is credited twice for overlapping incidents. The highest applicable tier applies once to the relevant fee basis; tiers are not added together. Total availability credits do not exceed 50% of the eligible fee basis for the month.
Credits normally reduce a future invoice and are not an immediate cash refund or a transferable balance. They do not expire while the eligible account remains active. If the account permanently ends before an approved credit can be applied, we account for it in the final billing reconciliation, applying it to valid outstanding charges or returning any remaining approved value. Annual payment does not require purchasing another annual term simply to use an approved credit.
9. Credit Requests and Review
Request an availability credit within 30 calendar days after the end of the affected measurement month, identifying the account, approximate outage times, affected functions and any relevant ticket or job identifiers. We do not require you to prove facts solely within our control or to provide confidential email content to establish an outage.
This deadline governs the additional contractual availability-credit process only. It does not shorten a statutory claim period or remove a refund, breach remedy or data protection right. We will reasonably consider a late request where an extended outage prevented timely submission or material information needed from us was unavailable.
We aim to acknowledge a credit request within five Business Days and provide a decision within 15 Business Days after receiving the reasonably necessary information. A "Business Day" is Monday to Friday excluding Singapore public holidays. If more time is reasonably needed, we explain why and provide an updated estimate. The decision will state the measured availability, relevant exclusions, fee basis and approved credit or reason for rejection.
You may request review through the same support route. An initial rejection is not conclusive proof that no contractual or statutory remedy exists. An invoice may be disputed under the TOS without forfeiting an otherwise eligible credit claim.
10. Relationship to Refunds and Other Remedies
An availability credit and a cash refund are different remedies. Credits address the measured availability shortfall; the Refund Policy and TOS govern cancellation, erroneous charges, discontinued service, unremedied material breach and other cash-refund situations.
Credits are the standard additional monetary remedy created by this SLA for a straightforward availability-percentage shortfall. They are not the exclusive remedy for every contractual breach, loss of data, confidentiality breach, negligence, fraud or statutory violation. The TOS liability provisions apply according to their lawful terms, and mandatory Consumer and data protection rights remain effective.
No Customer receives compensation twice for the same loss or unused service interval. Any overlap must be reconciled fairly; an unrelated credit or claim does not justify withholding a refund otherwise due. A material force-majeure interruption continuing for more than 30 consecutive days retains the termination and unused-prepayment refund rights in TOS Section 20.2, even if that event is excluded from the availability calculation.
11. Excluded Offerings, Changes and Contact
Trials, free services and expressly identified beta/preview functions do not receive availability credits under this SLA. Their express promises, reasonable-care obligations and statutory protections still apply.
We may update this SLA using the TOS material-change procedure. We do not retroactively reduce earned credits, change a completed month's measurement rules, or reduce a separately negotiated commitment by publishing a replacement. Material adverse changes to prepaid service preserve the applicable termination and refund rights.
Kumify remains subject to the Singapore PDPA and applicable subsidiary legislation. Neither an exclusion nor a credit limit waives required security, breach notification, lawful retention/deletion or overseas-transfer safeguards.
Kumify Pte. Ltd. | Singapore UEN 202647131C Website: https://www.kumobunker.com Support and SLA requests: Your account support channel or https://www.kumobunker.com/contact