Qmova Privacy Policy
Version: 1.0.0 Last Updated: 12 August 2026 Status: Public Intended Audience: Visitors to Qmova websites, Qmova Users, Customers, Visitors using Customer Workspaces, and other individuals whose Personal Information is processed by Qmova
Table of Contents
- At a Glance
- Scope
- Who We Are
- How Qmova Uses Personal Information
- Qmova's Role in Processing
- The Qmova Data Flow
- Personal Information We Collect
- Information We Do Not Intentionally Require
- How We Collect Personal Information
- Purposes of Processing
- Legal Bases for Processing
- Customer Data and Customer Responsibilities
- Customer-Owned WhatsApp
- Google OAuth
- Email and OTP Authentication
- Cookies and Similar Technologies
- Analytics
- Artificial Intelligence
- Automated Decision-Making and Profiling
- Sharing Personal Information
- Subprocessors
- International Data Transfers
- Data Residency
- Security
- Security Logs and Audit Records
- Data Retention
- Account Deletion and Data Deletion
- Customer Data Exports
- Privacy Rights
- How to Exercise Your Rights
- Children
- Healthcare and Sensitive Information
- Data Breach and Security Incident Response
- Third-Party Services
- Business Transfers
- Changes to this Privacy Policy
- Contact Information
- Related Documentation
- Document Governance
- Version History
1. At a Glance
Qmova is a Visit Management Platform that helps organizations manage customer interactions from booking through completion.
In simple terms:
- We do not sell Personal Information.
- Customers control the Customer Data they place in their Qmova Workspace.
- Qmova generally processes Customer Data on behalf of the Customer.
- Qmova may process certain information for its own purposes, including account administration, security, billing, support, and operation of the Qmova service.
- Customers connect their own WhatsApp infrastructure. Qmova does not own Customer WhatsApp numbers or use a shared Qmova-owned WhatsApp identity for Customer messaging.
- We use third-party providers to operate specific parts of the service, such as authentication, email, hosting, and messaging infrastructure.
- We use security controls including authentication, authorization, RBAC, tenant isolation, audit logging, session controls, monitoring, and encryption in transit.
- You may have rights to access, correct, delete, restrict, object to, or otherwise control the use of your Personal Information depending on applicable law.
- Customers remain responsible for their own legal obligations when using Qmova to collect and process Visitor information.
- Qmova is not an Electronic Health Record (EHR) system. Healthcare Customers remain responsible for determining what information they store and for complying with applicable healthcare laws.
This section is intended to make the policy easier to understand. It does not replace the detailed provisions below.
2. Scope
This Privacy Policy explains how Qmova processes Personal Information in connection with:
- the Qmova website;
- the Qmova Platform;
- Qmova Workspaces;
- user accounts;
- authentication;
- customer support;
- documentation services;
- APIs;
- integrations operated or supported by Qmova;
- security and fraud-prevention activities;
- communications from Qmova; and
- other services that expressly link to this Privacy Policy.
This Privacy Policy applies to information that Qmova processes as a Data Controller and, where relevant, explains how Qmova processes information as a Data Processor on behalf of Customers.
This Privacy Policy does not replace the privacy policies of third-party services used by Customers or Visitors.
Where a Customer uses Qmova to process information about its own customers, patients, students, citizens, guests, or other individuals, that Customer may have its own privacy notice and legal obligations.
3. Who We Are
Qmova is a Visit Management Platform operated by a company to be incorporated in South Africa.
Qmova is designed to serve Customers internationally.
The following corporate details will be published once finalized:
- Registered legal name
- Company registration number
- Registered office
- VAT registration details, where applicable
For privacy-related questions:
For legal matters:
4. How Qmova Uses Personal Information
Qmova processes Personal Information for purposes such as:
- providing and operating the Platform;
- creating and managing accounts;
- authenticating Users;
- maintaining Workspace access;
- managing Visits;
- managing Appointments;
- supporting Walk-ins;
- operating Queues;
- enabling QR Check-in;
- delivering notifications;
- providing analytics;
- providing Customer support;
- securing the Platform;
- detecting abuse and unauthorized activity;
- maintaining audit records;
- administering subscriptions and billing;
- complying with legal obligations;
- enforcing agreements; and
- improving the reliability and functionality of the Platform.
We do not sell Personal Information.
5. Qmova's Role in Processing
Qmova may act in different privacy roles depending on the information and purpose involved.
5.1 Qmova as Data Controller
Qmova generally acts as a Data Controller when it determines the purposes and means of processing information for its own business and operational purposes.
Examples may include:
- Qmova account registration;
- Qmova website operations;
- security monitoring;
- fraud prevention;
- customer support;
- billing;
- legal compliance;
- platform administration;
- direct communications from Qmova.
5.2 Qmova as Data Processor
Qmova generally acts as a Data Processor where a Customer determines why and how Customer Data is processed and Qmova processes that information to provide the Platform.
Examples may include:
- Visitor contact information;
- Appointment information;
- Walk-in records;
- Queue records;
- Visit records;
- Service information;
- Staff information;
- notification information;
- Customer-configured operational notes.
The distinction between controller and processor depends on the actual processing activity and applicable law. Under GDPR principles, the controller determines the purposes and means of processing, while a processor processes Personal Information on behalf of the controller.
Where Qmova acts as a Processor, the Customer remains responsible for the underlying processing decisions and generally for responding to requests from its own data subjects.
6. The Qmova Data Flow
A simplified Qmova data flow is:
Visitor
│
│ Appointment / Walk-in / Queue / Referral
▼
Customer Workspace
│
▼
Qmova Platform
│
├── Visit Management
├── Appointment Scheduling
├── Queue Management
├── QR Check-in
├── Notifications
├── Analytics
└── Audit Records
│
▼
Qmova Infrastructure
│
├── PostgreSQL
├── Redis
└── Real-Time Services
│
▼
Supported External Services
│
├── Google OAuth
├── Brevo
└── Customer-Connected WhatsApp Infrastructure
Who controls each part depends on the processing context:
| Component | Primary responsibility | | -------------------- | --------------------------------------------------------------------------------------------------- | | Visitor | Provides information when interacting with a Customer | | Customer | Determines the purpose and business context of Customer Data | | Qmova | Operates the Platform and processes Customer Data according to the applicable Customer relationship | | Third-party provider | Provides the specific external service under its own contractual and security framework |
The exact data flow depends on the Customer's configuration and the Qmova features used.
7. Personal Information We Collect
The information Qmova processes depends on how the Platform is used.
7.1 Account Information
For Qmova Users, we may process:
- name;
- email address;
- account identifier;
- profile information;
- authentication information;
- account preferences;
- Workspace memberships.
7.2 Authentication Information
Depending on the authentication method, we may process:
- email address;
- authentication provider identifier;
- one-time authentication codes;
- authentication events;
- session information.
We do not intentionally store passwords in plain text.
7.3 Customer and Workspace Information
Customers may provide:
- organization name;
- business details;
- Locations;
- Services;
- Staff Members;
- Workspace configuration;
- operating settings.
7.4 Visitor and Visit Information
A Customer may use Qmova to process:
- Visitor name;
- email address;
- telephone number;
- WhatsApp number;
- Appointment information;
- Visit information;
- Queue information;
- Check-in information;
- Service selected;
- Location;
- timestamps;
- Staff assignment;
- Visit status;
- operational notes.
The specific information collected is determined by the Customer.
7.5 Technical and Security Information
We may automatically process:
- IP address;
- browser information;
- operating system;
- device information;
- approximate geographic information derived from technical data where necessary;
- login timestamps;
- session identifiers;
- failed login attempts;
- security events;
- error information;
- API activity where necessary for security or debugging.
7.6 Usage Information
We may process information about how the Platform is used, such as:
- feature usage;
- configuration changes;
- account activity;
- administrative actions;
- API usage;
- operational events;
- audit events.
7.7 Payment Information
When a Customer utilizes Qmova's direct-to-tenant payment features (Stripe Connect integration), End-Users may provide payment information (e.g., credit card details) to facilitate a booking or multi-step workflow.
- Qmova does not collect, store, or process full credit card numbers or raw payment data.
- Payment processing is handled directly by Stripe and the respective Customer (Tenant).
- Qmova only receives and stores payment metadata necessary for tracking the transaction status, such as Stripe payment intent IDs, currency, amount charged, and the masked payment method type.
8. Information We Do Not Intentionally Require
Qmova is designed as a Visit Management Platform rather than a general-purpose repository for every category of personal information.
We do not intentionally require Customers to provide information such as:
- biometric identifiers;
- genetic information;
- criminal history;
- political opinions;
- religious beliefs;
- trade union membership;
- government identification numbers;
- detailed medical records.
However, Customers may choose to enter additional information into fields or operational notes where Qmova functionality permits it.
Customers are responsible for determining whether the information they choose to enter is necessary, lawful, and appropriate.
9. How We Collect Personal Information
We may collect Personal Information:
- directly from you;
- from a Customer using Qmova;
- when you create or use a Qmova account;
- through authentication providers;
- through Customer-configured forms and workflows;
- through QR Check-in;
- through APIs;
- through connected integrations;
- through support communications;
- automatically through cookies and similar technologies;
- through security and operational logs.
Where Qmova processes Customer Data as a Processor, the Customer may collect information directly from Visitors and submit it to Qmova.
10. Purposes of Processing
We may process Personal Information for the following purposes.
| Purpose | Examples | | -------------------- | ------------------------------------------------------------------------- | | Platform operation | Providing Visits, Appointments, Queues, Check-ins and other functionality | | Authentication | Account login, identity verification and session management | | Security | Preventing unauthorized access, abuse and attacks | | Customer support | Responding to support requests | | Communications | Service notifications, transactional messages and account communications | | Analytics | Understanding Platform usage and operational performance | | Billing | Managing subscriptions and payments | | Compliance | Meeting legal and contractual obligations | | Auditing | Maintaining relevant security and administrative records | | Platform improvement | Reliability, performance and feature improvement |
We will not use Customer Data for unrelated purposes that are incompatible with the applicable Customer relationship.
11. Legal Bases for Processing
Where GDPR or another jurisdiction requires a specific legal basis, Qmova may rely on one or more applicable legal bases, including:
Contract
Processing may be necessary to provide the Qmova service requested under an agreement.
Examples include:
- account creation;
- authentication;
- Workspace management;
- Visit management;
- service delivery;
- Customer support.
Legal Obligation
Processing may be necessary to comply with a legal obligation.
Legitimate Interests
Where permitted by applicable law, Qmova may process information where necessary for legitimate interests such as:
- security;
- fraud prevention;
- service improvement;
- protecting the Platform;
- enforcing agreements.
Where relying on legitimate interests, Qmova considers relevant privacy impacts and the rights and interests of affected individuals.
Consent
Where consent is the legally required basis, Qmova will seek consent in an appropriate manner and will provide mechanisms to withdraw consent where required.
Vital Interests
Where applicable law recognizes this basis, information may be processed to protect vital interests.
Customers are responsible for determining the lawful basis for their own processing of Customer Data.
12. Customer Data and Customer Responsibilities
Customers decide what Customer Data they collect through Qmova and why they collect it.
Customers are responsible for:
- having an appropriate legal basis;
- providing required privacy notices;
- obtaining required consents;
- collecting only information appropriate for their purposes;
- configuring access appropriately;
- responding to data-subject requests;
- establishing appropriate retention rules;
- complying with applicable industry requirements.
Qmova provides the infrastructure and functionality used to process Customer Data but does not determine the Customer's underlying business purpose.
Where Customer Data is processed by Qmova as a Processor, the applicable Data Processing Addendum provides additional contractual protections and obligations.
13. Customer-Owned WhatsApp
Qmova uses a Customer-owned model for supported WhatsApp workflows.
The architecture is:
Customer
│
│ Owns and controls
▼
Customer WhatsApp Environment
│
│ Customer-authorized connection
▼
Evolution API
│
▼
Qmova
│
▼
Customer Visit Workflow
This means:
- the Customer owns its WhatsApp number;
- the Customer controls its WhatsApp environment;
- the Customer determines which messages are sent;
- Qmova does not own the Customer's WhatsApp number;
- Qmova does not use a shared Qmova-owned WhatsApp identity for Customer messaging;
- Qmova provides infrastructure supporting the Customer's messaging workflows;
- the Customer remains responsible for its messaging practices and applicable WhatsApp requirements.
Qmova does not become the owner of Customer conversations merely because the Customer connects its WhatsApp environment to the Platform.
A Customer may disconnect its supported WhatsApp integration according to the available product functionality.
14. Google API Services and Integrations
Qmova supports Google OAuth as an authentication option and integrates with Google APIs (including Google Calendar and Google Business Profile) to provide core Visit Management functionality.
14.1 Authentication (Google OAuth)
When you choose Google authentication, Qmova receives the information made available through the applicable Google authentication flow to establish or authenticate your Qmova account. Depending on the Google authentication flow and provider response, this may include:
- your name;
- email address;
- profile information;
- a Google account identifier.
14.2 Google API Integrations (Calendar and Business Profile)
To provide our core services, Customers may optionally authorize Qmova to access their Google Calendar and Google Business Profile data.
- Google Calendar API: Qmova requests access to view, create, and edit calendar events to synchronize Qmova Appointments with your Google Calendar, check your availability, and prevent double-booking.
- Google Business Profile API: Qmova requests access to manage your business location data and services to synchronize your operational Locations and Services directly within the Qmova Workspace.
14.3 Limited Use Disclosure
Qmova is committed to protecting your data and strictly limits the use of information obtained through Google APIs.
Qmova's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Specifically:
- Allowed Use: We only use the data obtained via Google APIs to provide and improve the Qmova Visit Management, Appointment scheduling, and location synchronization features.
- No Third-Party Sharing for Advertising: We do not use or share Google user data for advertising purposes. We will not sell your Google data to third parties.
- Human Access: We do not allow humans to read your Google data unless we have your affirmative agreement for specific messages, doing so is necessary for security purposes such as investigating abuse, to comply with applicable law, or for the App's internal operations and even then only when the data has been aggregated and anonymized.
14.4 Data Retention and Revocation
Google data synced to Qmova (such as calendar events and location details) is stored securely within our infrastructure to facilitate real-time queue and appointment management. You can revoke Qmova's access to your Google account at any time via your Google Account Security Settings. Upon revoking access or disconnecting the integration within Qmova, Qmova will securely delete the synced Google Calendar and Business Profile data from our active systems in accordance with our data retention policies.
Google independently processes information under Google's own privacy practices and terms.
15. Email and OTP Authentication
Qmova may provide authentication using email and one-time passwords (OTP).
A simplified flow is:
User
│
▼
Qmova Authentication
│
▼
OTP Generated
│
▼
Brevo
│
▼
User Email
│
▼
OTP Verification
│
▼
Authenticated Qmova Session
Brevo is used as an external email-delivery service for supported OTP and transactional email functions.
Authentication events may be logged for security and operational purposes.
16. Cookies and Similar Technologies
Qmova may use Cookies and similar technologies for:
- authentication;
- security;
- remembering preferences;
- core functionality;
- analytics;
- other purposes disclosed at the time of collection.
Where applicable, Qmova provides a cookie preference mechanism that allows users to manage categories of non-essential Cookies.
The Qmova Cookie Policy explains:
- which Cookie categories we use;
- why we use them;
- how long they may remain active;
- how preferences can be changed.
Where consent is legally required, non-essential Cookies will not be activated before the applicable consent is obtained.
17. Analytics
Qmova may use analytics to understand:
- service performance;
- feature usage;
- website usage;
- Platform reliability;
- operational behavior;
- product adoption.
Analytics may involve aggregated, pseudonymized, or other technical information depending on the service involved.
Where analytics technologies require consent under applicable law, Qmova will respect the applicable consent choice.
Customer-facing operational analytics are primarily generated for the Customer's own Workspace and should not be interpreted as Qmova using Customer Data for unrelated commercial purposes.
18. Artificial Intelligence
Qmova may introduce or provide features that use artificial intelligence or machine-learning technologies.
Where such features exist, Qmova intends to:
- disclose the relevant functionality;
- use AI for defined product or operational purposes;
- maintain appropriate human oversight where appropriate;
- avoid representing AI output as guaranteed accurate;
- provide additional information through the Qmova AI Usage Policy.
Qmova does not intentionally use Customer Data to train general-purpose public AI models unless the applicable agreement or documentation expressly permits such processing.
Future AI functionality that has not yet been implemented should be treated as Roadmap or Planned rather than current functionality.
19. Automated Decision-Making and Profiling
Qmova may automate operational processes such as:
- Queue updates;
- notification delivery;
- Appointment reminders;
- Visit state transitions;
- workflow calculations.
Such automation is intended to support Customer operations.
Qmova does not intentionally make decisions producing legal or similarly significant effects about individuals solely through automated processing as part of the ordinary Platform.
Where future features involve materially significant automated decision-making or profiling, the applicable processing and safeguards will be documented separately.
20. Sharing Personal Information
Qmova may disclose Personal Information where reasonably necessary to operate the Platform or satisfy legal obligations.
This may include sharing information with:
Infrastructure and Service Providers
Providers that support:
- cloud hosting;
- storage;
- authentication;
- email;
- messaging;
- monitoring;
- security;
- support;
- other platform infrastructure.
Customer-Directed Integrations
Where a Customer enables an integration, information may be transmitted to that third-party service according to the Customer's configuration and the integration's functionality.
Legal and Regulatory Authorities
Qmova may disclose information where required by applicable law, lawful court order, regulatory requirement, or other legally valid request.
Professional Advisers
Where reasonably necessary, information may be disclosed to professional advisers such as legal, financial, or security advisers subject to appropriate confidentiality obligations.
Business Transactions
Information may be transferred in connection with a merger, acquisition, financing, reorganization, or sale of relevant assets, subject to applicable legal requirements.
We do not sell Personal Information.
21. Subprocessors
Qmova may engage third-party organizations to process Customer Data on Qmova's behalf.
Examples of service categories include:
- authentication;
- transactional email;
- WhatsApp connectivity;
- payment processing;
- hosting;
- storage;
- infrastructure;
- monitoring.
The current Subprocessor List is maintained separately and identifies applicable third-party subprocessors.
Examples of technologies used by the Qmova application include PostgreSQL and Redis. A technology component is not itself automatically a Subprocessor. Where Qmova uses a third-party managed service that processes Personal Information, the relevant provider is evaluated for inclusion in the Subprocessor List.
22. International Data Transfers
Qmova serves Customers internationally and uses infrastructure and providers that may operate across multiple jurisdictions.
As a result, Personal Information may be processed outside the country where it was originally collected.
Where GDPR applies, transfers of Personal Information outside the European Economic Area are subject to the transfer mechanisms and safeguards required by applicable law. These may include an adequacy decision or appropriate contractual safeguards such as the European Commission's Standard Contractual Clauses where applicable.
Where POPIA applies, Qmova will consider the requirements applicable to transfers of Personal Information outside South Africa and implement appropriate safeguards as required. POPIA contains specific requirements concerning transborder flows of Personal Information.
The exact mechanism applicable to a transfer depends on the parties, jurisdictions, processing activity, and applicable law.
23. Data Residency
Qmova uses cloud infrastructure and third-party services to operate the Platform.
Accordingly, Personal Information may be stored or processed in jurisdictions selected by Qmova or its infrastructure providers.
Qmova does not represent that all Customer Data is permanently stored in South Africa or in a single geographic region unless a specific contractual commitment expressly provides otherwise.
The location of processing may change as Qmova:
- scales infrastructure;
- changes providers;
- introduces new services;
- improves resilience;
- supports additional geographic markets.
Customers requiring specific data-residency commitments should address those requirements through the applicable commercial and contractual process.
24. Security
Qmova maintains technical and organizational safeguards intended to protect Personal Information.
Depending on the system and processing activity, these measures may include:
- HTTPS/TLS encryption in transit;
- password hashing;
- authentication controls;
- session management;
- Role-Based Access Control;
- tenant isolation;
- server-side authorization;
- audit logging;
- rate limiting;
- infrastructure monitoring;
- security logging;
- backup strategies;
- access controls.
Qmova does not claim that any security measure can eliminate all risk.
Further information is available in the Qmova Security Overview, Security Policy, and Trust Center.
25. Security Logs and Audit Records
Qmova may record technical and administrative events necessary for security, accountability, troubleshooting, and service operation.
Examples include:
- login timestamps;
- successful authentication;
- failed authentication attempts;
- IP addresses;
- session activity;
- policy acceptance;
- role changes;
- configuration changes;
- administrative actions;
- API requests where necessary;
- security events;
- system errors.
Logs are not retained indefinitely by default. Retention depends on the type of information, its operational purpose, legal requirements, security needs, and applicable retention policy.
Qmova does not treat operational logging as a license to inspect Customer content unnecessarily.
26. Data Retention
Qmova retains Personal Information only for as long as reasonably necessary for the purposes for which it was collected or processed, taking into account:
- contractual requirements;
- legal obligations;
- security and audit requirements;
- operational needs;
- dispute resolution;
- backup lifecycle;
- Customer configuration.
Retention periods therefore vary between data categories.
Examples include:
| Data Category | Retention Consideration | | ---------------------------- | ----------------------------------------------------------------------- | | Account information | Active account and applicable post-account period | | Authentication/security logs | Security and incident-investigation requirements | | Customer Data | Customer relationship and applicable contractual/retention requirements | | Audit records | Security, accountability and legal requirements | | Cookie preferences | Preference and consent-management requirements | | Backups | Applicable backup lifecycle |
Detailed retention periods will be maintained in the Qmova Data Retention Policy as those operational rules are finalized.
27. Account Deletion and Data Deletion
Where the applicable Qmova functionality supports account deletion, the deletion process is intended to follow a controlled lifecycle.
A simplified process is:
Deletion Request
│
▼
Identity / Authorization Check
│
▼
Applicable Grace or Retention Period
│
▼
Optional Data Export
│
▼
Deletion from Active Systems
│
▼
Applicable Secondary Systems
│
▼
Backup Expiration
│
▼
Deletion Lifecycle Complete
The exact deletion process depends on:
- account type;
- Workspace structure;
- Customer contractual terms;
- legal retention obligations;
- security or audit requirements;
- applicable backup systems.
Deletion from primary production systems does not necessarily mean that all backup copies disappear immediately.
Where Qmova is processing Customer Data as a Processor, a Customer's contractual deletion instructions and the applicable DPA may determine the deletion process.
28. Customer Data Exports
Customers may be able to export their operational information using Qmova's supported export functionality.
Depending on the feature and subscription, exports may include information such as:
- Workspace information;
- Visits;
- Appointments;
- Queue information;
- Services;
- other available operational records.
Export functionality may be subject to authentication, authorization, security controls, and reasonable technical limitations.
Where Qmova is acting as a Processor, Customer-directed exports are subject to the applicable Customer agreement and DPA.
29. Privacy Rights
Depending on where you are located and which law applies, you may have rights relating to your Personal Information.
These may include:
- right to be informed;
- right of access;
- right to correction;
- right to deletion or erasure where applicable;
- right to restriction of processing;
- right to object;
- right to data portability;
- right to withdraw consent where consent is the legal basis;
- rights relating to certain automated decision-making;
- right to lodge a complaint with a competent supervisory authority.
The GDPR provides rights including access, rectification, erasure, restriction, portability, and objection in applicable circumstances.
POPIA also provides Data Subject rights including access and correction/deletion mechanisms and allows complaints to be made to the South African Information Regulator.
Not every right applies in every circumstance.
A request may be subject to lawful limitations, exemptions, or requirements to verify identity.
30. How to Exercise Your Rights
For privacy requests relating to information Qmova controls directly, contact:
Please provide enough information for us to:
- understand the request;
- identify the relevant account or processing activity;
- verify your identity where necessary;
- respond appropriately.
Where the information relates to a Customer's processing of Customer Data, you should generally contact the relevant Customer first because the Customer may be the Data Controller.
Qmova will provide reasonable assistance to Customers where required under applicable law and contractual obligations.
For GDPR-covered requests, controllers generally must respond without undue delay and, where applicable, within the statutory time limit.
For POPIA-related requests, the South African Information Regulator provides mechanisms for access, correction, deletion, objection, and complaints.
31. Children
Qmova is not designed as a service directed specifically at children.
Customers may, however, operate services that are used by minors.
Where a Customer processes information relating to children through Qmova, the Customer is responsible for complying with applicable laws relating to children's Personal Information and obtaining any required permissions or consents.
Qmova does not intentionally use children's information for unrelated marketing purposes.
If you believe that Personal Information relating to a child has been provided to Qmova unlawfully, contact:
32. Healthcare and Sensitive Information
Qmova serves Customers in healthcare and other industries that may process sensitive information.
Qmova is a Visit Management Platform, not an Electronic Health Record (EHR) or clinical information system.
Customers may use Qmova to manage workflows such as:
- appointment booking;
- patient arrival;
- Queue management;
- Service allocation;
- Visit status;
- communication.
Customers remain responsible for deciding what information to place in Qmova and whether Qmova is appropriate for a particular regulated processing activity.
Customers should avoid placing unnecessary clinical information into Qmova.
Where a Customer chooses to process sensitive or special categories of Personal Information, the Customer remains responsible for:
- identifying the applicable legal requirements;
- establishing the appropriate legal basis;
- implementing required safeguards;
- providing required notices;
- managing access;
- complying with applicable healthcare or sector-specific regulation.
Qmova does not claim HIPAA compliance.
33. Data Breach and Security Incident Response
Qmova maintains processes for identifying, investigating, containing, remediating, and recovering from security incidents.
Where a confirmed incident affects Customer Data, Qmova will assess:
- what information was involved;
- which systems were affected;
- the nature and scope of the event;
- which Customers may be affected;
- contractual notification requirements;
- applicable legal notification obligations.
Where notification is legally or contractually required, Qmova will notify the appropriate Customer or other party without undue delay as required by the applicable obligation.
POPIA contains specific provisions concerning notification of security compromises, and applicable notification requirements will be assessed according to the circumstances of an incident.
Individuals may also contact Qmova regarding suspected privacy or security incidents:
34. Third-Party Services
Qmova relies on independent third-party services for selected parts of the Platform.
Examples include:
- Google for authentication;
- Brevo for OTP and transactional email;
- Evolution API for supported WhatsApp connectivity;
- cloud and infrastructure providers.
Third-party providers operate under their own contractual terms and privacy practices.
Where a third-party service is enabled or controlled directly by a Customer, the Customer is responsible for reviewing that provider's terms and privacy practices.
Qmova does not control third-party services merely because they are integrated with Qmova.
35. Business Transfers
If Qmova undergoes:
- a merger;
- acquisition;
- corporate restructuring;
- financing transaction;
- sale of assets; or
- similar corporate event,
Personal Information may be transferred as part of the transaction where legally permitted.
Where required, Qmova will take reasonable steps to ensure that Personal Information continues to receive appropriate protection.
36. Changes to this Privacy Policy
Qmova may update this Privacy Policy when:
- the Platform changes;
- our processing practices change;
- legal or regulatory requirements change;
- new services or integrations are introduced;
- our privacy practices are materially improved.
The version number and Last Updated date will be changed when a new version is published.
Where a change materially affects rights or obligations and applicable law requires notice or renewed consent, Qmova will provide the applicable notice or request.
Where Qmova's Platform requires renewed policy acceptance, the applicable policy version may be recorded against the User's account.
37. Contact Information
For privacy questions, requests, or concerns:
Privacy privacy@qmova.com
For security incidents and vulnerability reports:
Security security@qmova.com
For contractual or legal matters:
Legal legal@qmova.com
For general customer support:
Support support@qmova.com
For abuse reports:
Abuse abuse@qmova.com
Corporate registration and registered-office information will be published once finalized.
38. Related Documentation
This Privacy Policy should be read together with:
Trust and Security
- Qmova Trust Center
- Architecture Overview
- Security Overview
- Security Policy
- Responsible Disclosure Policy
- Subprocessor List
Legal
- Terms of Service
- Cookie Policy
- Data Processing Addendum
- Data Retention Policy
- Acceptable Use Policy
- Refund and Cancellation Policy
- Service Level Agreement
Compliance
- Compliance Roadmap
- Accessibility Statement
- AI Usage Policy
Product
- Qmova Glossary
- Visit Lifecycle
- Appointment Documentation
- Queue Documentation
- QR Check-in Documentation
Where another document provides more specific information about a particular processing activity, that document should be read together with this Privacy Policy.
39. Document Governance
Document Owner: Qmova Privacy & Legal Function
Classification: Public
Review Frequency: At least annually and whenever there is a material change to:
- applicable privacy law;
- Qmova's processing activities;
- Qmova's data architecture;
- subprocessors;
- authentication;
- messaging integrations;
- retention practices; or
- other material privacy practices.
This Privacy Policy describes Qmova's privacy practices as of the Last Updated date.
It does not create contractual commitments that are not otherwise contained in a binding agreement.
Where a Customer has a signed Data Processing Addendum or other applicable agreement with Qmova, the contractual terms govern the relevant relationship in the event of a conflict, subject to applicable law.
40. Version History
| Version | Date | Summary | | ------- | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 1.0.0 | 12 August 2026 | Initial publication incorporating Qmova's Visit-centric data model, Customer-owned WhatsApp architecture, authentication, security, retention, deletion, transfer, and privacy-rights framework |
41. Jurisdiction-Specific Privacy Rights
Depending on your region, you may have specific privacy rights.
41.1 California Residents (CCPA/CPRA)
Under the California Consumer Privacy Act (CCPA), California residents have specific rights regarding their personal information.
- No Sale or Sharing: Qmova does not "sell" or "share" Personal Information (as defined by the CCPA).
- Your Rights: You have the right to request access to the specific pieces of Personal Information we have collected about you, request deletion, and request correction. You will not receive discriminatory treatment for exercising these rights.
- Service Provider Role: When Qmova processes data on behalf of a Customer, we act as a "Service Provider". End-Users must submit CCPA requests directly to the Customer (Tenant).
41.2 European Economic Area (EEA) and United Kingdom (GDPR/UK GDPR)
- Data Subject Rights: If you are located in the EEA or the UK, you have the right to access, rectify, or erase your personal data; restrict or object to processing; and data portability.
- International Transfers: Data transferred outside the EEA/UK is protected by Standard Contractual Clauses (SCCs) or other legally approved transfer mechanisms.
Privacy Principle
Qmova's approach to privacy is simple: understand who controls the information, use it for a defined purpose, collect only what is appropriate, protect it with reasonable safeguards, retain it responsibly, and give individuals and Customers meaningful ways to exercise their rights.