Esta é a versão original. A versão em inglês é uma tradução.
O site recolhe informações durante a sua visita através do uso de cookies. Usamos esses cookies por diversos motivos, geralmente para distinguir você de outros usuários de nossos sites e para nos ajudar a compilar estatísticas agregadas sobre o uso de nossos sites.
Também usamos cookies para nos auxiliar a fornecer a você uma experiência positiva quando você navega em nosso site, para nos auxiliar a melhorar nosso conteúdo e a personalizar sua visita.
Cookies que usamos
Cookie
Para que serve
mt2-consent
Guarda a sua escolha no aviso de cookies (aceitar ou recusar) por 12 meses. Necessário para o site lembrar a sua decisão.
_ga, _ga_* (Google Analytics)
Medem visitas de forma agregada: páginas vistas, origem do acesso e tipo de dispositivo. Só são gravados se você clicar em “Aceitar”; se recusar, não são gravados e os existentes são apagados.
Você pode mudar a sua escolha a qualquer momento em Preferências de cookies, também disponível no rodapé de todas as páginas.
Você também pode controlar a aceitação de cookies modificando as preferências do navegador da Internet. Você tem a capacidade de aceitar todos os cookies, para ser notificado quando um cookie é definido ou para rejeitar todos os cookies. Por favor note que, se você optar por bloquear todos os cookies (incluindo cookies essenciais), você poderá não conseguir acessar todo ou parte do nosso site e poderá não conseguir utilizar esses serviços ou participar de atividades que exijam a colocação de cookies.
Quando você envia o formulário de contato ou conversa pelo chat, recebemos os dados que você informa para responder ao seu pedido.
Para exercer os seus direitos previstos na LGPD (Lei nº 13.709/2018), como acesso, correção ou exclusão dos seus dados, escreva para o Responsável de Dados em r.dados@mt2.page. Você também pode recorrer à Autoridade Nacional de Proteção de Dados (ANPD).
Como a MT2 trata os dados de clientes nos projetos está descrito na política de governança de dados, abaixo.
MT2 Serviços em Tecnologia da Informação Ltda
Política de governança e segurança de dados
Versão 1.2 · consolidada em 6 de novembro de 2026
Publicada em inglês (seção 1.6) e vinculante para prestadores e subcontratados autorizados com acesso a dados da MT2 ou de clientes, mediante incorporação expressa nos seus contratos (seção 1.2). A MT2 fornece uma versão ou explicação compreensível na incorporação inicial.
Data Governance & Security Policy (hosted, referenced by contract)
Governed by
Signed engagement instrument, NDA and applicable Project Data Handling Addendum; order of precedence in Section 1.5.
Applies to
All contractors and authorised subcontractors with access to MT2 or client data. Applicable operational rules also cover employees, subject to mandatory employment law.
Published at
https://mt2data.com/data-governance
Effective date
For each person, no earlier than actual publication and valid initial incorporation under Section 1.2. Subsequent versions follow Section 1.4.
Policy owner
MT2 Data Protection & Security function: Mattia Mossetti (mattia.mossetti@mt2.page) and Responsável de Dados (r.dados@mt2.page), or via the MT2 SPOC (Single Point of Contact) identified in your engagement
1. About This Policy
1.1 Nature and purpose
This Data Governance & Security Policy (the “Policy”) sets out MT2’s rules for access to and processing of MT2 and client data. MT2 maintains it as a living document at https://mt2data.com/data-governance. The current published version and the archived historical versions establish the content applicable at each time, subject to valid initial incorporation and the effective-date rules below.
1.2 Incorporation by reference
This Policy becomes binding through express incorporation into the Contractor Agreement, NDA or signed Project Data Handling Addendum confirming access to its contents and adherence to the update mechanism in Section 1.4. Once incorporated, updates to this Policy apply through publication at the designated URL, without individual notice, renewed acceptance or a signed amendment for each update. Employees may be subject to applicable operational security rules, but contractual changes remain subject to mandatory employment law.
1.3 Effective date
This consolidated edition takes effect for each Contractor no earlier than its actual publication and valid initial incorporation under Section 1.2, preserving actual signature dates. Subsequent versions follow Section 1.4. MT2 shall record actual publication and effective dates and preserve evidence of the content made available. The consolidation date is not proof of earlier publication or incorporation.
1.4 Changes to this Policy
MT2 may update this Policy from time to time, including to reflect changes in applicable law, technology, or MT2's data-protection practices.
Updates to this Policy shall be published at https://mt2data.com/data-governance and apply from the effective date stated in the publication, no earlier than their publication date, without individual notice, renewed acceptance or a signed amendment. Contractors and Subcontractors shall regularly consult the URL and comply with the current version.
MT2 may update governance, data-protection and security requirements within the subject matter of this Policy and require urgent lawful safeguards against a concrete security risk. Where implementation requires technical adaptation, the publication shall specify a reasonable implementation period compatible with the risk and applicable client obligations. Updates do not override mandatory law or the order of precedence in Section 1.5.
Each update shall identify its version and effective date and be recorded in an accessible change history. Historical versions shall be retained for reference.
1.5 Order of precedence
Between MT2 and the Contractor, the signed Project Data Handling Addendum and its Annex A prevail on Project data processing; the NDA governs other confidentiality matters; this Policy governs incorporated operational security requirements; and the engagement instrument governs other matters. MT2’s client agreements inform the obligations expressly flowed down, but do not automatically make Contractors parties to those agreements or import their financial, arbitration or liability regimes. Mandatory law and valid intellectual-property allocations remain unaffected. Updates to this Policy follow the publication mechanism in Section 1.4. Changes to remuneration, contractual penalties or other commercial terms of the engagement instrument are not made through this Policy.
1.6 Language
This Policy is published in English. MT2 shall provide an intelligible version or explanation upon initial incorporation. The prevailing language shall be the one identified in the signed engagement instrument or Project Addendum; English shall not override an expressly prevailing Portuguese version.
1.7 Universal baseline and project layer
This Policy supplies the baseline for every authorised role with access to MT2 or client data. A signed Project Data Handling Addendum applies to personnel allocated to that Project; it is not a prerequisite for unrelated roles to follow the baseline. Before any Project access, the required engagement, confidentiality commitments, approvals and Project documents must be in place. A generic template, unsigned Annex or software licence is not access authorisation.
2. Role, Data Context & Data Types
2.1 Scope of application
This Policy applies to any Contractor engaged by MT2 in a role that involves access to MT2 client data: including but not limited to data engineering, data analysis, data science, machine-learning engineering, business intelligence, integration engineering, project management with data access, and any other role in which the Contractor may view, retrieve, transform, transmit, or otherwise handle client data. Where a specific technical activity referenced below (e.g., pipeline configuration, SQL query authoring, dashboard publishing) does not apply to your specific role, the underlying principle still does.
2.2 Typical activities covered
Your work may include activities such as: building or maintaining data pipelines (Extract-Transform-Load / Extract-Load-Transform, i.e. ETL/ELT) that ingest, transform, or load client data; writing SQL queries against databases or data warehouses containing personal data; configuring and monitoring orchestration tools (e.g., Azure Data Factory, Databricks, dbt); producing analytical reports, dashboards (e.g., Power BI, Tableau), or exports that may surface client data; managing database schemas, credentials, or service connections; or otherwise interacting with client data or systems as part of your engagement.
Your access is often broader than most roles: potentially including read/write access to databases, pipeline configuration, and service principal credentials. This access must be treated as the highest-risk category and exercised with strict discipline.
2.3 Data types covered
This Policy covers all data you access, receive, or process in the course of your engagement, including:
Personal data: as defined under the Brazilian General Data Protection Law (LGPD, Lei nº 13.709/2018) and, where applicable, the EU General Data Protection Regulation (GDPR). Examples (e.g.): names, emails, phone numbers, addresses, CPFs, behavioural records, purchase history, engagement data.
Sensitive personal data: the statutory categories in LGPD Article 5(II), including racial or ethnic origin, religious belief, political opinion, union or religious, philosophical or political organisational affiliation, health or sex-life data, and genetic or biometric data linked to a natural person. GDPR Article 9 has its own categories and requirements, including biometric data processed to uniquely identify a person. Financial and credit data are confidential personal data where identifiable, but are not automatically statutory sensitive data under either provision.
Enterprise proprietary data: data of commercial value to MT2 or to MT2's clients. Examples (e.g.): client business logic, pricing tables, strategic documents, segmentation rules, customer lifetime-value calculations, model outputs and weights derived from client data, competitive intelligence, trade secrets.
All three categories are subject to the obligations in this Policy. Where a stricter standard applies to a specific category under applicable law (e.g., LGPD Art. 11 for sensitive personal data), the stricter standard also applies. If you are uncertain which category a given dataset falls into, treat it as the highest applicable category.
3. Personal Device Requirements
Control
Requirement
Encrypted “MT2 Client Data” folder
Local storage requires express Project authorisation. Use the designated encrypted storage and protect temporary files, caches and backups with approved device encryption and access controls. Folder encryption alone must not leave Project data exposed elsewhere. If compliant controls cannot be implemented, use only the approved remote environment with local download disabled.
Antivirus / endpoint protection
Active and up to date.
Supported OS
An operating-system version currently receiving vendor security updates, with security updates promptly applied. Unsupported or end-of-life versions are prohibited.
Screen lock
Auto-lock ≤5 minutes. Password or biometric.
Firewall
Operating-system-level firewall enabled.
No cloud sync on “MT2 Client Data” folder
The “MT2 Client Data” folder must be excluded from all personal cloud sync services (e.g., iCloud, personal OneDrive, Dropbox, Google Drive).
Power BI Desktop (if installed)
Use only the corporate MT2 or client account and workspace designated and authorised for the Project. No personal accounts or public workspaces. Apply approved encryption, access and retention controls to embedded data, local files and caches.
4. Day-to-Day Data Handling Obligations
4.1 Database and pipeline access
You receive named individual credentials for each system (e.g., database, Azure Data Factory, Databricks workspace). No shared service accounts for interactive use.
Use the minimum necessary permissions for each task. If read access is sufficient, do not request or accept write access.
Do not connect personal tools (e.g., DBeaver, TablePlus, local Power BI Desktop) directly to production databases without documented project-lead approval and compliance with the Project’s systems, security, client approvals and transfer restrictions. Use the approved managed compute environment.
All pipeline configurations containing connection strings or secrets must use Azure Key Vault or the approved equivalent secret-management system for the Project, not hardcoded values in JSON, YAML, or notebook configuration.
4.2 SQL query results and local exports
Exporting query results to local CSV or Excel files is one of the most common sources of personal data leakage. The rules:
Do not export raw personal data (e.g., names, emails, behavioural records) to local files unless necessary for the task and expressly authorised under the Project’s access, location and security rules.
When an approved local export is necessary: save it only in the approved encrypted environment (see Section 3). Follow MT2’s documented retention and disposal instructions as soon as the task is complete, preserving any required return or incident evidence. Do not accumulate unauthorised local copies.
Never open a data export in a spreadsheet and save it to a cloud-synced personal folder (e.g., iCloud, personal OneDrive, Dropbox).
Never email a data export containing personal or proprietary data from your personal email account.
Prefer approved aggregated or anonymised queries where the task permits. Do not anonymise, reidentify or repurpose client data contrary to the Project instructions; reduced identifiability does not itself authorise new uses.
4.3 Power BI, Tableau, and BI (Business Intelligence) tools
BI reports and connections to client data must use the corporate MT2 or client account designated for the Project, with approved authentication. Do not embed passwords or use personal accounts.
Publish reports only to the workspace and environment expressly authorised for the Project. A corporate subscription or tool brand alone is not authorisation.
Files containing client connections, embedded data or caches may be stored locally only when authorised, in the approved encrypted environment and subject to the Project’s retention and transfer controls.
Treat BI report files with embedded personal or confidential data, connections or caches as RESTRICTED. Verify actual content before any permitted sharing.
4.4 Credentials and service principals
Contractors with data access often handle the most sensitive credentials in the environment: storage account keys, service principal secrets, database passwords. These must be treated as high-value secrets.
Store credentials in the Project-approved secret-management system, such as Azure Key Vault or an authorised equivalent. Use secret references, not literal connection strings in code or configuration.
Service principal secrets must never be stored in (e.g.): .env files committed to git, spreadsheets, personal notes apps, or email.
Immediately report suspected credential exposure under Section 6 and coordinate prompt revocation or rotation by an authorised person. Perform containment within your authorised permissions, preserving evidence. Do not delay the notice while investigating or attempting to resolve the incident alone.
When your engagement ends, all service principals and access tokens created for your use must be revoked or rotated. This is not optional.
4.5 Version control and code
All pipeline code, dbt models, SQL scripts, and notebook code go to the MT2-designated repository. Not personal GitHub, not a local git repository that is never pushed.
Configure repository exclusions for data exports, credentials, private keys and secrets, including relevant .csv, .parquet, .xlsx, .env, credentials.json, .key and .pem files. File extensions alone are not a security control: inspect content and use approved secret-detection checks. Legitimate source-code configuration may be committed only after review and without protected data or secrets.
Review git diff before every commit: no data files, no credentials, no connection strings.
Pipeline deployment to production requires a code review from a second MT2 team member. No solo production deploys.
4.6 Logging and monitoring
MT2 shall implement appropriate logging for Project systems and notify authorised users of its scope, purpose, access and retention. Contractors shall preserve enabled logs and must not disable or tamper with them. Monitoring is limited to legitimate Project security and compliance needs, with access controls and protection of personal and third-party information; it does not authorise indiscriminate inspection of personal devices or activities.
If you notice unusual data access patterns (e.g., queries running under your credentials that you did not initiate), report immediately to the MT2 SPOC: this may indicate credential compromise.
4.7 Access, third parties and cross-border processing
Access is personal, limited to authorised purposes and least privilege, with MFA where supported and required. Third parties, new tools, overseas remote access, cloud-region changes and international transfers require prior documented MT2 approval, the client approvals required by the source instruments, and applicable legal safeguards. Before access, each authorised person must be bound by written confidentiality and data-protection commitments. Internal approval does not replace a legally valid transfer mechanism or client approval.
5. Specifically Prohibited Activities
Prohibited activity
Detail
Hardcoding credentials
No passwords, keys, or secrets in code, notebooks, or configuration files.
Personal cloud exports
No data exports in personal cloud storage (e.g., Dropbox, Google Drive, iCloud, personal OneDrive).
Personal BI workspaces
No client-connected reports published to personal Power BI or Tableau Public accounts.
Personal email for data
No data exports or pipeline outputs sent via personal email.
Unsanctioned SaaS (Software as a Service) connectors
No connecting client data to unapproved third-party integration tools (e.g., Zapier, Make, IFTTT) without explicit MT2 approval.
Unapproved LLM (Large Language Model) engines
No submission of protected MT2 or client data, including anonymised or aggregated derivatives, to AI or LLM services outside the expressly authorised Project scope and environments. Model training or validation within contracted Services requires documented MT2 instructions and required client approvals, without external reuse. Independently generated synthetic data may be used only within the source instrument’s permissions and MT2 approval. A licence alone is not permission to submit data or allow provider reuse.
Production changes without review
No direct production database modifications or pipeline deployments without a second reviewer.
Retaining data post-task or post-project
Follow Section 7 and the Project Addendum for secure handover and instructed return/deletion; do not retain unauthorised copies or destroy data or evidence before the required instructions.
6. Incident Reporting
Notify the MT2 SPOC immediately, in any event within 2 hours of suspicion, detection or awareness, if any of the following occur. Send available facts without waiting for confirmation or a complete investigation; supplement promptly. If receipt is not acknowledged, use the confirmed emergency backup contact in the Project Annex:
Device lost or stolen while containing project data or credentials.
Credentials or service principal secrets accidentally exposed (e.g., committed to git, sent by email).
Query results or pipeline outputs sent to an unauthorised destination.
Unauthorised access to systems under your credentials.
Pipeline error that may have exposed or misrouted personal or proprietary data.
Any inadvertent submission of client data to an unapproved LLM engine or third-party service.
Preserve evidence and assist containment, investigation, remediation and the response plan. Do not notify a client, data subject, regulator or other external party on your own initiative, except where legally required, with prior notice to MT2 where permitted. The internal two-hour ceiling is not permission to wait and does not extend any shorter client or statutory deadline.
7. End of Engagement: Cleanup Obligations
Promptly cease Project processing on exit, except as instructed for handover. Within 5 business days, or a shorter MT2 deadline required by a client obligation, securely hand over the data and records under your responsibility and identify all local exports, caches and other copies. Return or delete them only under documented MT2 instructions and the Project Addendum schedule, preserving the client’s choice of return and any lawfully required evidence.
Request revocation or rotation of service principal secrets and access tokens by the responsible administrator, or perform it within your authorised permissions, coordinating handover and preserving evidence.
Sign out of Azure AD, Power BI, Databricks, and all MT2 systems on your personal device.
Remove any SSH keys or certificates associated with MT2 infrastructure from your device.
Send written confirmation of actions actually completed, identifying data returned or deleted, access revoked, remaining copies, legal retention and outstanding actions with responsible persons and dates. Do not certify complete deletion before it has occurred; access revocation is not deletion.
7.1 Data-subject requests and training
Forward data-subject requests immediately to r.dados@mt2.page, copying mattia.mossetti@mt2.page, in any event within 24 hours of receipt. Preserve the relevant data and assist the response; do not answer on behalf of MT2 or a client, or confirm data, without documented instructions or a legal duty. Before first access and annually thereafter, complete MT2-designated training. MT2 shall keep individual identity, content/version, completion and date records. Equivalent applicable client training may be recorded when accepted by MT2.
8. Confidentiality Obligations
Confidentiality lasts for the applicable NDA period, never less than 5 years post-engagement once this term is validly incorporated, without reducing longer validly agreed periods. Personal data remain protected while processing or retention and legal duties subsist; trade secrets remain protected while retaining that status. Legitimate NDA exceptions remain subject to statutory personal-data protection.
Intellectual-property ownership and licences follow the engagement instrument, NDA and applicable Project Addendum. Client deliverables and data are protected accordingly, without transferring MT2’s pre-existing tools, background intellectual property or independently developed assets contrary to those instruments. No provision authorises reuse of confidential client data.
Where the signed Project Addendum identifies confidentiality beneficiaries, they may directly enforce the confidentiality obligations and claim damages for breach within applicable statutory and contractual limits, without excluding MT2’s rights or allowing double recovery. This Policy alone does not create unlimited liability to every MT2 client or automatic employee payroll deductions.
9. Governance, Contact & Reporting Concerns
9.1 Policy owner
This Policy is owned and operationally maintained by MT2’s Data Protection & Security function. Direct questions and approval requests to Mattia Mossetti (mattia.mossetti@mt2.page) and the Responsável de Dados (r.dados@mt2.page). MT2 manages systems, access, incidents, controls, publication and individual evidence. TDSA maintains the institutional archive of approved legal versions and their history on MT2’s behalf, using the exact published files and publication evidence supplied by MT2; that archival role does not transfer MT2’s operational security or data-protection responsibilities.
9.2 Reporting policy concerns and whistleblowing
Contractors who observe practices at MT2 or by other contractors that may violate this Policy — or applicable data protection law — are expected to report such concerns to the MT2 SPOC, to Mattia Mossetti (mattia.mossetti@mt2.page), or to the Responsável de Dados (r.dados@mt2.page). Reports made in good faith will be treated confidentially and will not adversely affect the reporting Contractor's engagement or standing with MT2.
9.3 Governing law
This Policy is governed by the laws of the Federative Republic of Brazil, without prejudice to other applicable mandatory law. GDPR applicability requires assessment under its territorial scope in Article 3; nationality of a data subject alone does not establish applicability.
Version History
Version
Date and summary of changes
v1.2
6 November 2026 (consolidation). Final consolidation of the TDSA-reviewed draft selected by MT2: publication-based updates, Project hierarchy, security controls, reporting, exit and evidence. Actual publication and effective dates must be recorded when hosted; this row does not certify past publication.
Earlier drafts
September–October 2026 (draft references). Retain original files and any actual publication evidence. Draft dates do not establish an effective historical version.