Personal Data Processing Agreement Data Processing Agreement (DPA)

This document governs the conditions under which Tess processes personal data as a processor, on behalf of corporate customers, in compliance with the Brazilian General Data Protection Law (LGPD — Law No. 13,709/2018) and the European Union General Data Protection Regulation (GDPR — Regulation (EU) 2016/679).

Version 03 · Last updated: September 2026 Trust Center Contact the DPO

This Personal Data Processing Agreement ("DPA") describes the conditions under which Tess Tecnologia LTDA. processes personal data as a processor, on behalf of corporate customers, in the provision of the Tess AI Platform services.

This is the public reference version. As between Tess and each customer, the DPA takes effect as an inseparable annex and addendum to the Services Agreement ("Main Agreement"). Corporate customers who need the formalized document may request it by email at dpo@tess.im.

This DPA applies both under the LGPD and under the GDPR. Where the processing is subject to Law No. 13,709/2018, Tess acts as operator (operadora) and the customer as controller (controlador). Where the processing is subject to Regulation (EU) 2016/679, Tess acts as a processor and the customer as a controller, and this instrument satisfies the contract required by Art. 28 of the GDPR. The obligations set out here apply to the extent that each of those laws applies.

This DPA does not apply to processing in which Tess acts as an independent controller — account data, billing, telemetry, and security — which is governed by the Privacy Policy and the Privacy Notice. The current list of sub-processors is published in the Tess Trust Center.

Controller

The corporate customer The legal entity identified in the Main Agreement, which determines the purposes and means of the processing of Personal Data ("CONTROLLER" or "CUSTOMER").

Processor

TESS TECNOLOGIA LTDA. Enrolled with the Brazilian Federal Revenue under CNPJ/MF No. 60.806.420/0001-91, with its principal place of business at Av. Prof. Pereira Reis, 76, Loja B, Santo Cristo, Rio de Janeiro, RJ, 20220-800, Brasil ("TESS" or "PROCESSOR").

Definitions

For the purposes of this Personal Data Processing Agreement ("DPA"), the definitions of the LGPD (Law No. 13,709/2018) apply and, where the processing is subject to the GDPR, the corresponding definitions of Regulation (EU) 2016/679. The terms controller and processor correspond, respectively, to controlador and operador under the LGPD, without prejudice to the following:

  • Personal Data: information relating to an identified or identifiable natural person, pursuant to Art. 5, I, of the LGPD.
  • Sensitive Personal Data: data concerning racial or ethnic origin, religious belief, political opinion, health, sex life, genetic data, or biometric data, pursuant to Art. 5, II, of the LGPD.
  • Data Subject: the natural person to whom the Personal Data processed under this DPA relates.
  • Controller: the CUSTOMER, which determines the purposes and means of the processing of Personal Data, pursuant to Art. 5, VI, of the LGPD and, where applicable, Art. 4(7) of the GDPR.
  • Processor: TESS, which processes Personal Data on behalf of the Controller, pursuant to Art. 5, VII, of the LGPD and, where applicable, Art. 4(8) of the GDPR.
  • Processing: any operation performed on Personal Data, pursuant to Art. 5, X, of the LGPD — collection, production, reception, classification, use, access, reproduction, transmission, distribution, processing, filing, storage, deletion, evaluation, control, modification, communication, transfer, dissemination, or extraction.
  • Security Incident: any adverse event, confirmed or suspected, related to a breach of the security of Personal Data, including unauthorized access, leakage, alteration, or accidental or unlawful loss.
  • Sub-processor: a third party engaged by the Processor to carry out, in whole or in part, Personal Data processing activities on behalf of the Controller.
  • ANPD: the Brazilian National Data Protection Authority (Autoridade Nacional de Proteção de Dados).
  • Applicable Data Protection Laws: all laws, regulations, and rules applicable to the protection of personal data, including, as applicable, the LGPD, the European Union General Data Protection Regulation (GDPR), the California Consumer Privacy Act (CCPA), and other related rules.
  • Controller Data: all data, content, files, information, prompts, outputs, logs, and metadata submitted, stored, processed, or generated in the context of the services, including Personal Data.
  • Affiliate: any entity that controls, is controlled by, or is under common control with a Party.
  • Data Subject Request: any request made by a Data Subject in connection with the exercise of their legal data protection rights.
  • Standard Contractual Clauses (SCCs): clauses approved by regulatory authorities to legitimize international data transfers.

Purpose and Scope

2.1The purpose of this DPA is to govern the conditions under which the PROCESSOR will process Personal Data on behalf of the CONTROLLER, within the scope and for the purposes of performing the Main Agreement, in accordance with Applicable Law, including the LGPD and the GDPR, to the extent each applies to the processing.

2.2This DPA forms an integral and inseparable part of the Main Agreement and applies to any and all processing of Personal Data carried out by the PROCESSOR by reason of the provision of the contracted services.

2.3The purpose of the processing shall be strictly limited to performance of the subject matter of the Main Agreement. The PROCESSOR may not process Personal Data for any other purpose, whether its own or that of a third party, including for training, developing, tuning, or improving artificial intelligence models, algorithms, or automated solutions, unless the CONTROLLER has given prior, express, and documented authorization.

2.4In the event of a conflict between this DPA and the Main Agreement with respect to obligations relating to the protection of Personal Data, the provisions of this DPA shall prevail.

2.5This DPA is the personal data processing instrument used by TESS both under the LGPD and under the GDPR. For CONTROLLERS subject to the LGPD, it satisfies the contracting obligations between controller and operator. For CONTROLLERS subject to the GDPR, it constitutes the contract between controller and processor required by Art. 28 of Regulation (EU) 2016/679, including as to the subject matter, duration, nature, and purpose of the processing, the type of personal data, the categories of data subjects, and the obligations and rights of the controller, as described in this DPA and its Annexes.

Roles of the Parties

3.1The CONTROLLER acts as controller of the Personal Data processed under this DPA and determines the purposes and means of the processing.

3.2The PROCESSOR acts as processor of the Personal Data, processing it exclusively on behalf of and in accordance with the documented instructions of the CONTROLLER, except where Applicable Law imposes a different obligation on the PROCESSOR, in which case the PROCESSOR shall inform the CONTROLLER in advance, unless such communication is prohibited on grounds of important public interest.

3.3If, in the course of performing the agreement, the Parties identify processing under joint controllership or independent controllership by the PROCESSOR for its own purposes, that arrangement shall be expressly agreed in a specific addendum. Until then, the processor regime set out in this DPA shall apply.

Description of the Processing

4.1The characteristics of the Personal Data processing covered by this DPA, including categories of data subjects, categories of data, purposes, operations carried out, duration, frequency, and the systems and environments involved, are described in Annex I, which shall be completed and kept up to date by the PROCESSOR, with validation by the CONTROLLER.

4.2Any material change to the scope of the processing described in Annex I shall be communicated to the CONTROLLER in advance. Such a change may not be implemented without the corresponding update of this Annex and, where required by Applicable Law, without the CONTROLLER's authorization.

Processor Obligations

The PROCESSOR shall:

5.1process Personal Data exclusively in accordance with the CONTROLLER's documented instructions and for the purposes set out in this DPA and the Main Agreement;

5.2ensure that persons authorized to process Personal Data are bound by a confidentiality obligation, whether contractual or statutory;

5.3adopt the technical and organizational information security measures set out in Annex II, appropriate to the nature, scale, risk, and scope of the processing;

5.4assist the CONTROLLER, to the extent reasonable and technically feasible, in responding to data subject requests and in complying with obligations under Applicable Law, including the preparation of impact assessments, where applicable;

5.5notify the CONTROLLER, without undue delay, of any Security Incident that may result in risk or relevant harm to Data Subjects, in accordance with Clause 11 of this DPA;

5.6not carry out an international transfer of Personal Data except in accordance with Clause 9 of this DPA;

5.7not subcontract the processing of Personal Data to Sub-processors except in accordance with Clause 8 of this DPA;

5.8delete or return the Personal Data at the end of the services, in accordance with the CONTROLLER's instructions and Clause 14 of this DPA, except where retention is required by law or regulation;

5.9make available to the CONTROLLER the information necessary to demonstrate compliance with the obligations set out in this DPA, including, where applicable, evidence of certifications, audit reports, or equivalent documentation.

Controller Obligations

The CONTROLLER shall:

6.1provide the PROCESSOR with lawful, clear, and documented instructions regarding the processing of Personal Data;

6.2ensure that it has an appropriate legal basis for the processing of Personal Data and for sharing it with the PROCESSOR, in accordance with Applicable Law;

6.3respond, to the extent it is responsible, to Data Subject requests relating to the exercise of rights under Applicable Law;

6.4inform the PROCESSOR in a timely manner of any material change that may affect the processing of Personal Data covered by this DPA.

Technical and Organizational Security Measures

7.1The PROCESSOR shall adopt, where appropriate to the nature, scale, risk, and scope of the processing, technical and organizational measures consistent with information security good practice, as detailed in Annex II of this DPA, which distinguishes mandatory minimum controls from additional controls applicable according to the risk involved.

7.2Certifications, seals, attestations of conformity, or audit reports maintained by the PROCESSOR (such as ISO 27001, SOC 2, or equivalents), as well as the date of the latest audit or security assessment, are published and kept up to date in the Trust Center, as indicated in Annex II, and may be required as complementary evidence of compliance, without prejudice to the minimum controls set out in this DPA.

7.3The CONTROLLER may, upon reasonable prior notice, request additional information about the security measures adopted by the PROCESSOR, subject to Clause 12 (Audit and Right of Oversight).

Subcontracting / Sub-processors

8.1The PROCESSOR may engage Sub-processors to process Personal Data under a general authorization of the CONTROLLER, hereby expressly granted in respect of the Sub-processors listed in the list published in the TESS Trust Center, provided that the PROCESSOR: (i) keeps that list up to date and publicly accessible; (ii) notifies the CONTROLLER in advance of any addition, replacement, or removal of a Sub-processor, with at least 15 (fifteen) calendar days' notice; and (iii) ensures the CONTROLLER's right to object, on reasoned grounds and in writing, within that period, to the engagement of a given Sub-processor. If a reasoned objection is raised, the Parties shall negotiate in good faith, for up to 30 (thirty) calendar days, a technically reasonable alternative; if no agreement is reached, the CONTROLLER may terminate, without charge or penalty, the services specifically affected by the objected subcontracting, and the Main Agreement shall remain in force as to the other services.

8.2The PROCESSOR remains fully liable to the CONTROLLER for its Sub-processors' compliance with the obligations set out in this DPA and shall contractually impose on them data protection obligations equivalent to those established here.

8.3Engaging a Sub-processor for the purpose of training artificial intelligence models, or involving the sharing of Personal Data for that purpose, requires the CONTROLLER's prior, express, and specific authorization. The general authorization in item 8.1 does not apply in that case.

List of sub-processors. The complete and current list of Tess Sub-processors — with the purpose, location, categories of data processed, and controls applicable to each — is published and kept up to date in the Tess Trust Center. The AI model providers listed there are engaged only when the CONTROLLER or its authorized users select the corresponding model or feature, and in no event are the data used to train models.

International Data Transfers

9.1The CONTROLLER acknowledges that the provision of the services involves, by its nature and architecture, an international transfer of Personal Data, and hereby expressly authorizes transfers to the countries, for the purposes, and to the Sub-processors described in Annex I and in the list of Sub-processors published in the Trust Center, which constitute, for all purposes of this Clause, valid and sufficient prior notice. Transfers to countries or sub-processors not described in Annex I or in that list shall require prior notice to the CONTROLLER, in the manner of Clause 8.1, and the adoption of the mechanisms required by Applicable Law, including, where relevant, standard contractual clauses, adequacy decisions, or other instruments recognized by the competent authority.

9.2Where required by Applicable Law or necessary to the lawfulness of an international transfer, the Parties shall adopt appropriate contractual, regulatory, and technical mechanisms, including standard contractual clauses or other instruments recognized by the ANPD or by a competent foreign authority, as applicable.

9.3Where there is an international transfer of Personal Data, the PROCESSOR shall state in Annex I and/or in the list of Sub-processors published in the Trust Center, before the processing begins or before any material change:

a)the destination countries or international organizations;

b)the categories of Personal Data involved;

c)the purpose of the transfer;

d)the sub-processors involved, if any; and

e)the legal, technical, and organizational safeguards adopted, in accordance with Applicable Law.

9.4If there is no international data transfer in the provision of the services, this Clause shall have no practical effect, and Annex I shall expressly state "not applicable".

Data Subject Rights

10.1The PROCESSOR shall assist the CONTROLLER, within a reasonable time and by appropriate technical and organizational measures, in responding to Data Subject requests relating to the exercise of rights under Applicable Law, such as confirmation of processing, access, correction, anonymization, deletion, portability, and information about data sharing.

10.2If the PROCESSOR receives a Data Subject request directly in relation to Personal Data processed on behalf of the CONTROLLER, it shall forward the request to the CONTROLLER within 5 (five) business days, unless a shorter period is necessary for the CONTROLLER to meet an applicable legal or regulatory deadline, and shall refrain from responding directly to the Data Subject unless the CONTROLLER instructs otherwise.

Security Incident Notification

11.1The PROCESSOR shall notify the CONTROLLER within 24 (twenty-four) hours of becoming aware of any Security Incident that may result in risk or relevant harm to Data Subjects, providing, to the extent possible, information on the nature of the incident, the categories and approximate number of Data Subjects and records affected, the likely consequences, and the measures taken or proposed to mitigate the risks.

Who the 24-hour period applies to. This DPA is entered into with corporate (enterprise) customers as an annex to the Main Agreement, and the 24-hour period in Clause 11.1 is a contractual obligation of Tess toward those customers. For other users of the Platform, incident communication follows the Privacy Notice and the time limits set out in applicable law, without prejudice to notifications to the ANPD, to the competent supervisory authority under the GDPR, and to data subjects.

11.2The PROCESSOR shall cooperate with the CONTROLLER in investigating the causes of the Security Incident, adopting corrective measures and, where applicable, complying with any obligations to notify the ANPD and the affected Data Subjects.

11.3The Parties shall designate a specific communication channel for Security Incident notifications. The PROCESSOR's channel is set out in Annex I.

Audit and Right of Oversight

12.1The CONTROLLER may, upon prior written notice of at least 15 (fifteen) calendar days and subject to the PROCESSOR's confidentiality and operational continuity requirements, carry out audits or inspections to verify compliance with the obligations set out in this DPA, either directly or through an independent third party it appoints, who may not be a competitor of the PROCESSOR and shall sign a confidentiality undertaking in favor of the PROCESSOR. Audits shall be limited to a maximum frequency of 1 (one) time every 12 (twelve) months, shall be conducted on business days and during business hours, without interrupting the PROCESSOR's operations, and shall be at the CONTROLLER's expense. The frequency limit does not apply in the event of a confirmed Security Incident affecting the CONTROLLER or of a substantiated indication of a breach of this DPA, in which cases the audit may be carried out at any time, upon 5 (five) business days' notice.

12.2Alternatively, the PROCESSOR may provide the CONTROLLER with independent audit reports, certifications, or equivalent compliance questionnaires, which the CONTROLLER may accept, at its discretion, in full or partial substitution for an on-site audit.

12.3The PROCESSOR shall grant the CONTROLLER reasonable access to the information strictly necessary to verify compliance with this DPA, protecting confidential information of third parties and of the PROCESSOR's other customers.

12.4If nonconformities are found in an audit, the PROCESSOR shall present the CONTROLLER with a corrective action plan within 15 (fifteen) calendar days of receipt of the final report, with owners and deadlines defined for each measure.

Confidentiality

13.1The PROCESSOR shall keep confidential all Personal Data and other confidential information to which it has access by reason of this DPA, and may not disclose, assign, or use them for any purpose other than that set out in this DPA and the Main Agreement.

13.2The confidentiality obligations in this Clause supplement, and do not exclude, any specific confidentiality obligations already set out in the Main Agreement.

Term, Retention, and Deletion of Data

14.1The PROCESSOR's processing of Personal Data shall remain in effect throughout the term of the Main Agreement and shall end automatically when the Main Agreement ends, except where retention is required by law or regulation or for the regular exercise of rights in judicial, administrative, or arbitral proceedings.

14.2When the services end, the PROCESSOR shall, in accordance with the CONTROLLER's instruction, return or delete all Personal Data processed by reason of the Main Agreement, including any copies, within the period stated in Annex I or, if no period is stated, within 30 (thirty) days of the end of the services.

14.3Backup copies that contain Personal Data may be deleted in the PROCESSOR's regular backup retention cycle, provided that, during that period, the data remain protected and inaccessible for any purpose other than disaster recovery.

Liability and Indemnity

15.1Each Party shall be liable for the damage it causes to Data Subjects or to the other Party as a result of a breach of the obligations set out in Applicable Law or in this DPA, to the extent of its respective participation in the processing that gave rise to the damage.

15.2Subject to the cap in Clause 15.3, the PROCESSOR shall indemnify and hold the CONTROLLER harmless from any losses, damages, fines, or administrative sanctions imposed by a competent authority that are proven to result from an act or omission of the PROCESSOR or its Sub-processors in breach of this DPA or of Applicable Law.

15.3The PROCESSOR's aggregate liability arising out of or relating to this DPA, together with liability arising out of the Main Agreement, is limited to the liability cap set out in the Main Agreement or, if none is specified, to the total amount actually paid by the CONTROLLER to the PROCESSOR in the 12 (twelve) months preceding the event giving rise to the liability. That limitation does not apply, and the breaching Party shall be liable without limit, in cases of willful misconduct, gross negligence, deliberate breach of confidentiality obligations, and other cases that cannot legally be waived.

15.4If the Parties adopt a specific liability cap for this DPA, that cap shall be stated in Annex I or in a separate addendum to the Main Agreement.

15.5Neither Party shall be liable to the other for lost profits, loss of revenue, loss of business opportunity, or indirect damages, except in cases that cannot legally be waived and for damage caused directly to Data Subjects.

General Provisions

16.1This DPA binds the Parties and their successors of any kind. Assignment of contractual position is prohibited without the prior consent of the other Party, except for an assignment resulting from a corporate transaction that does not materially change the conditions of Personal Data processing.

16.2A Party's tolerance of any breach of an obligation under this DPA shall not constitute novation, waiver, or amendment of the provisions set out here.

16.3If any provision of this DPA is held void, invalid, or unenforceable, the remaining provisions shall continue in full force and effect, and the Parties shall replace the affected provision with another that, to the greatest extent possible, preserves the Parties' original intent.

16.4This DPA may be updated at any time by a written addendum signed by both Parties, in particular because of changes in Applicable Law, in guidance from the ANPD, or from a competent supervisory authority under the GDPR.

Venue

17.1The venue set out in the Main Agreement is elected to resolve any disputes arising out of this DPA. If the Main Agreement contains no specific provision, the courts of the Judicial District of the Capital of the State of Rio de Janeiro/RJ are elected, with waiver of any other, however privileged.

Annex I — Detailed Description of the Processing

Description of the services provided

Provision of access to the Tess AI Platform, a multi-tenant SaaS solution that acts as a multimodal orchestrator of Generative Artificial Intelligence. The Platform routes the CONTROLLER's requests to third-party models (text/LLM, image, audio, transcription, and video) through TESS adaptive routing technology, without training its own models on the CONTROLLER's data.

Features: creation and execution of AI agents, templates, and automated workflows; knowledge bases with vector indexing (RAG); conversation history and workspaces; integrations and access via REST API (API-first, available from the Business plan); authentication via SSO (Google, Azure AD, Okta) and MFA.

Ancillary services, when contracted: technical support, training, prompt engineering (creation of agents, templates, and knowledge bases), allocation of a dedicated specialist, and development/customization of integrations and endpoints.

Role of the Processor

Pursuant to Art. 5, VII, of the LGPD and, where the processing is subject to the GDPR, Arts. 4(8) and 28 of Regulation (EU) 2016/679, in respect of all Personal Data submitted, generated, or stored by the CONTROLLER on the Platform. TESS processes such data exclusively in accordance with the CONTROLLER's documented and lawful instructions.

Independent controllership carve-out: TESS acts as an autonomous Controller, under its Privacy Policy, solely in respect of (i) account and billing data of the commercial relationship; and (ii) telemetry, log, and security data strictly necessary for operation, protection, fraud prevention, and compliance with legal obligations. That processing does not cover the CONTROLLER's content.

Purpose of the processing

Performance of the subject matter of the Main Agreement, namely: to make available, operate, maintain, monitor, and support the Tess AI Platform; to receive and process prompts, files, and content submitted by the CONTROLLER's authorized users for the generation of responses by AI models (inference); to store history, workspaces, agents, and knowledge bases; to record logs for security, audit, diagnostics, and consumption-based billing; and to provide technical support.

Express prohibition: the CONTROLLER's Personal Data and content are NOT used to train, tune, fine-tune, or improve artificial intelligence models, whether Tess's own or those of third parties, nor for any purpose of TESS's own, in accordance with Clauses 2.3 and 8.3 of this DPA.

Categories of Data Subjects
  • Authorized users of the CONTROLLER: employees, administrators, and other natural persons to whom the CONTROLLER grants access to the Platform.
  • Third parties of the CONTROLLER: customers, prospects, suppliers, candidates, or any other data subjects whose Personal Data the CONTROLLER chooses to include in prompts, files, knowledge bases, or integrations — in which case the categories of data subjects are determined exclusively by the CONTROLLER.
Categories of personal data
  • Account and registration data: name, corporate email, job title, company, user identifier, credentials (stored as a hash), roles, and permissions.
  • Access and usage data: IP address, date and time of access, browser, operating system, device, authentication and activity logs, credit/token consumption metrics, and execution history.
  • CONTROLLER content: prompts, files, and documents uploaded (text, image, audio, video), generated outputs, knowledge bases, embeddings, and agent configurations — the content of which is defined unilaterally by the CONTROLLER.
  • Billing data: legal name, CNPJ, billing details, and payment history. Full credit card data are collected and processed directly by the payment processors listed in the Trust Center and are NOT stored by TESS.
Sensitive personal data involved

No, by default. The Tess AI Platform is not intended, marketed, or configured for the processing of Sensitive Personal Data, and TESS does not request or deliberately collect such data.

If the CONTROLLER chooses to include Sensitive Personal Data in prompts, files, or knowledge bases, it does so under its sole responsibility as Controller. It is for the CONTROLLER to define and document the applicable legal basis (Art. 11 of the LGPD) and, if necessary, it may notify TESS in advance so that additional safeguards for those data can be assessed jointly.

Processing operations carried out

Collection/reception, access, storage, processing, inference by third-party AI models, transmission, indexing and vectorization (RAG), workflow orchestration, logging, security and performance monitoring, backups, technical support, export/portability, and deletion.

Duration of the processing

Throughout the term of the Main Agreement, ending automatically when the Main Agreement ends, subject to the return and deletion periods set out in Clause 14 and in this Annex I, and to any mandatory retention required by law or regulation.

Frequency of the processing

Continuous. Processing occurs automatically and without interruption whenever authorized users of the CONTROLLER use the Platform or its APIs.

Systems and environments involved

Tess AI Platform (web application and REST API), with logically segregated production, staging, and development environments. The CONTROLLER's real personal data travel exclusively in production; staging and development environments use anonymized or fictitious data.

The infrastructure runs on public cloud, on two providers:

  • Google Cloud Platform (GCP) — primary provider: operation in a Virtual Private Cloud (VPC), with containers and serverless functions (Cloud Run), a managed relational database (Cloud SQL), object storage (Cloud Storage), messaging (Pub/Sub), logging/monitoring, and a WAF (Cloud Armor).
  • Amazon Web Services (AWS) — secondary provider: compute, storage, networking, database, DNS, CDN, transactional email, backup, monitoring, and secrets management services used in the execution of the application services.

Complementary components: MongoDB Atlas (NoSQL database); a vector store for knowledge bases; Temporal (workflow orchestration); Cloudflare and Google Cloud Armor (CDN, WAF, DDoS mitigation, and DNS); Sentry and Google Cloud Logging/Monitoring (observability); and APIs of the AI model providers listed in the Trust Center.

All infrastructure is managed as code (Terraform), with no use of removable media, on-premises servers, or external file repositories (Google Drive, OneDrive, Box) for customer data. Isolation between customers is by logical segregation.

Place of storage / processing

United States of America, as the primary region for storage and processing, on public cloud infrastructure of Google Cloud Platform (primary provider), Amazon Web Services (secondary provider), and MongoDB Atlas.

Brazil: processing of domestic payments and traffic served by edge points of presence located in the country. In addition, for corporate customers that require data residency in national territory, TESS can make available a full private environment, with dedicated storage and processing within Brazil, under a specific contract.

Cloudflare operates a multi-regional edge network (processing of traffic, headers, and access logs at global points of presence, including Brazil).

AI model providers process prompts and outputs at inference time, predominantly in the United States, as listed in the Trust Center.

International data transfer

Yes — bilaterally between Brazil and the United States.

Brazil → United States flow: data submitted by authorized users in Brazil are transferred for hosting, storage, processing, and inference by AI models in the primary region, in the United States.

United States → Brazil flow: generated outputs and stored content return to Brazil whenever they are accessed or displayed to the CONTROLLER's authorized users. There is also processing in national territory for domestic payments and for traffic served by the edge network.

Destination countries: the United States of America (primary region) and Brazil, as well as the other locations of the sub-processors listed in the Trust Center, including processing on a multi-regional edge network.

Exception — data residency in Brazil: for corporate customers with a full private environment, contracted specifically to keep storage and processing within national territory, the international transfer described in this clause does not apply, subject to the conditions agreed in a separate addendum.

Categories involved: all categories described in this Annex I.

Purpose: hosting, storage, processing, inference by AI models, security, observability, payments, and technical support, strictly for performance of the Main Agreement.

Safeguards adopted (Arts. 33 to 36 of the LGPD): execution of a DPA and Standard Contractual Clauses (SCCs) with each sub-processor; enterprise/commercial API contracts with AI providers, expressly prohibiting the use of data to train models; encryption in transit (TLS 1.2 or higher) and at rest (AES-256); logical segregation by customer; least-privilege access control; and verification that sub-processors maintain SOC 2 Type II, ISO/IEC 27001, or equivalent attestations. For CONTROLLERS subject to the GDPR, the European Commission's SCCs may be adopted.

TESS provides reasonable assistance to the CONTROLLER in preparing Transfer Impact Assessments (TIAs).

Sub-processors involved

The complete and current list of Sub-processors — with the purpose, location, categories of data processed, and controls applicable to each — is published and kept up to date in the Tess Trust Center.

TESS will notify the CONTROLLER at least 15 (fifteen) calendar days in advance of any addition, replacement, or removal of a Sub-processor, with the right of reasoned objection preserved, in accordance with Clause 8.

Security incident communication channel

Primary email (monitored): dpo@tess.im

Secondary email: support@tess.im

Processor privacy contact point (DPO)

Data Protection Officer (DPO): DPO services are provided on behalf of TESS by Open CyberSecurity, a consultancy specialized in privacy and information security engaged to support LGPD/GDPR compliance.

Email: dpo@tess.im

Address: Av. Prof. Pereira Reis, 76, Loja B, Santo Cristo, Rio de Janeiro, RJ, 20220-800, Brasil.

Time limit for return / deletion after the agreement ends

Export: Controller Data may be self-exported on the platform, or otherwise made available for export in a structured, open, and machine-readable format (JSON, CSV, or SQL dump), during a transition period of 20 (twenty) calendar days after the contractual relationship ends, before any deletion.

Deletion: definitive and secure deletion in production environments within 30 (thirty) calendar days of the end of the services, with issuance of a formal certificate of destruction stating the date, scope (production, staging, backups, and logs), and methodology used.

Backups: deleted in TESS's regular backup retention cycle, remaining until then encrypted and inaccessible for any purpose other than disaster recovery, in accordance with Clause 14.3.

Residual retention: only where required by a legal or regulatory obligation, for the regular exercise of rights, or for fraud prevention, always with data minimization. Security logs are retained for at least 30 (thirty) days.

Specific liability cap under this DPA

Defined between the Parties in the Main Agreement or in a separate addendum. If no specific cap is agreed, the liability cap set out in the Main Agreement applies, except in cases of willful misconduct, gross negligence, and the other exceptions that cannot legally be waived, as set out in Clause 15.3.

Use of data to train AI models

Prohibited. No data entered on the Platform is used for machine learning, training, tuning, or improvement of foundation models, whether Tess's own or those of third parties. Data travel strictly for inference in the contracted session.

TESS's contracts with AI model providers are entered into on an enterprise/commercial API basis, with clauses prohibiting the use of data to improve the provider's services and, where available, zero data retention.

TESS does not sell, license, assign, monetize, combine, or enrich Controller Data with data of other customers or from its own sources.

AI models and routing

The Platform has no proprietary model trained by TESS. Requests are routed to third-party models according to the user's choice or the Platform's adaptive routing. The providers actually engaged are listed in the Trust Center and are engaged only when the CONTROLLER selects the corresponding model or feature.

Automated decisions: the Platform is a support tool and does not itself make decisions with legal effects on Data Subjects. Any use of outputs for that purpose is the CONTROLLER's exclusive decision and responsibility, and it is for the CONTROLLER to ensure human review pursuant to Art. 20 of the LGPD.

Documented instructions of the Controller

The CONTROLLER's documented instructions are: (i) the Main Agreement; (ii) this DPA and its Annexes; (iii) the settings, permissions, and parameters defined by the CONTROLLER on the Platform; and (iv) additional instructions formalized in writing between the Parties.

TESS will promptly inform the CONTROLLER if it considers that a given instruction violates Applicable Law.

Assistance with data subjects, DPIA, and RoPA

Data Subject requests (DSARs): TESS assists the CONTROLLER within no more than 5 (five) business days and does not respond directly to Data Subjects without the CONTROLLER's prior authorization, except where a legal obligation requires otherwise (Clause 10).

RIPD/DPIA: TESS provides reasonable assistance in preparing Personal Data Protection Impact Reports, risk assessments, and any consultations with the ANPD, supplying technical and organizational information about the processing.

RoPA: TESS maintains a record of processing activities carried out on behalf of the CONTROLLER and makes it available upon request and under an NDA.

Service level and continuity

Contracted availability: 99% (ninety-nine percent), except for scheduled downtime communicated at least 8 (eight) hours in advance and events of force majeure.

Support: remote, by chat and email, with a response on the next business day (9:00 to 18:00), in accordance with the Main Agreement.

Third-party dependency: if AI model provider APIs are unavailable, the corresponding feature may be temporarily suspended or routed to an alternative provider.

Annex II — Minimum Required Security Measures

The PROCESSOR shall adopt, at a minimum, the mandatory minimum controls listed below. Additional controls shall be adopted whenever the processing involves access to critical systems, a large volume of data, Sensitive Personal Data, or information technology services, according to the applicability indicated by the PROCESSOR and validated by the CONTROLLER.

Mandatory minimum controls (applicable to every Processor)

  • Individualized access to systems, with a prohibition on sharing credentials;
  • Use of strong passwords and, where technically available, multi-factor authentication (MFA);
  • Access control based on the principle of least privilege necessary to perform the activities;
  • A contractual confidentiality commitment and guidance for persons with access to Personal Data;
  • Keeping devices, operating systems, and software up to date;
  • Adoption of mechanisms to protect against malicious software and unauthorized access;
  • Notification of Security Incidents to the CONTROLLER within 24 (twenty-four) hours of becoming aware;
  • Secure disposal or return of Personal Data at the end of the processing, in accordance with Clause 14;
  • Appropriate management of Sub-processors, where applicable, in accordance with Clause 8.

Additional controls (according to risk, criticality, and applicability)

  • Encryption of Personal Data in transit and at rest;
  • Generation, retention, and monitoring of system access and usage logs;
  • Periodic security testing, vulnerability scanning, and patch management;
  • Use of threat detection and response solutions (EDR/SIEM or equivalents);
  • A Business Continuity Plan (BCP) and a Disaster Recovery Plan (DRP), with defined RTO and RPO;
  • Recognized certifications (for example, ISO/IEC 27001, SOC 2, or equivalents), where available;
  • Independent information security audits;
  • Periodic reviews of granted access and timely disabling of unused access.

Controls actually adopted by Tess

Minimum controls actually adopted

All mandatory minimum controls are adopted by TESS, as detailed below:

  1. Individualized access: unique identifiers per user on all systems, with a contractual and technical prohibition on sharing credentials.
  2. Passwords and MFA: the Platform requires a password of at least 8 characters (uppercase, lowercase, and a number); multi-factor authentication (2FA/MFA) is enabled for all TESS personnel and for privileged access; support for SSO (Google, Azure AD, Okta), OAuth, and OTP.
  3. Least privilege: role-based access control (RBAC), with a formal grant workflow, approval by a designated approver, and dual approval for privileged access.
  4. Confidentiality: a Code of Conduct and confidentiality clauses/agreements signed by all personnel; background checks at hiring; security and privacy training at onboarding and on an ongoing basis.
  5. Updates: infrastructure 100% in the cloud, managed as code (Terraform); patches monitored monthly, tested in staging, and deployed by automation, with a hotfix protocol for critical emergencies.
  6. Protection against malicious software and unauthorized access: WAF (Cloudflare and Google Cloud Armor) with protection against the OWASP Top 10, SQLi, and XSS; Super Bot Fight Mode; firewalls, IPS, and VPN; internal network segmented in a VPC; rate limiting and input validation on APIs.
  7. Incident notification to the CONTROLLER within 24 (twenty-four) hours of becoming aware, in accordance with Clause 11 and the Incident Response Plan.
  8. Secure disposal/return at the end of the processing, in accordance with Clause 14.
  9. Sub-processor management formalized, with third-party risk assessment, a DPA or equivalent terms, and data protection obligations equivalent to those of this DPA (Clause 8).
Additional controls actually adopted

Applicable and actually adopted:

  • Encryption: data in transit with TLS 1.2 or higher (HTTPS) and at rest with AES-256; use of RSA and AES; key management performed by the cloud provider under TESS administration. Customer-managed keys (BYOK/CMEK) are not supported.
  • Logs: generation, centralization, and monitoring of access and usage logs, with a minimum retention of 30 (thirty) days and access restricted to administrators; monitoring of privileged access and detection of anomalous behavior and misconfigurations.
  • Vulnerability management: systemic scans 2 (two) times per week; remediation SLA of up to 15 days for critical vulnerabilities, 30 days for high, and 45 days for medium; automated code review, dependency analysis, and vulnerability remediation before promotion to production (UAT).
  • Detection and response: multi-layer cloud protection (WAF, Cloud Armor, network scans, and logical protections in the VPC) and continuous observability (Sentry, Cloud Monitoring).
  • BCP/DRP: daily encrypted backups, with the type (full, incremental, or hybrid) defined by the criticality of the asset, and restore tests performed on the same annual cycle. RTO and RPO defined according to technical and commercial feasibility.
  • Independent security testing: penetration tests and adversarial Red Team exercises conducted by specialized partners, at least annually and additionally upon each relevant launch of a new function or service.
  • Access review: periodic review at least annually; revocation of credentials, API tokens, and integration keys within 48 (forty-eight) hours of termination or a change of role.
  • Governance: Information Security and Privacy Committee; appointed DPO; security and privacy policies published in the Trust Center and reviewed annually; a formal risk management program with a risk register; a whistleblowing channel via the DPO email, with a non-retaliation policy.
  • Environment segregation: production, staging, and development logically segregated; customers' real personal data are not used in non-production environments (anonymized data only).
Current certifications / seals

TESS's current certifications, seals, attestations of conformity, and audit reports are published and kept up to date in the Tess Trust Center.

Restricted-access documents — including certification, penetration-test, and Red Team reports, as well as sub-processor attestations, where available — must be requested directly in the Trust Center. Where required, disclosure is subject to access approval and the signing of an NDA.

Date of the latest audit / security assessment

The date of the latest audit, of the security assessments, and of the corresponding reports is published and kept up to date in the Tess Trust Center.

Contact and Data Protection Officer

Tess Tecnologia LTDA.

Processor Tess Tecnologia LTDA. — CNPJ 60.806.420/0001-91
Address Av. Prof. Pereira Reis, 76, Loja B, Santo Cristo, Rio de Janeiro, RJ, 20220-800, Brasil
DPO DPO services are provided on behalf of Tess by Open CyberSecurity, a consultancy specialized in privacy and information security engaged to support LGPD/GDPR compliance.
Incidents and DPA dpo@tess.im · support@tess.im
Sub-processors and evidence Trust Center · Status page