Qmova Data Processing Addendum

Version: 1.0.0 Last Updated: 12 August 2026 Status: Public Intended Audience: Qmova Customers, enterprise procurement teams, privacy teams, legal teams, security teams, and authorized representatives


Table of Contents

  1. At a Glance
  2. Purpose and Scope
  3. Relationship to the Customer Agreement
  4. Definitions
  5. Roles of the Parties
  6. Processing Instructions
  7. Processing Details
  8. Categories of Personal Information
  9. Categories of Data Subjects
  10. Customer Responsibilities
  11. Qmova's Processing Obligations
  12. Confidentiality
  13. Security Measures
  14. Personnel Access
  15. Subprocessors
  16. Changes to Subprocessors
  17. International Data Transfers
  18. Assistance with Data Subject Requests
  19. Security Incidents
  20. Assistance with Compliance
  21. Audits and Assessments
  22. Government and Legal Requests
  23. Data Retention and Deletion
  24. Customer Data Export
  25. Return and Deletion Upon Termination
  26. Customer-Directed Integrations
  27. Customer-Owned WhatsApp
  28. Special Categories and Sensitive Information
  29. Artificial Intelligence
  30. Aggregated and De-identified Information
  31. Liability
  32. Order of Precedence
  33. Changes to This DPA
  34. Term and Termination
  35. Miscellaneous
  36. Contact Information
  37. Related Documentation
  38. Document Governance
  39. Version History
  40. Schedule 1 — Processing Details
  41. Schedule 2 — Security Measures
  42. Schedule 3 — Current Subprocessors

1. At a Glance

This Data Processing Addendum ("DPA") governs how Qmova processes Personal Information on behalf of a Customer where the Customer acts as the relevant Data Controller or equivalent Responsible Party.

In plain English:

  • The Customer determines why Customer Data is processed.
  • Qmova processes Customer Data to provide the Qmova Services.
  • Qmova will not use Customer Data for unrelated purposes except where permitted by this DPA, the Customer Agreement, or applicable law.
  • Qmova uses security measures designed to protect Customer Data.
  • Qmova may use approved Subprocessors to provide parts of the Services.
  • Qmova will provide reasonable assistance with applicable privacy requests, security incidents, and compliance obligations.
  • Customers remain responsible for their own legal basis, notices, consents, and processing decisions.
  • Customer Data can be exported where supported by the Services and applicable agreement.
  • Customer Data is subject to deletion and retention procedures following termination, subject to legal, security, and backup requirements.
  • International transfers are handled using safeguards required by applicable law.

This DPA is intended to establish the contractual processing framework. It does not replace the Customer's responsibility to comply with privacy laws applicable to its own processing.


2. Purpose and Scope

This Data Processing Addendum forms part of the agreement between Qmova and the Customer under which Qmova provides the Services.

It applies where Qmova processes Personal Information on behalf of the Customer.

This DPA is intended to establish the respective obligations of Qmova and the Customer regarding that processing.

For Customers subject to GDPR, this DPA is intended to address the processor-contract requirements of Article 28 of the GDPR.

For Customers subject to South African privacy law, this DPA is intended to support the contractual and security relationship between a Responsible Party and an Operator under POPIA.

Under GDPR, processor processing must be governed by a binding contract setting out matters including the subject matter and duration of processing, nature and purpose, types of Personal Information, categories of Data Subjects, and the parties' rights and obligations.

Under POPIA, an Operator processes Personal Information for a Responsible Party under a contract or mandate and must process it with the knowledge or authorization of the Responsible Party and maintain appropriate confidentiality and security safeguards.


3. Relationship to the Customer Agreement

This DPA supplements the agreement governing the Customer's use of Qmova (the "Customer Agreement").

The Customer Agreement may include:

  • Qmova Terms of Service;
  • an Order Form;
  • subscription terms;
  • enterprise agreement;
  • Service Level Agreement;
  • other written commercial terms.

This DPA applies specifically to the processing of Customer Data.

Where there is a conflict concerning data protection or processing obligations:

  1. applicable mandatory law governs;
  2. this DPA governs matters specifically concerning the processing of Customer Data;
  3. the Customer Agreement governs other commercial and service matters.

An executed enterprise agreement may expressly establish a different order of precedence.


4. Definitions

Capitalized terms used in this DPA have the meanings below.

Customer

The Customer is the organization that subscribes to or otherwise uses Qmova under the Customer Agreement.

Customer Data

Customer Data means information submitted to Qmova by or on behalf of the Customer for processing through the Services.

Data Controller

A Data Controller is the entity that determines the purposes and means of processing Personal Information.

Data Processor

A Data Processor is the entity that processes Personal Information on behalf of a Data Controller.

Responsible Party

Under POPIA terminology, a Responsible Party is the party that determines the purpose of and means for processing Personal Information.

Operator

Under POPIA terminology, an Operator is a person or organization that processes Personal Information for a Responsible Party in terms of a contract or mandate without coming under the direct authority of that Responsible Party.

Personal Information

Personal Information means information relating to an identified or identifiable natural person or equivalent information protected by applicable privacy legislation.

Data Subject

A Data Subject is an identified or identifiable individual whose Personal Information is processed.

Subprocessor

A Subprocessor is a third party appointed by Qmova to process Customer Data on Qmova's behalf in connection with providing the Services.

Services

The Services are the Qmova products and features made available to the Customer under the Customer Agreement.

Workspace

A Workspace is the Customer's logical operating environment within Qmova.


5. Roles of the Parties

5.1 Customer as Controller

For Customer Data processed according to the Customer's instructions and purposes, the Customer is generally the Data Controller or equivalent Responsible Party.

The Customer determines:

  • the purpose of processing;
  • categories of Personal Information;
  • categories of Data Subjects;
  • retention requirements;
  • lawful basis;
  • operational use of the information.

5.2 Qmova as Processor

Qmova generally acts as the Customer's Data Processor or Operator when processing Customer Data to provide the Services.

Qmova may process Customer Data to:

  • provide the Platform;
  • maintain the Platform;
  • provide Customer support;
  • secure the Platform;
  • prevent abuse;
  • perform requested integrations;
  • comply with applicable law;
  • fulfill this DPA and the Customer Agreement.

The parties' roles are determined by the facts and applicable law rather than solely by the labels in this DPA.


6. Processing Instructions

Qmova will process Customer Data only:

  • on the Customer's documented instructions;
  • as necessary to provide the Services;
  • as permitted by the Customer Agreement;
  • as permitted by this DPA; or
  • where required by applicable law.

If applicable law requires Qmova to process Customer Data in a manner that conflicts with the Customer's instructions, Qmova will, where legally permitted, inform the Customer before carrying out that processing.

Qmova will not intentionally determine new independent purposes for Customer Data in a manner that converts processing covered by this DPA into unrelated commercial use.

Where Qmova determines purposes and means independently for a separate processing activity, that activity will be addressed under the Qmova Privacy Policy or another applicable legal framework.


7. Processing Details

The processing performed under this DPA may include:

  • collection;
  • organization;
  • storage;
  • retrieval;
  • consultation;
  • use;
  • transmission;
  • modification;
  • analysis for Customer-configured operational purposes;
  • notification delivery;
  • deletion;
  • other processing necessary to provide the Services.

Processing may occur through:

  • Qmova's application;
  • APIs;
  • databases;
  • caching and real-time systems;
  • authentication systems;
  • notification systems;
  • Customer-connected integrations;
  • approved Subprocessors.

8. Categories of Personal Information

Depending on the Customer's use of Qmova, Customer Data may include:

Identity Information

  • name;
  • username;
  • Customer-defined identifier;
  • Staff Member identity;
  • Visitor identity.

Contact Information

  • email address;
  • telephone number;
  • WhatsApp number;
  • other Customer-provided contact details.

Visit Information

  • Visit records;
  • Appointment information;
  • Walk-in information;
  • Queue position;
  • Check-in records;
  • Visit status;
  • timestamps;
  • Service information;
  • Location information;
  • assigned Staff Member.

Operational Information

  • notes;
  • customer-provided form information;
  • workflow information;
  • notification status;
  • operational outcomes.

Technical Information

Where necessary for providing a Customer-configured workflow:

  • IP address;
  • browser or device information;
  • session information;
  • technical identifiers.

Customers determine the precise categories of Personal Information they choose to process through their Workspaces.


9. Categories of Data Subjects

Depending on the Customer's business and configuration, Data Subjects may include:

  • Visitors;
  • customers;
  • patients;
  • students;
  • citizens;
  • guests;
  • clients;
  • employees;
  • Staff Members;
  • contractors;
  • representatives;
  • other individuals whose information the Customer enters into Qmova.

The Customer is responsible for determining which Data Subjects are relevant to its processing activities.


10. Customer Responsibilities

The Customer is responsible for:

  • establishing a lawful basis for processing;
  • providing appropriate privacy notices;
  • obtaining required consent;
  • determining appropriate data collection practices;
  • ensuring that Personal Information is accurate where required;
  • responding to Data Subject requests;
  • establishing appropriate retention periods;
  • configuring access controls;
  • determining whether sensitive information should be processed;
  • complying with sector-specific requirements;
  • ensuring that its use of Qmova complies with applicable law.

The Customer must not instruct Qmova to process Customer Data in a manner that knowingly violates applicable law.


11. Qmova's Processing Obligations

Qmova will:

  • process Customer Data only as authorized;
  • maintain appropriate confidentiality obligations;
  • implement appropriate technical and organizational measures;
  • provide reasonable assistance where required by applicable privacy law;
  • maintain a Subprocessor framework;
  • notify Customers of qualifying security incidents as required;
  • support applicable deletion and export requirements;
  • cooperate with reasonable compliance requests;
  • return or delete Customer Data according to applicable contractual requirements.

12. Confidentiality

Qmova will ensure that personnel authorized to process Customer Data are subject to appropriate confidentiality obligations.

Qmova will not intentionally disclose Customer Data to individuals who do not require access to perform authorized functions.

Confidentiality obligations continue after the end of the relevant person's employment, engagement, or other authorization where required by applicable obligations.


13. Security Measures

Qmova maintains technical and organizational measures designed to protect Customer Data against:

  • unauthorized access;
  • unlawful processing;
  • accidental loss;
  • destruction;
  • damage;
  • unauthorized disclosure;
  • alteration.

Relevant measures may include:

  • authentication;
  • Role-Based Access Control;
  • tenant isolation;
  • authorization controls;
  • encryption in transit;
  • password hashing;
  • session management;
  • audit logging;
  • rate limiting;
  • security monitoring;
  • operational monitoring;
  • backup procedures;
  • incident-response processes.

The measures Qmova applies may change over time as the Platform evolves.

Qmova will maintain security appropriate to the nature of the processing and the risks presented.

POPIA requires reasonable technical and organizational measures to protect integrity and confidentiality and to prevent loss, destruction, unlawful access, or processing; it also requires ongoing verification and updating of safeguards.


14. Personnel Access

Qmova will restrict access to Customer Data to personnel or systems that require access for authorized purposes.

Access may be necessary for:

  • service operation;
  • support;
  • security;
  • incident investigation;
  • infrastructure administration;
  • legal compliance.

Qmova is not required to provide Customer Data access to personnel merely for convenience.

Where appropriate, administrative activities are subject to access controls and audit mechanisms.


15. Subprocessors

The Customer authorizes Qmova to use Subprocessors where necessary to provide the Services.

Examples of service categories may include:

  • authentication;
  • email delivery;
  • messaging infrastructure;
  • hosting;
  • storage;
  • monitoring;
  • infrastructure services.

Qmova remains responsible for its contractual relationship with its Subprocessors in accordance with applicable law and the Customer Agreement.

Under GDPR, a processor may engage another processor only with the controller's specific or general written authorization, and a general authorization requires notice of intended changes so the controller can object.


16. Changes to Subprocessors

Qmova may add or replace Subprocessors as the Platform evolves.

Qmova will maintain an up-to-date Subprocessor List.

Where GDPR or another applicable law requires advance notice or an opportunity to object to a new Subprocessor, Qmova will provide the applicable notice.

A Customer's objection should be based on reasonable data-protection grounds.

Where a Customer reasonably objects and the parties cannot resolve the objection, the parties will work in good faith to identify a reasonable alternative.

Nothing in this section requires Qmova to maintain a particular Subprocessor indefinitely where that provider is no longer commercially, technically, or legally appropriate.


17. International Data Transfers

Customer Data may be processed in jurisdictions outside the country in which the Customer or Data Subject is located.

Where GDPR applies, Qmova will use an applicable lawful transfer mechanism for restricted international transfers, which may include:

  • an adequacy decision;
  • Standard Contractual Clauses;
  • another legally recognized transfer mechanism.

Where POPIA applies, Qmova will consider applicable requirements governing cross-border transfers of Personal Information and implement appropriate safeguards.

The parties may enter into additional transfer documentation where required by applicable law.

The European Commission has adopted standard contractual clauses for controller-processor relationships under Article 28, and GDPR provides specific requirements for transfers to third countries.


18. Assistance with Data Subject Requests

Taking into account the nature of the processing, Qmova will provide reasonable assistance to the Customer in responding to applicable requests from Data Subjects.

Assistance may include:

  • identifying relevant Customer Data;
  • exporting available information;
  • correcting or deleting information where technically and contractually appropriate;
  • restricting processing where supported;
  • providing information reasonably necessary for the Customer to respond.

The Customer remains responsible for:

  • receiving the request;
  • verifying the requestor where appropriate;
  • determining whether the request is legally valid;
  • applying applicable exemptions;
  • communicating with the Data Subject.

Qmova may refer a Data Subject directly to the Customer where Qmova is processing the information on the Customer's behalf.


19. Security Incidents

Qmova will maintain procedures for identifying, investigating, containing, and responding to security incidents involving Customer Data.

Where Qmova becomes aware of a confirmed Personal Information breach affecting Customer Data, Qmova will notify the Customer without undue delay where required by applicable law or the Customer Agreement.

Where reasonably available, the notification may include:

  • description of the incident;
  • categories of information affected;
  • known or reasonably suspected impact;
  • steps taken to contain or remediate;
  • recommended Customer actions;
  • information available for regulatory assessment.

Qmova will provide additional information as it becomes reasonably available.

Qmova will not unnecessarily delay notification while waiting for every detail to be conclusively established.


20. Assistance with Compliance

Taking into account the nature of processing and information available to Qmova, Qmova will provide reasonable assistance with the Customer's obligations concerning:

  • security of processing;
  • Data Subject requests;
  • Personal Information breach response;
  • data protection impact assessments where applicable;
  • consultations with regulators where legally required.

The Customer remains responsible for determining whether it needs to conduct a Data Protection Impact Assessment or equivalent assessment.

Qmova may provide information about:

  • security controls;
  • processing activities;
  • subprocessors;
  • data flows;
  • retention;
  • technical architecture.

Such assistance may be subject to reasonable limits and confidentiality obligations.


21. Audits and Assessments

The Customer may request information reasonably necessary to demonstrate Qmova's compliance with applicable processor obligations.

Qmova may provide:

  • security documentation;
  • privacy documentation;
  • architecture documentation;
  • Subprocessor information;
  • security questionnaires;
  • relevant policies;
  • other appropriate compliance information.

Where a Customer has a legally justified need for a more detailed audit, the parties will cooperate in good faith to establish a reasonable audit process.

Any audit must:

  • occur during reasonable business hours;
  • minimize disruption;
  • protect other Customers' information;
  • protect Qmova confidential information;
  • comply with applicable security requirements;
  • not require disclosure of credentials or exploitable security details.

Unless prohibited by applicable law, a Customer's audit rights should not permit access to another Customer's data.


22. Government and Legal Requests

If Qmova receives a legally binding request from a governmental authority for Customer Data, Qmova will assess the request according to applicable law.

Where legally permitted, Qmova will:

  • notify the Customer before disclosure;
  • provide sufficient information for the Customer to assess the request;
  • limit disclosure to the information legally required.

Where law prohibits notification, Qmova will not provide notice until that restriction expires or otherwise permits disclosure.

Qmova may challenge an unlawful or overbroad request where reasonably appropriate.


23. Data Retention and Deletion

Customer Data is retained according to:

  • the Customer Agreement;
  • Customer instructions;
  • applicable retention requirements;
  • security requirements;
  • legal obligations;
  • Qmova's documented deletion processes.

Qmova does not retain Customer Data indefinitely solely because it has previously been processed through the Platform.

Backup copies may persist for a limited period after deletion from primary systems.

The Qmova Data Retention Policy provides additional information about retention principles.


24. Customer Data Export

Where supported by the Services, Customers may export Customer Data.

Export functionality may include:

  • Visits;
  • Appointments;
  • Queue records;
  • Services;
  • Workspace information;
  • other available operational records.

Exports may require:

  • authentication;
  • appropriate authorization;
  • security verification;
  • use of supported formats;
  • reasonable technical limitations.

Qmova may charge reasonable fees for extraordinary export assistance where permitted by the Customer Agreement and applicable law.


25. Return and Deletion Upon Termination

Following termination of the applicable Services, the Customer may request return or export of Customer Data during the applicable period specified by the Customer Agreement.

After the applicable period:

Customer Agreement Ends
        │
        ▼
Applicable Export Period
        │
        ▼
Customer Data Deleted
from Active Systems
        │
        ▼
Secondary Systems
        │
        ▼
Backup Lifecycle Expires

Qmova may retain information where required by:

  • applicable law;
  • regulatory requirements;
  • legal proceedings;
  • security investigations;
  • fraud prevention;
  • legitimate recordkeeping obligations.

Retained information remains subject to applicable confidentiality and security obligations.


26. Customer-Directed Integrations

Customers may connect third-party services to Qmova.

Where the Customer instructs Qmova to transmit Customer Data to a third-party service:

  • the Customer authorizes the integration;
  • the Customer is responsible for selecting the service;
  • the Customer remains responsible for its use of that service;
  • the third party may act independently of Qmova.

Qmova will process the information necessary to support the integration according to the Customer's instructions and the integration's documented functionality.


27. Customer-Owned WhatsApp

Qmova's supported WhatsApp architecture is based on Customer-owned messaging infrastructure.

The Customer:

  • owns its WhatsApp number;
  • controls its WhatsApp environment;
  • authorizes the connection;
  • determines its messaging purposes;
  • determines message content.

Qmova:

  • provides messaging integration infrastructure;
  • processes the information necessary to operate the integration;
  • does not own the Customer's WhatsApp number;
  • does not use a shared Qmova-owned WhatsApp identity as the Customer's sender.

The Customer remains responsible for:

  • applicable WhatsApp terms;
  • recipient rights;
  • messaging consents;
  • lawful messaging practices;
  • message content.

Qmova may restrict or disable an integration when necessary to protect security, comply with law, or respond to abuse or restrictions imposed by the underlying provider.


28. Special Categories and Sensitive Information

Customers may process information that is subject to additional protections under applicable law.

Examples may include:

  • health information;
  • biometric information;
  • financial information;
  • information concerning children;
  • government-issued identifiers;
  • other specially protected categories.

Qmova is a Visit Management Platform, not an Electronic Health Record system.

If a Customer chooses to process sensitive or special categories of Personal Information, the Customer remains responsible for determining:

  • whether processing is legally permitted;
  • whether additional safeguards are required;
  • whether an appropriate legal basis exists;
  • whether a Data Protection Impact Assessment or equivalent assessment is required;
  • whether Qmova is appropriate for the use case.

Qmova does not claim HIPAA compliance.


29. Artificial Intelligence

If Qmova provides AI-assisted functionality, Customer Data will not be used for unrelated AI training or model development unless the applicable agreement or documentation expressly permits that use.

For AI features processing Customer Data on the Customer's behalf, Qmova will provide processing consistent with the Customer's documented instructions and the applicable feature terms.

Where Qmova uses third-party AI services as Subprocessors or integration providers, those services will be evaluated under the applicable Subprocessor framework.

Qmova's AI Usage Policy provides additional information about AI functionality.


30. Aggregated and De-identified Information

Subject to applicable law and the Customer Agreement, Qmova may create aggregated or de-identified information from Platform data.

Such information may be used for purposes including:

  • service performance analysis;
  • capacity planning;
  • product improvement;
  • security analysis;
  • operational statistics.

Qmova will take reasonable measures designed to prevent the resulting information from being used to identify an individual where it is represented as de-identified.

Customer Data that remains identifiable remains subject to this DPA and applicable privacy obligations.


31. Liability

The parties' liability is governed by the Customer Agreement unless a signed agreement states otherwise.

Nothing in this DPA limits liability that cannot legally be limited.

Any liability cap applicable to this DPA will be the liability cap in the Customer Agreement unless the parties expressly agree otherwise.


32. Order of Precedence

If documents conflict, the following order applies to the extent of the conflict:

  1. mandatory applicable law;
  2. a signed enterprise agreement, where expressly stated;
  3. this DPA for data-processing matters;
  4. a signed Order Form;
  5. the Service Level Agreement for service-level matters;
  6. the general Terms of Service;
  7. other referenced policies.

An enterprise agreement may establish a different contractual hierarchy.


33. Changes to This DPA

Qmova may update this DPA when necessary to:

  • reflect changes in privacy law;
  • reflect material changes to processing;
  • add or change security requirements;
  • incorporate new regulatory requirements;
  • clarify operational practices.

A change that materially reduces the Customer's contractual data-protection rights will not be made solely through routine documentation updates where the Customer Agreement requires a different amendment process.

Where the Customer is entitled to notice or objection regarding a material change, Qmova will provide the applicable notice.


34. Term and Termination

This DPA becomes effective when:

  • the Customer accepts it;
  • an applicable Customer Agreement incorporates it;
  • the parties execute it; or
  • another documented contractual mechanism makes it binding.

It remains effective while Qmova processes Customer Data on behalf of the Customer.

Relevant obligations survive termination for as long as Qmova retains Customer Data or is otherwise legally required to perform the applicable obligation.


35. Miscellaneous

No Waiver

Failure to enforce a provision of this DPA does not constitute a waiver.

Severability

If a provision is unenforceable, the remaining provisions remain effective to the extent permitted by law.

Electronic Form

This DPA may be accepted electronically.

Amendments

Amendments may be made through an applicable Customer Agreement or other written or electronic agreement between the parties.

This DPA is intended to create binding obligations concerning the processing of Customer Data where incorporated into the applicable Customer Agreement.


36. Contact Information

For privacy and data-protection matters:

Privacy: privacy@qmova.com

For security incidents:

Security: security@qmova.com

For contractual matters:

Legal: legal@qmova.com

For general support:

Support: support@qmova.com


37. Related Documentation

This DPA should be read together with:

Privacy

  • Privacy Policy
  • Cookie Policy
  • Data Retention Policy

Security

  • Qmova Trust Center
  • Architecture Overview
  • Security Overview
  • Security Policy
  • Responsible Disclosure Policy
  • Subprocessor List
  • Terms of Service
  • Service Level Agreement
  • Acceptable Use Policy
  • Refund and Cancellation Policy

Compliance

  • Compliance Roadmap
  • Accessibility Statement
  • AI Usage Policy

38. 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, subprocessors, security practices, data architecture, or Customer contractual framework.

This DPA is a general Qmova processing framework and should be reviewed by qualified privacy counsel before being treated as Qmova's final contractual DPA for regulated or enterprise Customers.


39. Version History

| Version | Date | Summary | | ------- | -------------- | -------------------------------------- | | 1.0.0 | 12 August 2026 | Initial Qmova Data Processing Addendum |


40. Schedule 1 — Processing Details

Subject Matter

The processing of Personal Information necessary to provide Qmova's Visit Management Platform.

Duration

Processing continues for the duration of the applicable Customer Agreement and any additional period required for:

  • deletion;
  • backup expiration;
  • legal retention;
  • dispute resolution;
  • security and compliance requirements.

Nature of Processing

Processing may include:

  • collection;
  • storage;
  • organization;
  • retrieval;
  • use;
  • transmission;
  • notification;
  • analysis for Customer-configured purposes;
  • modification;
  • deletion.

Purpose of Processing

The primary purposes are to:

  • provide Qmova;
  • manage Visits;
  • manage Appointments;
  • manage Walk-ins;
  • manage Queues;
  • provide QR Check-in;
  • provide notifications;
  • support Customer operations;
  • secure the Platform;
  • provide technical support;
  • perform Customer-authorized integrations.

Categories of Personal Information

Depending on Customer configuration:

  • identity information;
  • contact information;
  • Appointment information;
  • Visit information;
  • Queue information;
  • Check-in information;
  • Service information;
  • Staff information;
  • operational notes;
  • notification information;
  • relevant technical information.

Categories of Data Subjects

Depending on Customer configuration:

  • Visitors;
  • Customers' customers;
  • patients;
  • students;
  • citizens;
  • guests;
  • clients;
  • Staff Members;
  • employees;
  • contractors;
  • other individuals represented in Customer Data.

41. Schedule 2 — Security Measures

Qmova maintains security measures appropriate to the nature and risks of processing.

The current security framework may include:

Identity and Authentication

  • authenticated user accounts;
  • Google OAuth;
  • email authentication;
  • OTP authentication;
  • session management.

Authorization

  • Role-Based Access Control;
  • Workspace membership;
  • server-side authorization;
  • permission checks.

Tenant Isolation

  • Workspace context;
  • access controls;
  • tenant-aware application logic;
  • separation of Customer data access.

Data Protection

  • HTTPS/TLS encryption in transit;
  • password hashing;
  • controlled access to infrastructure;
  • protection of authentication material.

Logging

  • authentication logs;
  • audit records;
  • security events;
  • operational logs;
  • relevant configuration changes.

Monitoring

  • application monitoring;
  • infrastructure monitoring;
  • error monitoring;
  • security monitoring;
  • integration monitoring.

Resilience

  • database backup strategies;
  • recovery procedures;
  • operational monitoring;
  • incident response.

Security Management

  • vulnerability management;
  • responsible disclosure;
  • incident response;
  • access management;
  • documented security policies.

These measures may be updated as Qmova's architecture and security program mature.

Qmova does not claim SOC 2, ISO 27001, HIPAA, or other certification unless formally obtained and expressly identified in the Qmova Trust Center or applicable agreement.


42. Schedule 3 — Current Subprocessors

The following categories of external providers may process Customer Data as part of the Qmova Services:

| Provider / Service | Purpose | | ----------------------------------------------------------- | ---------------------------------------------------------------------- | | Google | Authentication | | Brevo | OTP and transactional email | | Evolution API / applicable WhatsApp infrastructure provider | Customer-connected WhatsApp workflows | | Hosting / infrastructure providers | Hosting and infrastructure services | | Other approved providers | Specific platform functionality as identified in the Subprocessor List |

The authoritative Subprocessor List should identify:

  • legal entity name;
  • service;
  • processing purpose;
  • processing location, where appropriate;
  • categories of Personal Information;
  • date added;
  • applicable transfer mechanism, where relevant.

Because Qmova's infrastructure may evolve, this Schedule should be kept synchronized with the public Subprocessor List.


Processing Principle

The Customer decides why Customer Data is processed. Qmova provides the infrastructure that processes it on the Customer's behalf, protects it with appropriate safeguards, and supports the Customer in meeting its applicable data-protection obligations.