EnigmaSuite

Legal · DPA-17

Data Processing Addendum

Document
DPA-17
Version
1.0
Effective
November 18, 2026
Next review
November 2027
Owner
Data Protection Officer
Approved by
Executive Management

This English version is provided for convenience. Where a document states that the Spanish version governs, the Spanish version prevails.

This English version is a courtesy translation. The Spanish version is the governing text.

Data Processing Addendum (DPA)

This Data Processing Addendum (the "DPA") is entered into between Enigmatech Mexico SAPI de CV, the company that operates the EnigmaSuite platform ("EnigmaSuite"), with registered address at Velázquez 324, Col. La Estancia, C.P. 45030, Zapopan, Jalisco, México, and the customer identified in the EnigmaSuite Terms of Service or in the applicable signed commercial agreement (the "Customer").

This DPA is an integral part, by incorporation by reference, of the EnigmaSuite Terms of Service (the "ToS") and, where applicable, of the signed commercial agreement between the parties. With respect to personal data protection matters, this DPA prevails over the ToS. Acceptance of the ToS (through the electronic acceptance mechanism described in Section 17) constitutes acceptance of this DPA.

1. Definitions

1.1 Capitalized terms not defined in this DPA have the meaning given to them in the ToS. For purposes of this DPA:

2. Object, scope and duration

2.1 Object. This DPA governs the processing of Customer Data that EnigmaSuite performs, in its capacity as Processor, on behalf of and in accordance with the instructions of the Customer, in connection with the provision of the Platform.

2.2 Scope. This DPA applies to all Customer Data processed through the Platform, regardless of the module used. The data categories, Data Subjects and processing operations are detailed in Annex A.

2.3 Duration. This DPA takes effect upon acceptance of the ToS (or upon signature of the commercial agreement incorporating it, whichever occurs first) and remains in force for as long as EnigmaSuite processes Customer Data, including after termination of the ToS, until the return and deletion provided for in Section 14 are completed.

3. Roles of the parties

3.1 The Customer is and remains the Controller of all personal data it uploads, collects or generates through the Platform, including, without limitation: the data of its employees and contractors (including biometric and geolocation data), the data of its clients and buyers, the data of citizens or applicants captured in forms, and the data of any other End User.

3.2 EnigmaSuite acts exclusively as Processor with respect to Customer Data, and processes it solely on behalf of the Customer and in accordance with its documented instructions (Section 4).

3.3 EnigmaSuite is the Controller only of: (a) the account data of the Customer and its administrative and staff users (identification, contact details, credentials); (b) the Customer's billing and collection data; and (c) Platform telemetry, security and usage data. Such processing is governed by EnigmaSuite's Comprehensive Privacy Notice (doc_code AVISO-INT) and not by this DPA.

3.4 Relationship with End Users. Every sale, filing, service or relationship managed through the Platform is a relationship exclusively between the Customer and its End User. EnigmaSuite is not a party to that relationship and does not assume, vis-à-vis End Users, the Customer's obligations as Controller. If a Data Subject addresses to EnigmaSuite a request relating to Customer Data, EnigmaSuite will forward it to the Customer without undue delay (Section 12.4).

4. Documented instructions

4.1 The Configuration Documentation constitutes the Customer's documented instructions. The configuration the Customer establishes in the Platform — including the activation or deactivation of modules and features (for example, biometric or geolocation features), the configuration of integrations with its own third-party accounts, retention parameters, and its users' permissions — embodies the Customer's instructions to EnigmaSuite.

4.2 The following also constitute documented instructions: (a) the instructions set forth in the ToS, in this DPA and in the signed commercial agreement, where applicable; and (b) reasonable additional instructions communicated by the Customer in writing through official support channels, provided they are compatible with the Platform's features.

4.3 EnigmaSuite will process Customer Data solely in accordance with such instructions, unless a legal obligation requires otherwise, in which case EnigmaSuite will inform the Customer of that requirement before processing, unless the law prohibits it.

4.4 EnigmaSuite will inform the Customer — without this implying an obligation to perform legal analysis — when it considers that a Customer instruction infringes Applicable Data Protection Law, and may suspend its execution until the Customer confirms or modifies it.

5. Nature and purposes of processing

5.1 Nature. Processing comprises the operations necessary to provide the Platform: collection (through the interfaces configured by the Customer), recording, organization, structuring, storage, retrieval, use, disclosure to the Customer itself and to the recipients the Customer configures, backup, and erasure or destruction.

5.2 Purposes. EnigmaSuite processes Customer Data exclusively to: (a) provide, operate, maintain and support the Platform and its modules in accordance with the Configuration Documentation; (b) prevent fraud and safeguard the security of the Platform; and (c) comply with legal obligations applicable to EnigmaSuite as Processor.

5.3 Prohibitions. EnigmaSuite will not use Customer Data for its own purposes other than the foregoing; will not sell it or disclose it to third parties except to Subprocessors authorized under Section 7 or where required by law; and will not retain it beyond what is provided in Section 14.

5.4 Offline operation. The Customer acknowledges that certain Platform features (for example, offline time-clock and route operation) temporarily store data — including, where applicable, encrypted biometric data — on devices under the control of the Customer or its personnel, until synchronization. Physical custody of such devices is the Customer's responsibility.

6. Obligations of EnigmaSuite as Processor

6.1 EnigmaSuite undertakes to:

6.2 EnigmaSuite will maintain logical isolation of Customer Data from the data of other Platform customers, through the mechanisms described in Annex B.

7. Subprocessors

7.1 General authorization. The Customer generally authorizes EnigmaSuite to engage Subprocessors for the provision of the Platform. The current Subprocessors are identified in the Subprocessor List (doc_code SUBPROC), which forms part of this DPA as Annex C by reference and is publicly available in the Legal section of the Platform.

7.2 Customer-configured integrations. Third-party services that the Customer connects to the Platform using its own accounts, credentials or keys (for example: payment gateways, marketplaces and sales channels, tax invoicing providers, the Customer's email providers, map services under the Customer's key, and the Customer's pixels and analytics tools) are not Subprocessors of EnigmaSuite. Such third parties process data on behalf of the Customer under the agreements the Customer itself maintains with them, and the Customer is solely responsible for their selection, configuration and legal compliance. The Subprocessor List distinguishes them for informational purposes.

7.3 Changes to Subprocessors. EnigmaSuite will notify the Customer of the addition or replacement of platform Subprocessors at least 30 (thirty) calendar days in advance, by updating the Subprocessor List and sending a notice to the administrators of the Customer's organization (email or in-Platform notice).

7.4 Objection. If the Customer reasonably objects in writing, within the notice period, to the addition of a Subprocessor on well-founded data protection grounds, the parties will negotiate a reasonable alternative in good faith. If none is available, the Customer may terminate the affected functionality or service as provided in the ToS.

7.5 Flow-down and liability. EnigmaSuite will impose on each Subprocessor, by written contract, data protection obligations substantially equivalent to those of this DPA to the extent applicable to the subcontracted service, and will be liable to the Customer for the acts and omissions of its Subprocessors in the processing of Customer Data as if they were its own, subject to Section 16.

8. International transfers

8.1 Infrastructure abroad. The Customer acknowledges and agrees that the Platform is hosted and operated on cloud infrastructure located primarily in the United States of America, and therefore Customer Data is stored and processed in that country through the infrastructure Subprocessors identified in the Subprocessor List.

8.2 Cloud biometric processing. When the Customer activates the cloud biometric engine, facial verification captures are sent to a facial recognition service operated in the United States of America (AWS Rekognition, us-east-2 region) for one-to-one comparison; that service does not retain the captures once the comparison is completed. The Customer may choose, where available in its configuration, the biometric engine that processes on the device itself.

8.3 Customer's disclosure duty. As Controller, the Customer must inform Data Subjects, in its own privacy notices and consents, that their data is processed on servers located in the United States of America, and obtain the consents required by Applicable Data Protection Law (see Section 15).

8.4 New locations. The addition of new processing locations or countries at the platform level will be treated as a Subprocessor change under Section 7.3.

9. Security measures

9.1 EnigmaSuite implements and maintains the administrative, technical and physical security measures described in Annex B, designed to protect Customer Data against damage, loss, alteration, destruction, or unauthorized use, access or processing.

9.2 EnigmaSuite may update such measures provided the update does not materially reduce the level of protection of Customer Data.

10. Personnel and confidentiality

10.1 EnigmaSuite will limit access to Customer Data to personnel who require it to provide the service, will subject them to confidentiality obligations, and will provide them with reasonable data protection training.

10.2 The confidentiality obligations of this Section survive indefinitely after termination of this DPA.

11. Security Breach notification

11.1 Notice to the Customer. EnigmaSuite will notify the Customer of any Security Breach without undue delay once confirmed, with the target of doing so within 72 (seventy-two) hours following confirmation of the Security Breach, addressed to the administrators of the Customer's organization through the contact channels registered in the Platform.

11.2 Content. To the extent the information is available, the notice will include: (a) the nature of the Security Breach and the date or estimated period in which it occurred; (b) the categories of Customer Data and of affected Data Subjects and, where possible, their approximate number; (c) the likely consequences; (d) the corrective measures adopted or proposed; and (e) an EnigmaSuite contact point. EnigmaSuite may deliver the information in phases as the investigation progresses.

11.3 Cooperation. EnigmaSuite will reasonably cooperate with the Customer and provide the information the Customer reasonably requires so that the Customer, in its capacity as Controller, can comply with its notification obligations to Data Subjects and, where applicable, to the Authority.

11.4 No direct notification. Unless otherwise required by law or agreed in writing between the parties, it is the Customer — and not EnigmaSuite — who must notify the Security Breach to Data Subjects and the Authority with respect to Customer Data.

11.5 No admission of liability. Notification of a Security Breach does not constitute an acknowledgment of fault, negligence or liability by EnigmaSuite.

12. ARCO rights assistance

12.1 Handling by the Customer. It is the Customer's responsibility, as Controller, to receive, process and respond to requests for the rights of access, rectification, cancellation and objection (ARCO), as well as consent withdrawal and limitation of use or disclosure, submitted by Data Subjects of Customer Data.

12.2 Platform tools. As the first avenue of assistance, the Platform provides self-service tools that allow the Customer to handle such requests directly, including: record lookup, export, rectification and deletion features; self-service account deletion mechanisms for End Users in the modules that offer them; and revocation of employees' biometric templates.

12.3 Additional assistance. Where the Customer cannot handle a request with the available tools, EnigmaSuite will provide reasonable assistance upon written request, with the target of responding within 10 (ten) business days following receipt of the assistance request. If complexity so requires, EnigmaSuite will inform the Customer of the estimated timeframe.

12.4 Requests addressed to EnigmaSuite. If a Data Subject submits an ARCO request relating to Customer Data directly to EnigmaSuite, EnigmaSuite will forward it to the Customer without undue delay and will not respond to it directly, except where legally required.

12.5 Assessments. Upon the Customer's reasonable request, EnigmaSuite will provide available information about the processing as necessary for the Customer to carry out impact assessments or to handle Authority requirements imposed on it as Controller by Applicable Data Protection Law.

13. Audits

13.1 Documentary audit. EnigmaSuite will make available to the Customer, upon written request, reasonable information to demonstrate compliance with this DPA, which may consist of: descriptions of the security measures in force, summaries of security assessments or tests, certifications and audit reports of infrastructure Subprocessors, and written responses to reasonable security questionnaires.

13.2 Limits. The reviews contemplated in this Section: (a) will be limited to one per 12 (twelve)-month period, except following a Security Breach affecting the Customer or a well-founded requirement of the Authority; (b) will be documentary in nature, with no physical access to facilities or production systems, given that the infrastructure is operated by cloud providers; (c) will be at the Customer's expense; and (d) will be subject to confidentiality obligations regarding the information provided.

13.3 Information provided under this Section may not be used for purposes other than verifying compliance with this DPA.

14. Return and deletion upon termination

14.1 Export window. Upon termination of the ToS or the commercial agreement, the Customer will have 30 (thirty) calendar days to export Customer Data using the Platform's export tools. Upon written request within that period, EnigmaSuite will provide reasonable export assistance.

14.2 Deletion. Once the export window has elapsed, EnigmaSuite will delete Customer Data from its systems within a period of no more than 90 (ninety) calendar days, including its removal from backups in accordance with backup rotation cycles.

14.3 Certificate. Upon the Customer's written request, EnigmaSuite will issue a certificate of deletion once completed.

14.4 Biometric data. Notwithstanding the foregoing, biometric templates and captures will be destroyed when the purpose for which they were processed has been fulfilled (for example, the employee's offboarding or the revocation of their enrollment) or upon the Customer's request, whichever occurs first, including during the term of this DPA.

14.5 Legal exceptions. EnigmaSuite may retain data it is required to keep by legal obligation (for example, tax information or evidence of electronic acceptances under the Commercial Code), in which case it will keep such data isolated, protected in accordance with Annex B and blocked from any other processing, until the corresponding legal periods expire.

15. Customer representations and obligations

15.1 The Customer represents and warrants that:

15.2 EnigmaSuite makes consent-capture and consent-recording tools available to the Customer as operational support; their use does not transfer to EnigmaSuite the obligation to obtain or evidence consents, which rests exclusively with the Customer as Controller.

15.3 Breach of this Section 15 is additionally governed by the indemnification clause of the ToS.

16. Liability

16.1 Each party's liability arising from this DPA is subject to the limitations and exclusions of liability agreed in the ToS (or, where applicable, in the signed commercial agreement), including the aggregate liability cap equal to the amounts paid by the Customer in the 12 (twelve) months preceding the triggering event, and the exclusion of indirect damages.

16.2 The aggregate cap is single and combined for claims arising under the ToS and this DPA; invoking it under one does not duplicate it under the other.

16.3 Nothing in this DPA limits liability that cannot be limited under applicable law, including liability arising from willful misconduct or gross negligence (Article 2106 of the Federal Civil Code).

17. Precedence, amendments and acceptance

17.1 Order of precedence. (a) With respect to personal data protection matters, this DPA prevails over the ToS. (b) If a signed commercial agreement exists between the parties, that agreement prevails on commercial terms, and the ToS and this DPA govern the operation of the Platform; if the signed agreement contains specific data protection clauses that contradict this DPA, those clauses will prevail between the parties.

17.2 Amendments. EnigmaSuite may update this DPA in accordance with the legal document amendment procedure set forth in the ToS. Material changes will be notified at least 30 (thirty) calendar days in advance and will require re-acceptance by the Customer's administrators.

17.3 Electronic acceptance. This DPA is accepted through the electronic acceptance (clickwrap) mechanism of the ToS or through the signature of the commercial agreement incorporating it. The parties acknowledge the validity of such acceptance as a data message under Articles 89 and 93 of the Mexican Commercial Code, and agree that the acceptance record (identity, document version, hash and server timestamp) constitutes evidence of its execution.

17.4 Language. The governing text of this DPA is the Spanish version; the English version is a courtesy translation.

18. Governing law and jurisdiction

18.1 This DPA is governed by the federal laws of the United Mexican States, including Applicable Data Protection Law and the Commercial Code.

18.2 For any dispute arising from this DPA, the parties submit to los tribunales competentes con sede en Zapopan, Jalisco, México, waiving any other forum to which they might be entitled by reason of their present or future domiciles.

Annex A — Data categories, Data Subjects and processing operations

A.1 Categories of Data Subjects

A.2 Categories of personal data

#CategoryExamples in the PlatformData SubjectsSensitive?
1IdentificationName, date of birth, gender, marital status, photograph, CURP, NSS (social security number), RFC (tax ID)Employees; End Users (RFC in CRM/invoicing)Not sensitive per se; high-risk identifiers requiring special care
2ContactEmail, telephone numbers, address, emergency contactEmployees; End UsersNo
3Employment and payrollPosition, salary and contribution base salary, deductions, benefits, employment documents (contracts, IDs)EmployeesPartially (see category 6)
4Financial and asset-relatedEmployees' CLABE and bank accounts; credit information of CRM clientsEmployees; End UsersNot sensitive, but Applicable Data Protection Law requires reinforced consent for financial/asset data
5BiometricFacial templates/vectors generated for identity verification; facial verification captures (time clock/enrollment); verification metadata (confidence level, liveness)EmployeesYES — Sensitive Personal Data
6Health-related (health-adjacent)Medical, dental and vision insurance deductions and benefits; dependents; conditions recorded in labor compliance profiles (e.g., pregnancy, disability)EmployeesYES — Sensitive Personal Data
7GeolocationClock-in/clock-out coordinates and geofence status; geofences configured by the Customer (which may include the employee's home address); live GPS tracking of drivers; route stop history with photos and signaturesEmployees (drivers, operational personnel)Not statutorily sensitive, but high-risk processing subject to prior notice and consent
8Commerce and End UsersEnd User accounts (name, email, phone, credentials); ticket and point-of-sale buyers; marketplace buyer PII (name, address, email, phone) ingested from sales channels; content of forms and files in filings/reports defined by the Customer; CRM (RFC, tax regime, addresses, credit); logistics portal clientsEnd UsersContent of configurable forms may include sensitive data under the Customer's responsibility
9TaxTax invoices (CFDI) in XML/PDF with issuer and recipient RFC; the Customer's tax certificates and keys (FIEL/CSD) held for stampingEnd Users; the Customer itselfNo
10PaymentCard brand, last 4 digits and authorization code; gateway transaction identifiers. The Platform does not store full card numbers (PAN) or security codes (CVV)End UsersNo
11Technical and audit recordsIP addresses, user agent, activity and audit logs (which may include per-event coordinates), synchronization recordsAllNo

A.3 Processing operations

Hosting and storage; structuring and organization by module; retrieval and display by the Customer's authorized users; one-to-one biometric verification (where activated by the Customer); computation and reporting (payroll, sales, indicators); disclosure to the recipients configured by the Customer (for example, emails to End Users, tax stamping, sales channels); backup and restoration; deletion.

A.4 Temporary storage on devices

For offline operation, certain data (including biometric templates and encrypted captures pending synchronization, and route and client data for deliveries) is temporarily stored on the devices used by the Customer's personnel, under the Customer's custody (Section 5.4).

Annex B — Technical and organizational security measures

EnigmaSuite maintains, at a minimum, the following measures:

B.1 Encryption.

B.2 Multi-tenant isolation.

B.3 Access control.

B.4 Secrets management.

B.5 Logging and audit.

B.6 Continuity and backup.

B.7 Incident management.

B.8 Biometric data lifecycle.

EnigmaSuite may update this Annex B in accordance with Section 9.2.

Annex C — Subprocessor List

The current Subprocessor List (doc_code SUBPROC) is incorporated into this DPA by reference and is published in the Legal section of the Platform. That list distinguishes: (a) the platform Subprocessors engaged by EnigmaSuite; and (b) for informational purposes, the Customer-configured integrations that do not constitute Subprocessors of EnigmaSuite (Section 7.2). Changes to the list are governed by Sections 7.3 and 7.4.

Annexes D and E — Reserved

Reserved for future use.

Annex F — Country Addenda (stub)

F.1 This Annex F will receive the applicable jurisdiction-specific addenda when the Customer or its Data Subjects are located outside Mexico. As of this version, no country addendum has been issued; the baseline of this DPA is Mexican law.

F.2 Without limitation, the following are expected to be issued in the future: (a) a United States Addendum (including state privacy requirements — e.g., CCPA/CPRA — and biometric data laws such as Illinois BIPA, with their retention and destruction schedules); and (b) a Canada Addendum (PIPEDA and Quebec Law 25, including consent and French-language requirements). [ADDENDA US/CA — PENDIENTES DE REDACCIÓN]

F.3 Once issued, country addenda will automatically attach to this DPA based on the Customer's country registered in the Platform, and will prevail over the body of the DPA only with respect to the Data Subjects and processing subject to the corresponding jurisdiction.