EnigmaSuite

Legal · SPL-19

Subprocessor List

Document
SPL-19
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.

Enigmatech Mexico SAPI de CV, the company that operates the EnigmaSuite platform ("EnigmaSuite"), with registered address at Velázquez 324, Col. La Estancia, 45030 Zapopan, Jalisco, Mexico.

This document is issued in Spanish and English. The Spanish version governs; this English version is a courtesy translation.

1. Introduction and Purpose of This List

1.1 Purpose. This list identifies: (a) the Subprocessors and infrastructure providers that EnigmaSuite engages to operate the Platform and that, in that capacity, process personal data on behalf of the Customer (Table A); and (b) the third-party services that the Customer configures and contracts directly through the Platform and that are not Subprocessors of EnigmaSuite (Table B).

1.2 Relationship to the DPA. This document forms an integral part of the Data Processing Addendum (doc_code: DPA) entered into between EnigmaSuite and the Customer, and is incorporated into it by reference as its Subprocessor annex. Capitalized terms not defined here ("Platform", "Customer", "End User", "Data Subject", "Controller", "Processor", "Subprocessor", "Configuration Documentation") have the meaning assigned to them in the DPA.

1.3 Roles model. Under the DPA: the Customer is and remains the Controller of the personal data it uploads, collects, or generates on the Platform (data of its employees, its customers, and its End Users); EnigmaSuite acts as Processor for that data, and is Controller only of the Customer's own account, billing, and telemetry data. Accordingly:

    a) with respect to data for which the Customer is Controller, the providers in Table A act as Subprocessors of EnigmaSuite; and

    b) with respect to the account, billing, and telemetry data for which EnigmaSuite is Controller, those same providers act as Processors of EnigmaSuite.

1.4 General authorization and advance-notice commitment. By accepting the DPA, the Customer grants a general authorization for EnigmaSuite to use the Subprocessors listed in Table A. EnigmaSuite commits to notify the Customer at least thirty (30) calendar days in advance of the addition of any new platform-level Subprocessor, or of a material change of purpose for an existing one, by: (i) email to the Customer's organization administrators registered on the Platform; and (ii) an in-app notice within the Platform itself. The notification procedure and the right to object are detailed in Section 5.

1.5 Obligations imposed on Subprocessors. EnigmaSuite imposes on each Subprocessor in Table A, by written contract, data protection obligations substantially equivalent to those assumed by EnigmaSuite in the DPA (confidentiality, security, processing limited to instructions), and remains liable to the Customer for such Subprocessors' compliance as set out in the DPA.

2. Table A — Platform-Level Subprocessors (Engaged by EnigmaSuite)

2.1 The following providers are engaged by EnigmaSuite, apply to all Customers of the Platform, and process personal data in the ordinary operation of the service:

#SubprocessorService and purposeCategories of data processedProcessing location
A-1Supabase, Inc.Database, authentication, file storage, and server functions (the Platform's primary backend)All categories of data processed on the Platform, including Customer account data and data for which the Customer is Controller (employees, customers, End Users), including sensitive data where the Customer enables the corresponding features (e.g., biometric templates, employment and health-adjacent data)United States
A-2Amazon Web Services, Inc. — S3 (us-east-2 region)Storage of tax/fiscal filesTax receipts (CFDI in XML/PDF, including issuer and recipient RFC) and electronic signature certificates (FIEL: .cer/.key files) uploaded by the CustomerUnited States
A-3Amazon Web Services, Inc. — Rekognition (us-east-2 region)Facial verification for the Customer's employee time-and-attendance (1:1 comparison at enrollment and at clock-in/out). ⚠️ Subprocessor of biometric data (sensitive personal data under the Mexican LFPDPPP). Applies only when the Customer enables the cloud facial engineLive facial captures of the Customer's employees, submitted for comparison; the Platform does not retain the capture server-side once the comparison is performedUnited States
A-4Amazon Web Services, Inc. — Lightsail (us-east-1 region)Backend application server, cache, and processing queuesData transiting the Platform's API in normal operation (all categories); technical logs including IP addressesUnited States
A-5Cloudflare, Inc.Content delivery network (CDN), DNS, and TLS certificates, including Customers' custom domainsNetwork traffic data (IP addresses, connection metadata); encrypted transit of Platform contentUnited States / global network
A-6Stripe, Inc.Collection of the Customer's SaaS subscription payments to EnigmaSuite (Platform billing)Contact and billing data of the Customer's organization; card data is collected and held by Stripe directly (it does not pass through the Platform)United States
A-7Twilio, Inc. (SendGrid)Sending of the Platform's transactional emailRecipient names and email addresses; content of transactional messagesUnited States
A-8Resend, Inc.Internal technical/operational alerts addressed to EnigmaSuite staffOperational and technical data; personal data only incidentally and minimallyUnited States
A-9GitHub, Inc. (Microsoft)Continuous integration and deployment (CI/CD) of the Platform's codeSource code and deployment artifacts; by design it does not process Data Subjects' personal data in ordinary operationUnited States
A-10Anthropic, PBCThe Platform's artificial intelligence features (e.g., drafting assistance for documents and content)Content submitted to the AI features by users. As a matter of policy, no personal data of the Customer's Data Subjects should be sent to this provider [PENDING VALIDATION — confirm technically and contractually the actual scope of data sent before publishing]United States
A-11OpenAI, LLCThe Platform's artificial intelligence features (e.g., drafting assistance for documents and content)Content submitted to the AI features by users. As a matter of policy, no personal data of the Customer's Data Subjects should be sent to this provider [PENDING VALIDATION — confirm technically and contractually the actual scope of data sent before publishing]United States

2.2 Biometric data note (A-3). AWS Rekognition is used only when the Customer, through its Configuration Documentation, enables the cloud facial verification engine for its attendance module. Under the DPA, such enablement constitutes a documented instruction of the Customer and a representation by the Customer that it has obtained the express written consent of each Data Subject (employee), including disclosure of processing on servers located in the United States. The Platform also offers a facial verification engine that runs entirely on-device, with no capture sent to the cloud; the choice of engine belongs to the Customer.

2.3 AI features note (A-10 and A-11). The Platform's artificial intelligence features are designed to operate on business content (for example, text and documents) and not to receive personal data of the Customer's Data Subjects. [PENDING VALIDATION — before publishing this list it must be verified that: (i) no current Platform flow sends Data Subjects' personal data to these providers; and (ii) the retention and no-training terms applicable to the accounts contracted by EnigmaSuite.]

2.4 Currency. This table reflects the Subprocessors in effect as of the last-updated date indicated at the top of this document. The current version is permanently published at https://app.enigmasuite.com/legal/subprocessors.html.

3. Table B — Third-Party Services Configured by the Customer (NOT Subprocessors of EnigmaSuite)

3.1 Nature of these services. The Platform allows the Customer to connect third-party services using the Customer's own credentials, accounts, or contracts (API keys, OAuth connections, commercial accounts). Such connection forms part of the Customer's Configuration Documentation and constitutes an instruction by the Customer to exchange data with the chosen third party. With respect to these services:

    a) the third party is not a Subprocessor of EnigmaSuite; it processes the data under the direct contractual relationship between the Customer and that third party;

    b) the Customer is solely responsible for: (i) entering into any necessary agreements with the third party (including data processing agreements), (ii) verifying the third party's compliance with applicable law, and (iii) informing Data Subjects and obtaining any required consents; and

    c) EnigmaSuite merely transmits or receives data according to the Customer's configuration and assumes no responsibility for the third party's processing.

3.2 Third-party services configurable by the Customer as of the date of this list:

#ServicePurposeTypical data exchangedWho contracts it
B-1Stripe (Customer's own account / Stripe Connect)Collection of the Customer's sales from its End UsersBuyer data (name, email) and payment data; the card is processed by Stripe directlyThe Customer
B-2Mercado PagoPayment gateway for the Customer's salesBuyer and payment dataThe Customer
B-3OpenPay (BBVA)Payment gateway for the Customer's salesBuyer and payment dataThe Customer
B-4ConektaPayment gateway for the Customer's salesBuyer and payment dataThe Customer
B-5PayPalPayment gateway for the Customer's salesBuyer and payment dataThe Customer
B-6BBVA — PAX physical terminalIn-person card payment at the point of saleCard data is captured and processed on the terminal itself and never passes through the Platform; the Platform records only the card brand, last 4 digits, and authorization codeThe Customer
B-7Mercado LibreThe Customer's online sales channelThe Customer's buyer data (name, address, email, phone) and order data, which enter the Platform for fulfillmentThe Customer
B-8ShopifyThe Customer's online sales channelThe Customer's buyer data (name, address, email, phone) and order data, which enter the Platform for fulfillmentThe Customer
B-9Amazon (SP-API)The Customer's online sales channelThe Customer's buyer and order data, which enter the Platform for fulfillmentThe Customer
B-10FacturAPI (authorized PAC, Mexico)Stamping of the Customer's tax receipts (CFDI)Tax data of issuer and recipient (legal name, RFC, tax regime, invoiced items)The Customer (own per-organization credentials)
B-11SendGrid or the Customer's own SMTP server (per-organization configuration)Sending of the Customer's emails to its own customers and End UsersRecipient names and email addresses; content of the Customer's messagesThe Customer
B-12WhatsApp Cloud API (Meta Platforms)The Customer's messaging with its customersPhone numbers and message contentThe Customer
B-13Google Maps (Google)Geocoding and map display within the Customer's modulesAddresses and geographic coordinatesThe Customer (with the option of a courtesy key provided by the Platform)
B-14Google Drive (Google)File storage linked by the CustomerFiles and documents the Customer chooses to linkThe Customer
B-15Telematics providers (e.g., Motive, Samsara, custom integrations)GPS telematics for the Customer's fleetVehicle and driver location, unit identifiers, and trip eventsThe Customer
B-16Wodely (Canada)The Customer's 3PL / TMS logistics operationsOrder, shipment, and recipient dataThe Customer
B-17SAP (the Customer's own system)Data exchange with the Customer's own ERP (e.g., inventory imports)The Customer's inventory and business data; personal data only if the Customer includes it in its filesThe Customer
B-18Analytics and advertising pixels (Meta Pixel / Conversions API, Google Analytics 4)Measurement and advertising on the Customer's public surfaces (event pages, funnels, sites)Browsing identifiers and visit events; for Meta's Conversions API, email and phone hashed with SHA-256The Customer (enabled in its configuration)

3.3 The Customer's public surfaces. The pixels and scripts in row B-18 run only on the public surfaces configured by the Customer and are subject to the Customer's privacy notice and cookie policy; the Customer is the Controller vis-à-vis visitors of those surfaces.

4. International Data Transfers

4.1 Infrastructure location. The Platform's primary infrastructure (Table A) is hosted in the United States of America. Consequently, personal data provided by the Customer and its Data Subjects from Mexico is stored and processed on servers located outside Mexico.

4.2 Legal nature. The transmission of personal data by EnigmaSuite (as Processor) to the Subprocessors in Table A is carried out on behalf of and under the instructions of the Customer, within the framework of the service and the DPA. [NOTE FOR LEGAL REVIEW — confirm the characterization of these communications as "remisiones" (data remittances to processors, as opposed to "transfers") under the Mexican LFPDPPP in force (Official Gazette 20-Mar-2025) and adjust the terminology of this clause accordingly.]

4.3 Safeguards applied. With respect to data hosted or processed abroad, EnigmaSuite applies at least the following safeguards: (a) encryption of data in transit (TLS) and at rest; (b) contractual data protection clauses entered into with each provider in Table A; (c) access controls and per-organization isolation (including row-level security policies in the database); and (d) the other security measures described in the security-measures annex of the DPA.

4.4 Customer's disclosure obligation. The Customer, as Controller, must inform its Data Subjects — in its own privacy notice and in the consents it obtains — that their data is processed on servers located in the United States, including express disclosure of the biometric processing described in row A-3 whenever the Customer enables that feature.

5. Change-Notification Procedure and Right to Object

5.1 Publication. The current version of this list is permanently and publicly available at https://app.enigmasuite.com/legal/subprocessors.html. Each version indicates its number and last-updated date.

5.2 Changes requiring advance notice. EnigmaSuite will notify the Customer at least thirty (30) calendar days before the following take effect: (a) the addition of a new platform-level Subprocessor (Table A); and (b) a material change of purpose in the processing entrusted to an existing Subprocessor. Notice will be given by: (i) email to the Customer's organization administrators; and (ii) an in-app notice within the Platform.

5.3 Changes not requiring advance notice. The notice under Section 5.2 is not required for: (a) the removal of a Subprocessor; (b) changes to a Subprocessor's name or corporate structure that do not alter the processing; and (c) additions, removals, or changes of the Table B services, which depend exclusively on the Customer's own configuration and contracts.

5.4 Right to object. The Customer may object to the addition of a new Subprocessor, on reasonable and well-founded data protection grounds, by written notice to [email protected] within thirty (30) calendar days following the notification. Upon receipt of the objection, the parties will negotiate in good faith a reasonable solution (for example, an alternative configuration that avoids the use of the new Subprocessor for the Customer's data). If no solution can be reached within a reasonable time, the Customer may terminate the affected services as provided in the ToS and the DPA with a pro-rated refund of any fees paid in advance for the period not provided. Failure to object within the stated period will be deemed acceptance of the new Subprocessor.

5.5 Urgent replacements. If, for reasons of security, service continuity, or a provider's sudden cessation, it becomes necessary to replace or add a Subprocessor without observing the period in Section 5.2, EnigmaSuite may do so immediately, notifying the Customer as soon as reasonably practicable; the right to object under Section 5.4 will run from that notification.

5.6 Country addenda. Where a Country Addendum applies under the DPA (for example, for Customers or operations in the United States or Canada), that addendum may supplement or adjust the timeframes and mechanisms of this Section for the relevant jurisdiction.

6. Contact

6.1 For questions about this list or the Subprocessors, or to exercise the right to object: [email protected].

6.2 For the exercise of ARCO rights (access, rectification, cancellation, objection) by Data Subjects, please refer to EnigmaSuite's Comprehensive Privacy Notice (for data for which EnigmaSuite is Controller) or to the applicable Customer's privacy notice (for data for which the Customer is Controller).