QEMRA legal
Service Availability Terms
This document explains the rules, responsibilities, and protections that apply when you use QEMRA.
1. Standard service level
QEMRA standard plans are provided on a best-effort availability basis.
There is no fixed public uptime SLA for standard plans. Any contractual SLA must be separately agreed in a signed enterprise agreement.
2. Dependencies
QEMRA depends on providers and networks including Meta/WhatsApp, Cashfree, Vercel, Railway, MongoDB Atlas, OpenAI, Resend, PostHog, telecom networks and internet providers.
An incident affecting those providers may affect QEMRA.
3. Maintenance
QEMRA may perform planned or emergency maintenance. Where practical, material planned maintenance likely to affect availability will be communicated in advance.
Emergency security or reliability work may occur without advance notice.
4. Incident communication
Material service incidents may be posted at https://status.qemra.vmnexa.co.in.
The status page is intended to show approximately 6 months of incident/outage history.
5. Recovery
QEMRA uses monitoring, backups, retries and recovery controls appropriate to the service. No recovery objective is guaranteed unless expressly stated in a signed enterprise agreement.
6. Force majeure
QEMRA is not liable for delay or failure caused by events outside reasonable control, including major cloud or telecom outages, natural disasters, government actions, war, civil disturbance, strikes or widespread internet disruption.
7. Third-party messaging
Message delivery, read status, template approval and account eligibility are controlled in part by Meta/WhatsApp and telecommunications infrastructure.
QEMRA cannot guarantee message delivery or platform access.
8. Enterprise terms
An enterprise customer may negotiate uptime targets, support priority, service credits, recovery commitments or incident-response terms through a separate signed Business Customer Agreement.