Compliance Roadmap
Version: 1.0.0
Last Updated: 12 August 2026
Status: Public
Table of Contents
- Purpose
- At a Glance
- Current Compliance Position
- Privacy Framework
- Security Program
- Current Platform Capabilities
- Certifications
- Planned Improvements
- Long-Term Roadmap
- Customer Requests
- Related Documentation
- Contact Information
- Document Governance
- Version History
1. Purpose
Qmova is committed to continuously improving the privacy, security, and operational maturity of its platform.
This Compliance Roadmap provides transparency into:
- our current compliance posture;
- security capabilities already implemented;
- initiatives that are planned;
- certifications that are under consideration.
This document is intended to help Customers understand where Qmova is today and where we intend to invest in future improvements.
2. At a Glance
Available Today
✅ Multi-tenant architecture
✅ Role-Based Access Control (RBAC)
✅ Tenant isolation
✅ Audit logging
✅ HTTPS/TLS encryption
✅ Secure authentication
✅ Google OAuth
✅ Email authentication
✅ One-Time Password (OTP)
✅ Customer-owned WhatsApp architecture
✅ Privacy documentation
✅ Data Processing Addendum (DPA)
✅ Data Retention Policy
✅ Security Policy
✅ Responsible Disclosure Policy
✅ Trust Center
Planned
- Expanded security monitoring
- Centralized status page
- Additional audit capabilities
- Enhanced administrative controls
- Customer-managed API keys
- SSO (Enterprise)
- SCIM provisioning
- Additional regional hosting options
- Compliance automation
Not Currently Certified
At the time of publication, Qmova does not claim certification for:
- SOC 2
- ISO/IEC 27001
- HIPAA
- PCI DSS
If certifications are obtained in the future, this page will be updated.
3. Current Compliance Position
Qmova has been designed with internationally recognized privacy and security principles in mind.
Our documentation and platform architecture consider requirements commonly associated with:
- POPIA
- GDPR principles
- general SaaS security best practices
Compliance obligations ultimately depend on each Customer's own legal, regulatory, and contractual requirements.
4. Privacy Framework
Qmova maintains documentation covering:
- Privacy Policy
- Cookie Policy
- Data Processing Addendum
- Data Retention Policy
- Acceptable Use Policy
These documents work together to explain how Customer Data is processed, protected, retained, and managed.
5. Security Program
Current security capabilities include:
- encrypted communications using HTTPS/TLS;
- password hashing;
- secure authentication;
- role-based permissions;
- tenant isolation;
- audit logging;
- session management;
- infrastructure monitoring;
- backup procedures;
- responsible vulnerability disclosure.
Security controls evolve continuously as the platform develops.
6. Current Platform Capabilities
Qmova currently supports operational security features including:
- Workspace isolation
- User roles
- Audit history
- Authentication via Google OAuth
- Email login
- One-Time Password authentication
- Visit lifecycle tracking
- QR Check-in
- Queue management
- Appointment management
- Notification infrastructure
Customers remain responsible for configuring appropriate permissions within their own Workspaces.
7. Certifications
Current Position
Qmova is currently building its security and compliance program.
At this time we do not claim certification for:
- SOC 2
- ISO/IEC 27001
- ISO/IEC 27701
- HIPAA
- PCI DSS
We believe transparency is preferable to overstating compliance maturity.
Future Certifications
As Qmova grows, we may evaluate certifications based on customer demand and operational readiness.
Potential future initiatives include:
- SOC 2 Type II
- ISO/IEC 27001
- ISO/IEC 27701
These initiatives are aspirational and should not be interpreted as commitments or timelines.
8. Planned Improvements
Areas currently under consideration include:
Identity & Access
- Enterprise SSO
- SCIM
- Additional MFA options
Infrastructure
- Expanded monitoring
- Regional hosting options
- Disaster recovery enhancements
Security
- Additional penetration testing
- Automated security scanning
- Improved security dashboards
Privacy
- Expanded privacy controls
- Additional data export capabilities
- Enhanced retention management
Administration
- Additional audit reporting
- Improved administrative controls
- More granular permissions
Implementation priorities may change based on customer feedback, technical considerations, and business requirements.
9. Long-Term Roadmap
Qmova aims to continue investing in:
- platform resilience;
- operational maturity;
- privacy engineering;
- security automation;
- enterprise administration;
- customer transparency;
- documentation.
Future investments will be guided by:
- customer needs;
- regulatory developments;
- platform growth;
- industry best practices.
10. Customer Requests
Enterprise Customers often have specific security or compliance requirements.
Where appropriate, Qmova welcomes discussions regarding:
- security questionnaires;
- procurement reviews;
- privacy assessments;
- data processing requirements;
- contractual commitments.
Additional documentation may be provided under appropriate confidentiality arrangements.
11. Related Documentation
Trust
- Trust Center
- Security Policy
- Responsible Disclosure Policy
- Subprocessor List
Privacy
- Privacy Policy
- Cookie Policy
- Data Processing Addendum
- Data Retention Policy
Legal
- Terms of Service
- Service Level Agreement
- Acceptable Use Policy
12. Contact Information
Compliance
legal@qmova.com
Privacy
privacy@qmova.com
Security
security@qmova.com
General Support
support@qmova.com
13. Document Governance
Document Owner: Privacy, Security & Compliance
Classification: Public
Review Frequency: At least annually or whenever Qmova's compliance posture, certifications, or security program changes.
This roadmap is provided for transparency only. It is not a contractual commitment, product guarantee, or certification statement.
14. Version History
| Version | Date | Summary | |---------|------|---------| | 1.0.0 | 12 August 2026 | Initial Compliance Roadmap |
Qmova is committed to steadily improving its security, privacy, and operational maturity through transparent documentation, responsible engineering, and continuous investment in enterprise-ready capabilities.