Service Level Agreement (SLA)
Version: 1.0.0
Last Updated: 12 August 2026
Status: Public
Table of Contents
- At a Glance
- Purpose
- Scope
- Definitions
- Service Availability
- Planned Maintenance
- Emergency Maintenance
- Support
- Incident Management
- Customer Responsibilities
- Backups and Disaster Recovery
- Security
- Service Limitations
- Third-Party Dependencies
- Communication
- SLA Exclusions
- Changes to this Agreement
- Related Documentation
- Contact Information
- Document Governance
- Version History
1. At a Glance
This Service Level Agreement explains how Qmova operates and supports the platform.
It describes:
- how we approach platform availability;
- planned and emergency maintenance;
- incident management;
- customer support expectations;
- backup and recovery practices;
- responsibilities shared between Qmova and Customers.
Unless otherwise agreed in writing, this SLA is informational and applies to the standard Qmova service.
Enterprise Customers may have separately negotiated service commitments.
2. Purpose
This SLA establishes Qmova's operational commitments and explains how we deliver and maintain the Services.
It should be read together with:
- Terms of Service
- Security Policy
- Trust Center
- Data Processing Addendum (DPA)
3. Scope
This SLA applies to:
- Qmova web application;
- APIs;
- authentication;
- Visit management;
- Appointment scheduling;
- Queue management;
- QR Check-in;
- analytics;
- notifications.
It does not apply to:
- Customer-owned infrastructure;
- Customer internet connectivity;
- third-party software outside Qmova's control;
- Customer-managed integrations.
4. Definitions
Availability means the ability to access the Qmova Services.
Incident means an unplanned interruption or degradation of the Services.
Maintenance means planned or emergency work performed on the platform.
Customer means the organization using Qmova.
Workspace means a Customer's tenant within Qmova.
5. Service Availability
Qmova is designed for reliable operation and continuous improvement.
We implement measures including:
- infrastructure monitoring;
- application health checks;
- logging and alerting;
- redundancy where appropriate;
- backup procedures;
- security monitoring.
Qmova does not guarantee uninterrupted or error-free operation.
Availability may occasionally be affected by:
- maintenance;
- infrastructure failures;
- internet connectivity;
- third-party provider outages;
- security incidents;
- events outside our reasonable control.
Where a formal uptime commitment is agreed with an Enterprise Customer, it will be documented separately.
6. Planned Maintenance
From time to time, Qmova performs planned maintenance to:
- deploy improvements;
- apply security updates;
- upgrade infrastructure;
- improve reliability.
Where reasonably practicable, planned maintenance will be scheduled to minimize customer disruption.
7. Emergency Maintenance
Emergency maintenance may be required to:
- address critical security vulnerabilities;
- restore service;
- protect Customer Data;
- respond to infrastructure failures.
Emergency maintenance may occur without advance notice where necessary.
8. Support
Customers may contact:
- support@qmova.com
- security@qmova.com (security issues)
- privacy@qmova.com (privacy requests)
- legal@qmova.com (legal matters)
Support is provided on a reasonable-efforts basis unless otherwise agreed in writing.
Response times may vary depending on:
- issue severity;
- complexity;
- available information;
- business hours.
9. Incident Management
When a significant incident occurs, Qmova aims to:
- identify the issue;
- investigate the cause;
- mitigate customer impact;
- restore service;
- verify stability;
- perform post-incident review where appropriate.
Where appropriate, affected Customers may receive updates regarding major service disruptions.
10. Customer Responsibilities
Customers are responsible for:
- maintaining accurate account information;
- protecting their credentials;
- assigning appropriate Workspace permissions;
- complying with the Acceptable Use Policy;
- maintaining their own internet connectivity;
- exporting operational data where required;
- configuring Customer-owned integrations.
Customers are also responsible for the information they choose to store in Qmova.
11. Backups and Disaster Recovery
Qmova maintains backup and recovery procedures designed to support business continuity.
Backups are intended for disaster recovery and operational resilience.
Backup systems are not intended to function as a customer archive.
Deletion of Customer Data from production systems does not necessarily result in immediate deletion from backup media.
Further information is available in the Data Retention Policy.
12. Security
Qmova applies administrative, technical, and organizational safeguards appropriate to the Services.
Examples include:
- HTTPS/TLS encryption;
- secure authentication;
- Role-Based Access Control (RBAC);
- tenant isolation;
- audit logging;
- infrastructure monitoring;
- password hashing;
- secure session management.
Additional information is available in the Security Policy and Trust Center.
13. Service Limitations
Qmova's Services depend on third-party infrastructure and internet connectivity.
Accordingly, Qmova cannot guarantee uninterrupted access under all circumstances.
Examples include:
- cloud provider outages;
- ISP failures;
- DNS failures;
- force majeure events;
- widespread internet disruptions.
14. Third-Party Dependencies
Certain functionality relies on third-party providers, including:
- authentication;
- email delivery;
- cloud infrastructure;
- WhatsApp connectivity.
Service availability may therefore be affected by outages experienced by these providers.
A current list of providers is available in the Subprocessor List.
15. Communication
Where practical, Qmova will communicate significant operational events through appropriate channels.
Examples include:
- maintenance notices;
- security notifications;
- incident updates;
- policy changes.
Communication methods may include:
- email;
- in-product notifications;
- documentation updates.
16. SLA Exclusions
This SLA does not apply to interruptions caused by:
- Customer misuse;
- unsupported configurations;
- Customer-developed integrations;
- Customer-owned infrastructure;
- force majeure events;
- actions prohibited by the Acceptable Use Policy.
17. Changes to this Agreement
Qmova may update this SLA from time to time to reflect:
- operational improvements;
- platform changes;
- infrastructure changes;
- legal requirements;
- support process improvements.
Material updates will be reflected by a new version number and publication date.
18. Related Documentation
This SLA should be read together with:
Legal
- Terms of Service
- Privacy Policy
- Acceptable Use Policy
- Refund & Cancellation Policy
Trust
- Trust Center
- Security Policy
- Responsible Disclosure Policy
- Subprocessor List
Compliance
- Data Processing Addendum (DPA)
- Data Retention Policy
- AI Usage Policy
- Compliance Roadmap
19. Contact Information
General Support
support@qmova.com
Security
security@qmova.com
Privacy
privacy@qmova.com
Legal
legal@qmova.com
20. Document Governance
Document Owner: Operations & Security
Classification: Public
Review Frequency: At least annually or whenever significant operational changes occur.
This SLA describes Qmova's standard operational practices. It does not create additional contractual obligations beyond those expressly agreed in a separate written agreement.
21. Version History
| Version | Date | Summary | |---------|------|---------| | 1.0.0 | 12 August 2026 | Initial Service Level Agreement |
Qmova is committed to operating a reliable, secure, and resilient Visit Management Platform through continuous improvement, proactive monitoring, and transparent communication with Customers.