Trust & Compliance

Service Level Agreement

Which services carry a contractual service level, how availability is measured, and the limited credit available when we fall short.

Last updated: 27 October 2026 Applies to all Luveedu Cloud services
Service Level Agreement

Luveedu Cloud · Wenxenith Technologies LLP · Last updated 27 October 2026 · luveedu.cloud

This Service Level Agreement ("SLA") records the limited availability commitment that we are prepared to make, the manner in which availability is measured, and the sole remedy available to you if that commitment is not met. It is a narrow document by design, and it applies only to Services that we have expressly designated as eligible.

This SLA does not apply to shared hosting, cloud hosting, WordPress hosting, reseller hosting, or to any VPS plan that has not been expressly designated as SLA-Eligible. Availability figures published on our website are operational targets and descriptions of typical performance, and are not contractual guarantees.

1.Introduction and Scope

This SLA forms part of our agreement with you and must be read together with our Terms and Conditions. It applies only to a Service that satisfies every condition in Section 3 and Section 5. Where any condition is not satisfied, no service level, no target, and no credit applies.

The SLA describes availability of the platform only, meaning the ability of our network and host infrastructure to respond to our own monitoring. It does not describe, and does not extend to, the availability, speed, correctness, or fitness of your application, code, plugins, themes, database queries, third-party integrations, or content.

This SLA replaces any prior statement, marketing material, sales conversation, or online comparison that refers to uptime, availability, or service credits. Where any such statement conflicts with this SLA, this SLA prevails.

Nothing in this SLA obliges us to maintain any particular service level for any Service that is not a Designated SLA-Eligible Service, and no course of dealing, published figure, or technical capability creates such an obligation.

2.Definitions

In this SLA, the following terms have the meanings given below. Terms defined in our Terms and Conditions carry the same meaning here.

  • Designated SLA-Eligible Service means a specific plan that we have expressly marked as SLA-Eligible at the point of purchase or in the client area. No other plan is eligible, and eligibility may be withdrawn in accordance with Section 16.
  • Availability means the proportion of minutes in a calendar month during which our monitoring records the Designated SLA-Eligible Service as responding, calculated under Section 6.
  • Unavailability means a continuous period in which our monitoring records a complete failure to respond, applying the thresholds in Section 6. Partial failure, degraded performance, elevated latency, packet loss, intermittent errors, and reduced throughput do not constitute Unavailability.
  • Incident means a single continuous period of Unavailability affecting one Designated SLA-Eligible Service.
  • Service Credit means the account credit described in Section 8, which is the sole and exclusive remedy available under this SLA.
  • Monitoring Data means the records generated by our monitoring systems, which are the sole authoritative record for the purposes of this SLA.
  • Scheduled Maintenance and Emergency Maintenance have the meanings given in Section 13.
  • Business Day means a day other than a Saturday, Sunday, or public holiday in India.

3.Services Eligible for the SLA

A service level exists only where we have expressly created one. A Service is a Designated SLA-Eligible Service only if all of the following are true:

  • the plan page or order screen expressly labels the plan as SLA-Eligible;
  • the client area displays the Service as SLA-Eligible at the time of the Incident;
  • the Service is active, fully provisioned, and paid for in advance for the relevant period; and
  • the Service has been continuously active for at least 30 days before the Incident, so that a baseline can be established.

Where these conditions are not met, the Service is provided on a commercially reasonable efforts basis only, with no availability commitment and no credit of any kind.

We determine, in our discretion, which plans are designated as SLA-Eligible. Designation is a commercial decision, is not a representation about the performance of any other plan, and may be limited to particular billing terms, resource sizes, or regions.

4.Services Not Covered

For the avoidance of doubt, this SLA does not apply to any of the following, and no availability commitment or service credit arises in respect of them.

  • Shared hosting of any plan, tier, or billing period.
  • Cloud hosting of any plan, tier, or billing period.
  • WordPress hosting of any plan, tier, or billing period.
  • Reseller and agency hosting, including any service you provide to your own customers.
  • Any VPS plan that has not been expressly designated as SLA-Eligible, including standard, promotional, trial, and custom VPS plans.
  • Domains - registration, renewal, transfer, restoration, and DNS operated by a registry or registrar.
  • SSL certificates - issuance, validation, and renewal by a certificate authority.
  • Email - mailbox access, delivery, deliverability, and reputation.
  • DNS, CDN, backup, migration, AI tools, and all ancillary services, whether provided by us or by a third party.
  • Free plans, trials, beta and preview features, promotional periods, and any Service supplied at no charge.

We may operate availability monitoring and internal targets for these Services. Internal targets are operational tools for our own engineering teams. They are not commitments to you, are not published as guarantees, and create no right to any remedy.

5.Conditions Precedent to Any Claim

Any claim under this SLA is subject to each of the following conditions being satisfied, both at the time of the Incident and at the time of the claim. Failure to satisfy any one of them entitles us to reject the claim in full.

  • The Service is a Designated SLA-Eligible Service within the meaning of Section 3.
  • Your account is in good standing, with no overdue invoice, no unresolved payment dispute, and no open breach of our Terms and Conditions or Acceptable Use Policy.
  • You have not been suspended, restricted, or throttled for any reason attributable to your use of the Service.
  • The Service is configured in a supported manner, using supported software versions, within the resource limits of the plan.
  • The Incident is not attributable to any cause listed in Section 10.
  • You submit the claim within the period, and in the form, required by Section 9.
  • You provide the information we reasonably require to verify the claim.

Credits are calculated only on the recurring fee actually paid for the affected Designated SLA-Eligible Service in the month of the Incident, after any discount or promotional reduction. Fees for add-ons, domains, licences, one-off services, professional services, and taxes are excluded from the calculation.

6.How Availability Is Measured

Availability is measured exclusively by our monitoring systems. Monitoring Data is the sole authoritative record for the purposes of this SLA, and our determination based on that data is final, subject only to Section 17.

Method

  • Checks are made against the Designated SLA-Eligible Service at intervals determined by us, typically 60 seconds.
  • A check succeeds when the Service returns a valid response within the timeout configured by us.
  • An Incident begins only when checks from a majority of our probe locations fail consecutively for the period set out below.
  • An Incident ends at the first successful check, as recorded by our systems.

Thresholds

An Incident is recorded only if it is continuous for at least 30 minutes and is confirmed by at least three consecutive failed checks from a majority of probe locations. Shorter interruptions, intermittent failures, and isolated regional reachability differences are not recorded as Incidents and do not affect Availability.

Calculation

Availability is calculated as the total minutes in the calendar month, less minutes recorded as Unavailability and less minutes of Scheduled Maintenance, divided by the total minutes in the month, expressed as a percentage and rounded down to two decimal places.

Customer evidence

Monitoring performed by you or by a third party is not determinative. We may consider such evidence at our discretion, but we are not obliged to depart from Monitoring Data, and we may decline a claim where your evidence cannot be correlated with our records, was captured from a location or network we do not use, or would require us to infer a result that our systems did not record.

7.Availability Target for Designated Services

Where a Service is a Designated SLA-Eligible Service, the availability target for that Service in a calendar month is 99.9%, measured in accordance with Section 6.

This figure is a target that determines whether a credit may be available under Section 8. It is not a warranty, not a guarantee of uninterrupted service, and not a promise that the Service will meet that figure in any particular month. It does not apply to any Service listed in Section 4, and it does not apply during any period in which this SLA is suspended or the Service is not a Designated SLA-Eligible Service.

Where the availability of a Designated SLA-Eligible Service in a calendar month is at or above the target, no credit is due, and no claim may be brought in respect of that month.

8.Service Credit Schedule

Where Availability for a Designated SLA-Eligible Service falls below the target in Section 7, and the conditions in Sections 5 and 9 are satisfied, the following credit may be available. The amounts are deliberately modest, because they reflect the fee for the affected month and not the consequences of any interruption.

  • 99.90% or higher - no credit.
  • 99.50% to 99.89% - credit of 5% of the monthly fee.
  • 99.00% to 99.49% - credit of 10% of the monthly fee.
  • 98.00% to 98.99% - credit of 20% of the monthly fee.
  • 95.00% to 97.99% - credit of 30% of the monthly fee.
  • Below 95.00% - credit of 50% of the monthly fee, being the maximum credit available.

Further limitations

  • Only one credit may be issued per Designated SLA-Eligible Service per calendar month, regardless of the number of Incidents in that month.
  • Credits are issued as account credit only. They are not cash, are not redeemable, are not transferable, and carry no monetary value outside our platform.
  • Credits expire 90 days after issue if not applied, and are forfeited on closure of the account.
  • No credit is available on a Service supplied free of charge, at a promotional price of zero, or during a trial.
  • Where a subscription is paid annually, the monthly fee used is one twelfth of the amount paid, after any discount.

9.How to Submit a Claim

There is no automatic credit. A credit is issued only where a valid claim is received, verified, and approved. The process is intentionally procedural, because a credit cannot be assessed without reliable detail.

Step 1 - Submit within 15 days

Submit the claim by opening a billing ticket from your client area, or by emailing [email protected] from the address registered on your account. The claim must be received within 15 calendar days after the end of the calendar month in which the Incident is said to have occurred. Claims received after that period are barred, because our detailed per-service records are not retained beyond it.

Step 2 - Provide the required detail

  • the Service identifier or server IP address;
  • the date and time the Incident is said to have begun and ended, with the time zone;
  • a description of the failure as you observed it;
  • the invoice number for the affected month; and
  • any evidence you wish us to consider.

Step 3 - Assessment

We acknowledge claims within 48 hours on Business Days and aim to complete our assessment within 10 Business Days. We compare the claim with Monitoring Data. We may request further information, and we may decline a claim where the required detail is missing, inconsistent, or cannot be verified.

Step 4 - Decision and application

Our decision is final, subject only to Section 17. An approved credit is applied to the next invoice issued after approval. If no further invoice will be issued, the credit is applied against any outstanding balance and any remainder is forfeited.

10.Exclusions and Excluded Events

No credit is payable, and no failure to meet the target in Section 7 is actionable, in any of the following circumstances. The list is illustrative of the boundary of our commitment and is not exhaustive.

Planned and protective work

  • Scheduled Maintenance, whether or not it overruns the window described in Section 13.
  • Emergency Maintenance, including work carried out without notice.
  • Work required by a registry, a certificate authority, an upstream provider, or a competent authority.

Customer-side causes

  • Your application, code, plugins, themes, scripts, cron jobs, or database queries.
  • Resource exhaustion caused by your traffic, your configuration, or your Content, including inode, CPU, memory, process, and connection limits.
  • An expired domain, an incorrect DNS record, a removed SSL certificate, or a lapsed licence.
  • Changes, restarts, migrations, or updates carried out by you or on your instruction.
  • Suspension, restriction, throttling, or termination for breach, non-payment, or risk.
  • Failure to apply security updates or to follow our published guidance.

Third-party and external causes

  • A third-party network, registrar, registry, certificate authority, CDN, payment provider, or email provider.
  • Your visitors, their devices, their internet service providers, or local censorship and filtering.
  • Public telecommunications, power, or upstream transit failures.
  • Any denial-of-service or other hostile activity, including activity that is within the mitigation capacity of your plan.
  • Events of force majeure as described in our Terms and Conditions.

Measurement and scope boundaries

  • Interruptions shorter than the 30-minute threshold in Section 6.
  • Degraded performance, latency, packet loss, or partial loss of functionality that does not amount to a complete failure to respond.
  • Single-region or single-network reachability differences.
  • Any Service listed in Section 4.
  • Any month for which a valid claim is not received within the period in Section 9.

11.Why Our Timing and Thresholds Are Structured This Way

Each limit in this SLA exists to make the commitment measurable and sustainable. We set out the reasoning so that the boundary is understood rather than assumed.

Why coverage is limited to designated plans

Shared, cloud, WordPress, and reseller hosting run on multi-tenant infrastructure where a single customer can affect neighbours through resource contention, and where a maintenance action may touch many accounts at once. A per-customer availability commitment is not technically meaningful on that architecture. A contractual service level is therefore offered only on plans where resources are isolated and the measurement is attributable to a single customer.

Why the month is the measurement period

Invoices are built from calendar months. Applying the same period means the credit is a direct percentage of a figure you were actually charged, with no estimation. It also prevents a short, unrepresentative period from producing a distorted percentage.

Why a complete failure is required

Availability is a binary measurement in this SLA: the Service either responds or it does not. Slowness and partial degradation are affected by your application, your traffic, and your configuration, and cannot be attributed reliably to the platform. Including them would make the metric subjective and the outcome unpredictable for both sides.

Why the threshold is 30 minutes

Short interruptions are absorbed by retries, connection reuse, and caching, and are frequently invisible to visitors. A 30-minute floor ensures that only interruptions of real consequence affect the measurement, and it prevents very short events from being aggregated into claims that do not reflect customer impact.

Why our Monitoring Data governs

Our monitoring is continuous, consistent in method, and retained in a form that can be audited. Customer-side measurement varies in location, interval, and configuration, and cannot be reconciled reliably across claims. Using a single authoritative source keeps the assessment consistent for every customer.

Why the claim window is 15 days

Detailed per-service records are retained for a limited period for privacy and operational reasons. Fifteen days is enough to notice an issue and report it, and short enough that the record is still available to verify. A longer window would invite claims that cannot be tested against retained data.

Why the credit is a small percentage of the fee

The fee is the only figure that is agreed in advance and identical for every customer on the same plan. Compensating against revenue, profit, or business impact would require us to assess your business, would vary unpredictably, and would make the cost of the commitment impossible to price. A percentage of the fee keeps the remedy proportionate, predictable, and equal for all customers.

Why the maximum is 50%

A credit is a reduction in the price of a month in which performance fell short, not a transfer of business risk. Our prices are set on the basis that our exposure is limited to a fraction of the fee, and the 50% ceiling reflects that basis. A higher ceiling would require higher prices for every customer.

12.Support Response Targets

The following response times are operational targets. They describe how we aim to prioritise and begin work. They are not guarantees, they do not form part of the availability commitment, they are not a resolution commitment, and no credit arises from a missed response target.

  • Priority 1 - Critical. Complete unavailability of a Designated SLA-Eligible Service. First response target: 1 hour, at any time.
  • Priority 2 - High. Material degradation of a Designated SLA-Eligible Service. First response target: 4 hours.
  • Priority 3 - Normal. A single feature not behaving as expected, or a configuration question. First response target: 12 hours on Business Days.
  • Priority 4 - Low. General questions and suggestions. First response target: 24 hours on Business Days.

Priority is assigned by us, based on the technical description in the ticket and the number of customers affected. A ticket opened as Priority 1 that does not meet the definition above may be reclassified, and the reclassification determines the applicable target.

Response targets are measured during the hours stated. Time spent waiting for information from you, time during which the Service is under Scheduled Maintenance, and time attributable to any exclusion in Section 10 are disregarded.

Where a ticket is not progressing as you expect, reply to it with the word escalate and a short summary of the impact. Escalation changes the internal owner of the ticket; it does not create a new commitment or a credit entitlement.

13.Maintenance

We require flexibility to maintain, secure, and upgrade the platform. The following applies to all Services, including Designated SLA-Eligible Services.

Scheduled Maintenance

  • We aim to give at least 24 hours notice, but notice is a courtesy and not a condition of carrying out the work.
  • We choose the window, which is normally outside peak hours for the region, but we are not obliged to schedule work outside business hours.
  • There is no fixed monthly limit on Scheduled Maintenance. Windows may exceed 60 minutes where the work requires it.
  • Minutes of Scheduled Maintenance are excluded from the Availability calculation, whether or not the window overruns.

Emergency Maintenance

We may carry out Emergency Maintenance at any time, with or without notice, where we consider it necessary for security, integrity, stability, or to prevent a wider failure. Emergency Maintenance and any resulting interruption are excluded from the Availability calculation and from any credit, and we are not obliged to obtain your consent or to schedule the work around your usage.

Your maintenance

You are responsible for maintaining your application, dependencies, and content. Interruptions arising from your own maintenance, updates, or migrations are excluded from this SLA.

14.Credits, Limits and Sole Remedy

Service Credits are the only remedy available to you for any failure to meet a target in this SLA. They replace any other claim, whether in contract, tort, statute, or otherwise, arising from that failure, except where the law provides a right that cannot be excluded.

Our total liability under this SLA in any billing month is limited to 50% of the recurring fee paid for the affected Designated SLA-Eligible Service in that month. This limit applies to the aggregate of all credits, claims, and remedies connected with that Service and that month.

Credits are proportionate to the fee and are not compensation for consequences. They do not cover lost sales, lost revenue, lost profit, lost advertising spend, lost goodwill, wasted management time, the cost of rebuilding a website, or any indirect or consequential loss, all of which are excluded by our Terms and Conditions.

We may decline a claim, in whole or in part, where we reasonably believe that it is exaggerated, duplicated, submitted on multiple accounts, submitted by a person not authorised to act for the account, or made in bad faith. We may also set off any credit against an amount you owe us.

Nothing in this Section limits liability for fraud, for death or personal injury caused by negligence, or for any liability that cannot be limited by law. If you are a consumer, your statutory rights that cannot be waived by agreement are unaffected.

15.No Warranty of Uninterrupted Service

The Services are provided on an "as is" and "as available" basis, in accordance with our Terms and Conditions. We do not warrant that any Service, including a Designated SLA-Eligible Service, will be uninterrupted, error-free, free of latency, or available at any particular time.

Any figure described as uptime, availability, or a service level on our website, in marketing material, or in a sales conversation is an indication of typical performance or an internal engineering target. It is not a warranty, not a condition of the contract, and not a representation on which you should rely when deciding whether to purchase.

You are responsible for designing your own resilience, including independent backups, redundancy where your availability requirements justify it, and monitoring of your own services. Where your requirements exceed what this SLA provides, you should arrange independent redundancy rather than rely on a single provider.

16.Changes to This SLA

We may amend, replace, suspend, or withdraw this SLA, in whole or in part, at any time. Where we make a material change, we will publish the revised version on this page and update the date shown at the top.

We may withdraw SLA-Eligible designation from a plan on 30 days notice. Following withdrawal, the plan continues to be provided, but without any availability commitment or credit.

We may make changes without prior notice where the change is required by law, by a provider, or to correct an error, or where the change does not reduce an entitlement that has already accrued in respect of a completed calendar month.

Your continued use of the Services after a change takes effect constitutes acceptance of the revised SLA. If you do not accept a change, your remedy is to stop using the affected Service in accordance with our Terms and Conditions.

17.Governing Law and Contact

This SLA is governed by the laws of India, and the courts of Tripura have exclusive jurisdiction, subject to any right you have to bring a claim in a forum that cannot be excluded by agreement.

Before commencing any proceedings, you must submit a claim in accordance with Section 9 and allow us the period stated in that Section to assess it. We will not consider a claim that has not first been submitted through that process.

Service Credit claims and questions about this SLA should be sent to [email protected]. Legal notices should be sent to [email protected]. Our postal address is Luveedu Corporate Office, Bishalgarh, Sepahijala, Tripura, 799102 - India.

We acknowledge claims within 48 hours on Business Days and aim to complete our assessment within 10 Business Days.

Grievance Redressal

Grievance Officer

Wenxenith Technologies LLP has appointed a Grievance Officer for complaints and notices under this policy. He acts independently of our sales and support teams, and there is no charge to raise a grievance.

Email the Grievance Officer at [email protected]
Include your account email, the policy concerned, and any reference number
Expect an acknowledgement within 48 hours
We provide a written outcome within 30 days
Technical support remains available at [email protected]
Designated Grievance Officer
Shyamal Debnath
Grievance Officer
[email protected]
+91 7641818218
Luveedu Corporate Office, Bishalgarh, Sepahijala, Tripura, 799102 - India
We acknowledge every grievance within 48 hours and aim to resolve it within 30 days.