1. Scope
This SLA covers the availability of the core LekhaBooks web application at app.lekhabooks.in — logging in, creating and viewing invoices, recording transactions, and accessing your data. It applies only while your subscription is on a paid plan and in good standing (not expired, not suspended under the Terms, and not in a free/trial tier).
Third-party and government-dependent features are covered by best-effort only and are explicitly excluded from the uptime commitment (see section 8). These include GST portal filing, e-invoice (IRP) and e-way-bill generation, bank-feed imports, payment-gateway checkout, SMS/e-mail delivery, and any AI ("Lekha AI") features that depend on an external model provider.
2. Uptime commitment
We target a Monthly Uptime Percentage of 99.5% for the core application, measured per calendar month (IST). At 99.5% the maximum allowed unavailability is about 3 hours 39 minutes in a 30-day month.
3. How uptime is measured
"Monthly Uptime Percentage" = (Total minutes in the month − Downtime minutes) ÷ Total minutes in the month × 100, rounded to two decimals.
- "Downtime" means a period in which the core application returns server errors (HTTP 5xx) or is unreachable for all users, confirmed by our external monitoring, for a continuous period of 5 minutes or more.
- Downtime is measured by our third-party uptime monitor probing the application at 1-minute intervals from outside our network. Monitoring data is the authoritative source for any credit claim.
- Brief, isolated errors affecting a single account, single request, or single feature (rather than the whole application) are handled as support incidents, not as SLA downtime.
4. Service credits
If we miss the 99.5% monthly target for a given calendar month, you may claim a service credit as a percentage of that month's subscription fee (i.e. the annual fee divided by 12, or the monthly fee for monthly plans). Credits are applied to your account and adjusted against your next renewal.
| Monthly uptime achieved | Service credit (% of that month's fee) |
|---|---|
| 99.5% or above | No credit (SLA met) |
| Below 99.5% but at or above 99.0% | 10% |
| Below 99.0% but at or above 98.0% | 15% |
| Below 98.0% but at or above 95.0% | 25% |
| Below 95.0% | 50% |
Service credits are our standard remedy for any failure to meet the uptime commitment. They do not limit your right to a refund under Section 7 of the Terms of Service or any right that cannot be excluded by law. The total credits issued for any single month will not exceed 50% of that month's subscription fee. Credits have no cash value while your plan is active. If your plan ends before a credit is applied, we will, at your choice, extend your plan by the credit's value or refund it to the original payment method on request within 30 days of the plan ending.
5. Support & response times
Support is available by e-mail to support@lekhabooks.in and via in-app chat, Monday to Saturday, 10:00–19:00 IST, excluding national holidays. "Response time" means our first meaningful human response, targeted at the following speeds (measured within support hours):
| Severity | Description | Target first response |
|---|---|---|
| S1 — Critical | Application fully down or inaccessible for your whole company; data appears lost or corrupted. | Within 4 business hours |
| S2 — High | A core function (invoicing, payments recording, reports) is broken with no workaround. | Within 1 business day |
| S3 — Normal | A feature is impaired but a workaround exists; questions and configuration help. | Within 2 business days |
| S4 — Low | General questions, feature requests, cosmetic issues. | Within 3 business days |
These are response targets, not resolution guarantees — resolution time depends on the nature of the issue. We assign the severity in good faith based on the reported impact and may re-classify with an explanation.
6. Scheduled maintenance
We reserve a recurring maintenance window on Sundays, 01:00–04:00 IST, during which the application may be briefly unavailable. Time inside a properly announced maintenance window does not count as Downtime for SLA purposes.
- Routine maintenance in the standard window: we aim to give advance notice where the work is user-visible, but no notice is guaranteed for the standard window.
- Planned maintenance expected to exceed 30 minutes of downtime: at least 48 hours' advance notice by e-mail and/or in-app banner.
- Emergency maintenance (security patches, urgent stability fixes): performed with as much notice as circumstances allow; excluded from Downtime.
7. Backups, RPO & RTO
Your business data is backed up so it can be restored after a failure:
- Backup frequency: full database backups are taken at least daily and stored separately from the primary database, on a rolling basis for up to 30 days: our own daily backup is kept for 14 days, and one copy, encrypted with our own key before it leaves our server, is kept off-site in Google Drive for 30 days (see Privacy Policy Section 10).
- Recovery Point Objective (RPO): 24 hours. In a worst-case data-loss event, we aim to lose no more than the last 24 hours of data. On our roadmap we intend to shorten this to 1 hour with more frequent/point-in-time backups after the infrastructure migration.
- Recovery Time Objective (RTO): 8 hours. In a major outage requiring restore from backup, we aim to bring the service back within 8 hours of declaring the incident.
- You can always take your own export at any time from Settings → Data & Backup — we strongly recommend keeping your own periodic export as well.
8. Exclusions
The uptime commitment and service credits do not apply to unavailability caused by:
- Scheduled or announced maintenance (section 6) and emergency maintenance.
- Third-party and government systems outside our control — GST portal, e-invoice IRP, e-way-bill system, bank feeds, payment gateways (Razorpay), SMS/e-mail relays, and external AI model providers. Outages of our own hosting (MilesWeb) and network (Cloudflare) providers count as downtime, as they are part of the service we provide.
- Force majeure — events beyond our reasonable control, including internet backbone or DNS failures, power failures, natural disasters, strikes, or government action.
- Issues arising from your systems, network, browser, mis-configuration, or use of the service in a way not permitted by the Terms.
- Suspension or throttling under the Terms, for example for a reversed payment, abuse, or violation of the Terms.
- Beta, preview, or "early access" features clearly marked as such.
9. Claiming a service credit
To claim a credit for a month in which we missed the SLA:
- E-mail support@lekhabooks.in with the subject "SLA credit request", your company name, and the affected month.
- Send the claim within 30 days of the end of the affected month, so that we can check it against our monitoring records. Claims made later are not eligible for a service credit; this does not affect any other right you have under the Terms of Service or the law.
- Include the dates/times you experienced downtime if you have them; we reconcile against our monitoring records.
- We acknowledge within 2 business days and confirm the credit (or explain why the SLA was met) within 7 business days. Approved credits are applied to your account and reduce your next renewal invoice.
10. Changes & contact
We may update this SLA from time to time. Material reductions in commitments will be announced by e-mail at least 30 days before they take effect; improvements (for example raising the uptime target after our infrastructure migration) may take effect immediately with a version bump on this page.
Version 1.2 (15 November 2026): backup retention described as in the Privacy Policy (our own daily backup 14 days, encrypted off-site copy 30 days); export menu name corrected to Settings → Data & Backup; "non-payment" replaced by "reversed payment", because plans are prepaid; late-claim sentence clarified.
Billing: billing@lekhabooks.in
Lekha Logic Consulting Private Limited
This SLA should be read together with our Terms of Service, Privacy Policy and Refund Policy.