{"id":336,"date":"2025-06-26T16:36:38","date_gmt":"2025-06-26T13:36:38","guid":{"rendered":"https:\/\/mapsly.com?page_id=336"},"modified":"2026-08-18T13:31:19","modified_gmt":"2026-08-18T10:31:19","slug":"dpa","status":"publish","type":"page","link":"https:\/\/mapsly.com\/pt\/dpa\/","title":{"rendered":"ADENDO DE PROCESSAMENTO DE DADOS MAPSLY"},"content":{"rendered":"
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Adendo de Processamento de Dados<\/h1>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Last updated: July 31, 2026. This version supersedes the version last updated September 15, 2023.<\/i><\/p>

Este Acordo Adicional de Processamento de Dados (\u201cDPA\u201d) \u00e9 um acordo entre voc\u00ea e a entidade que voc\u00ea representa (\u201cCliente\u201d, \u201cvoc\u00ea\u201d ou \u201cseu\u201d) e a Mapsly LLC (\u201cMAPSLY\u201d). Este DPA complementa os Termos de Servi\u00e7o da MAPSLY dispon\u00edveis em https:\/\/mapsly.com\/terms<\/a>, as updated from time to time between Customer and MAPSLY, or other agreements between Customer and MAPSLY that govern Customer\u2019s use of the MAPSLY Services (the \u201cAgreement\u201d). \u201cCustomer\u201d refers to the entity defined as \u201cUser\u201d under the MAPSLY Terms of Service. This DPA applies to the extent MAPSLY processes Customer Data on Customer\u2019s behalf in providing the Services.<\/p>

Defini\u00e7\u00f5es. Todos os termos em mai\u00fasculas usados neste DPA ter\u00e3o os significados que lhes forem atribu\u00eddos abaixo, salvo se definido de outra forma no Contrato:<\/p>

\u201cAPI\u201d<\/span><\/b> significa uma interface de programa\u00e7\u00e3o de aplica\u00e7\u00f5es.<\/p>

\u201cApplicable Data Protection Law\u201d<\/span><\/b> means all laws and regulations applicable to and binding on the processing of Customer Data by a party, including, as applicable, the GDPR, the UK GDPR and the UK Data Protection Act 2018, the Swiss Federal Act on Data Protection (\u201cFADP\u201d), and applicable United States federal and state privacy laws (including the California Consumer Privacy Act, as amended).<\/p>

\u201cBinding Corporate Rules\u201d<\/span><\/b> tem o significado que lhe \u00e9 dado no GDPR.<\/p>

\u201cController\u201d<\/span><\/b> tem o significado que lhe \u00e9 dado no GDPR.<\/p>

\u201cController-to-Processor Clauses\u201d<\/span><\/b> significa as cl\u00e1usulas contratuais padr\u00e3o entre Controladores e Processadores para Transfer\u00eancias de Dados, conforme aprovado pela Decis\u00e3o de Execu\u00e7\u00e3o da Comiss\u00e3o Europeia (UE) 2021\/914 de 4 de junho de 2021.<\/p>

\u201cCustomer Data\u201d<\/span><\/b> means the Personal Data that is uploaded to or generated within the Services under Customer\u2019s MAPSLY accounts, excluding the End-User account and usage information described in Section 1.5.<\/p>

\u201cData Privacy Framework\u201d or \u201cDPF\u201d<\/span><\/b> means, together, the EU-U.S. Data Privacy Framework, the UK Extension to the EU-U.S. Data Privacy Framework, and the Swiss-U.S. Data Privacy Framework, as administered by the U.S. Department of Commerce.<\/p>

\u201cDocumentation\u201d<\/span><\/b> significa a documenta\u00e7\u00e3o vigente na \u00e9poca para os Servi\u00e7os localizada em https:\/\/help.mapsly.com<\/a> (e quaisquer locais sucessores designados pelo MAPSLY).<\/p>

\u201cEEA\u201d<\/span><\/b> significa o Espa\u00e7o Econ\u00f3mico Europeu.<\/p>

\u201cEnd Users\u201d<\/span><\/b> refere-se aos usu\u00e1rios da conta Mapsly do Cliente, incluindo funcion\u00e1rios e contratados do Cliente que foram designados pelo Cliente para usar o Mapsly.<\/p>

\u201cGDPR\u201d<\/span><\/b> significa o Regulamento 2016\/679 do Parlamento Europeu e do Conselho, de 27 de abril de 2016, relativo \u00e0 prote\u00e7\u00e3o das pessoas singulares no que diz respeito ao tratamento de dados pessoais e \u00e0 livre circula\u00e7\u00e3o desses dados, e que revoga a Diretiva 95\/46\/CE (Regulamento Geral sobre a Prote\u00e7\u00e3o de Dados).<\/p>

\u201cMAPSLY Network\u201d<\/span><\/b> significa os servidores, equipamentos de rede e sistemas de software host (por exemplo, firewalls virtuais) que est\u00e3o sob o controle da MAPSLY e s\u00e3o usados para fornecer os Servi\u00e7os.<\/p>

\u201cMAPSLY Setup console\u201d<\/span><\/b> significa a se\u00e7\u00e3o Configura\u00e7\u00e3o no servi\u00e7o Mapsly dispon\u00edvel em \u201cConfigura\u00e7\u00e3o\u201d no menu principal.<\/p>

\u201cPersonal Data\u201d<\/span><\/b> significa dados pessoais, informa\u00e7\u00f5es pessoais, informa\u00e7\u00f5es pessoalmente identific\u00e1veis ou outro termo equivalente (cada um conforme definido na Lei de Prote\u00e7\u00e3o de Dados Aplic\u00e1vel).<\/p>

\u201cProcessing\u201d<\/span><\/b> tem o significado dado a ele no RGPD e \u201cprocessar\u201d, \u201cprocessos\u201d e \u201cprocessado\u201d ser\u00e3o interpretados de acordo.<\/p>

\u201cProcessor\u201d<\/span><\/b> tem o significado que lhe \u00e9 dado no GDPR.<\/p>

Cl\u00e1usulas de Processador para Processador<\/span><\/b> means the standard contractual clauses between Processors for Data Transfers, as approved by the European Commission Implementing Decision (EU) 2021\/914 of 4 June 2021.<\/p>

Incidente de seguran\u00e7a<\/span><\/b> significa uma viola\u00e7\u00e3o da seguran\u00e7a da MAPSLY que leva \u00e0 destrui\u00e7\u00e3o, perda, altera\u00e7\u00e3o acidental ou il\u00edcita, divulga\u00e7\u00e3o n\u00e3o autorizada ou acesso a Dados do Cliente.<\/p>

Controles de Servi\u00e7o<\/span><\/b> significa os controles, incluindo os recursos e funcionalidades de seguran\u00e7a, que os Servi\u00e7os fornecem, conforme descrito na Documenta\u00e7\u00e3o.<\/p>

\u201cStandard Contractual Clauses\u201d<\/span><\/b> means (i) the Controller-to-Processor Clauses, or (ii) the Processor-to-Processor Clauses, as applicable in accordance with Sections 9.2.1 and 9.2.2, as supplemented, where applicable, by the UK Addendum (for Data Transfers subject to the UK GDPR) and by the Swiss adaptations described in Section 9.2.4 (for Data Transfers subject to the FADP).<\/p>

Pa\u00eds terceiro<\/span><\/b> means a country outside the EEA, the United Kingdom, or Switzerland not recognized by the European Commission (or, as applicable, by the competent United Kingdom or Swiss authorities) as providing an adequate level of protection for personal data (as described in the GDPR, the UK GDPR, or the FADP, as applicable).<\/p>

\u201cUK Addendum\u201d<\/span><\/b> means the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses issued by the UK Information Commissioner, in force 21 March 2022.<\/p>

\u201cUK GDPR\u201d<\/span><\/b> means the GDPR as it forms part of the law of the United Kingdom by virtue of section 3 of the European Union (Withdrawal) Act 2018.<\/p>

1. Data Processing<\/h2>

1.1 Scope and Roles.<\/span><\/b> Este DPA aplica-se quando a MAPSLY processa Dados do Cliente. Neste contexto, a MAPSLY atuar\u00e1 como Processador para o Cliente, que pode atuar como Controlador ou Processador dos Dados do Cliente.<\/p>

1.2 Customer Controls.<\/span><\/b> O Cliente pode usar os Controles de Servi\u00e7o para auxili\u00e1-lo nas suas obriga\u00e7\u00f5es sob a Lei de Prote\u00e7\u00e3o de Dados Aplic\u00e1vel, incluindo as obriga\u00e7\u00f5es de responder a pedidos de titulares de dados. Levando em considera\u00e7\u00e3o a natureza do processamento, o Cliente concorda que \u00e9 improv\u00e1vel que a MAPSLY tome conhecimento de que os Dados do Cliente transferidos sob as Cl\u00e1usulas Contratuais Padr\u00e3o est\u00e3o incorretos ou desatualizados. No entanto, se a MAPSLY tomar conhecimento de que os Dados do Cliente transferidos sob as Cl\u00e1usulas Contratuais Padr\u00e3o est\u00e3o incorretos ou desatualizados, informar\u00e1 o Cliente sem demora indevida. A MAPSLY cooperar\u00e1 com o Cliente para apagar ou retificar Dados do Cliente incorretos ou desatualizados transferidos sob as Cl\u00e1usulas Contratuais Padr\u00e3o, fornecendo os Controles de Servi\u00e7o que o Cliente pode usar para apagar ou retificar os Dados do Cliente.<\/p>

1.3 Details of Data Processing.<\/span><\/b><\/p>

1.3.1 Subject matter.<\/span><\/b> O objeto do processamento de dados sob este DPA s\u00e3o os Dados do Cliente.<\/p>

1.3.2 Duration.<\/span><\/b> The processing continues for the Term of the Agreement and thereafter for the limited period necessary to return, delete, or lawfully retain Customer Data in accordance with Section 11.<\/p>

1.3.3 Purpose.<\/span><\/b> O objetivo do processamento de dados sob este DPA \u00e9 a presta\u00e7\u00e3o dos Servi\u00e7os iniciados pelo Cliente de tempos em tempos.<\/p>

1.3.4 Nature of the processing.<\/span><\/b> Compute, storage, geocoding, routing, synchronization with Customer\u2019s connected systems, and such other Services as described in the Documentation and initiated by Customer from time to time, including, where Customer uses AI-based features of the Services, processing by AI model providers engaged as Sub-processors solely to provide the Services to Customer. MAPSLY does not use Customer Data to train generalized artificial intelligence or machine learning models.<\/p>

1.3.5 Type of Customer Data.<\/span><\/b> Customer Data uploaded to or generated within the Services under Customer\u2019s MAPSLY accounts, which may include contact and CRM records, addresses and other location data (including precise geolocation of End Users where Customer enables location tracking, check-in, or similar features), photos, notes, form responses, audio recordings and transcripts (where Customer uses voice or AI-based features), and automation and activity data.<\/p>

1.3.6 Categories of data subjects.<\/span><\/b> The data subjects could include Customer\u2019s customers, prospects and leads, employees, suppliers and End Users.<\/p>

1.4 Compliance with Laws.<\/span><\/b> Cada parte cumprir\u00e1 todas as leis, regras e regulamentos a ela aplic\u00e1veis e vinculativos no desempenho deste DPA, incluindo a Lei de Prote\u00e7\u00e3o de Dados Aplic\u00e1vel.<\/p>

1.5 Mapsly as Controller.<\/span><\/b> Customer acknowledges that Mapsly collects certain information about Customer\u2019s End Users \u2014 such as account, authentication, billing, support, and usage information \u2014 as described in the MAPSLY Privacy Policy (currently published at https:\/\/mapsly.com\/privacy-policy<\/a>). To the extent Mapsly determines the purposes and means of processing such information, Mapsly acts as an independent Controller of that information and processes it in accordance with the MAPSLY Privacy Policy and Applicable Data Protection Law; such information is not Customer Data processed under this DPA. Mapsly may disclose such information internally and to its service providers for legitimate business purposes relating to the operation, support, and improvement of the Services, such as billing, account management, technical support, and product development.<\/p>

2. Customer Instructions<\/h2>

The parties agree that this DPA and the Agreement (including Customer providing instructions via configuration tools such as the MAPSLY Setup console and APIs made available by MAPSLY for the Services) constitute Customer\u2019s documented instructions regarding MAPSLY\u2019s processing of Customer Data (\u201cDocumented Instructions\u201d). MAPSLY will process Customer Data only in accordance with Documented Instructions (which if Customer is acting as a Processor, could be based on the instructions of its Controllers). Additional instructions outside the scope of the Documented Instructions (if any) require prior written agreement between MAPSLY and Customer, including agreement on any additional fees payable by Customer to MAPSLY for carrying out such instructions. Where an additional instruction is required for Customer\u2019s compliance with Applicable Data Protection Law and the parties are unable, within thirty (30) days, to reasonably agree on its implementation and any applicable fees, Customer may terminate the affected Services by written notice, and MAPSLY will refund Customer the prepaid fees prorated for the unused portion of the then-current Billing Period for the terminated Services. Taking into account the nature of the processing, Customer agrees that it is unlikely MAPSLY can form an opinion on whether Documented Instructions infringe Applicable Data Protection Law. If MAPSLY forms such an opinion, it will immediately inform Customer, in which case, Customer is entitled to withdraw or modify its Documented Instructions.<\/p>

3. Confidentiality of Customer Data<\/h2>

A MAPSLY n\u00e3o acessar\u00e1, usar\u00e1 ou divulgar\u00e1 a terceiros quaisquer Dados do Cliente, exceto, em cada caso, conforme necess\u00e1rio para manter ou fornecer os Servi\u00e7os, ou conforme necess\u00e1rio para cumprir a lei ou uma ordem v\u00e1lida e vinculativa de um \u00f3rg\u00e3o governamental (como uma intima\u00e7\u00e3o ou ordem judicial). Se um \u00f3rg\u00e3o governamental enviar \u00e0 MAPSLY uma solicita\u00e7\u00e3o por Dados do Cliente, a MAPSLY tentar\u00e1 redirecionar o \u00f3rg\u00e3o governamental para solicitar esses dados diretamente ao Cliente. Como parte desse esfor\u00e7o, a MAPSLY pode fornecer ao \u00f3rg\u00e3o governamental as informa\u00e7\u00f5es b\u00e1sicas de contato do Cliente. Caso seja obrigada a divulgar os Dados do Cliente a um \u00f3rg\u00e3o governamental, a MAPSLY fornecer\u00e1 ao Cliente um aviso razo\u00e1vel da solicita\u00e7\u00e3o para permitir que o Cliente busque uma ordem de prote\u00e7\u00e3o ou outro recurso apropriado, salvo se a MAPSLY estiver legalmente proibida de faz\u00ea-lo.<\/p>

4. Confidentiality Obligations of MAPSLY Personnel<\/h2>

A MAPSLY restringe seu pessoal de processar Dados de Clientes sem autoriza\u00e7\u00e3o da MAPSLY. A MAPSLY imp\u00f5e ao seu pessoal obriga\u00e7\u00f5es contratuais apropriadas, incluindo obriga\u00e7\u00f5es relevantes relativas \u00e0 confidencialidade, prote\u00e7\u00e3o de dados e seguran\u00e7a de dados.<\/p>

5. Security of Data Processing<\/h2>

5.1<\/span><\/b> MAPSLY has implemented and will maintain the appropriate technical and organizational measures to ensure the security and confidentiality of the Customer Data, as described in Annex A (Technical and Organizational Measures) to this DPA and in accordance with Mapsly\u2019s security standards described in this DPA and within the MAPSLY Privacy Policy. MAPSLY may update the measures described in Annex A from time to time, provided that no update materially reduces the overall security of the Services.<\/p>

5.2 Customer Responsibilities and Optional Security Features.<\/span><\/b> MAPSLY disponibiliza diversos Controles de Servi\u00e7o que o Cliente pode optar por usar para fortalecer ainda mais a seguran\u00e7a dos Dados do Cliente. O Cliente \u00e9 respons\u00e1vel por (a) usar os Servi\u00e7os de forma segura, incluindo a prote\u00e7\u00e3o das credenciais de autentica\u00e7\u00e3o da sua conta, (b) proteger a seguran\u00e7a dos Dados do Cliente durante o tr\u00e2nsito de e para os Servi\u00e7os, (c) tomar as medidas adequadas para criptografar ou fazer backup seguro dos Dados do Cliente carregados nos Servi\u00e7os, (d) configurar corretamente os Servi\u00e7os e os Controles de Servi\u00e7o, e (e) tomar outras medidas que o Cliente considerar adequadas para garantir a seguran\u00e7a, prote\u00e7\u00e3o e exclus\u00e3o dos Dados do Cliente.<\/p>

5.3 Security Incident Notification.<\/span><\/b><\/p>

5.3.1 Security Incident.<\/span><\/b> MAPSLY ir\u00e1 (a) notificar o Cliente sobre um Incidente de Seguran\u00e7a sem demora indevida ap\u00f3s ter conhecimento do Incidente de Seguran\u00e7a, e (b) tomar as medidas apropriadas para tratar o Incidente de Seguran\u00e7a, incluindo medidas para amenizar quaisquer efeitos adversos decorrentes do Incidente de Seguran\u00e7a.<\/p>

5.3.2 MAPSLY Assistance.<\/span><\/b> Para permitir que o Cliente notifique um Incidente de Seguran\u00e7a \u00e0s autoridades supervisoras ou aos titulares dos dados (conforme aplic\u00e1vel), a MAPSLY cooperar\u00e1 e auxiliar\u00e1 o Cliente, incluindo na notifica\u00e7\u00e3o informa\u00e7\u00f5es sobre o Incidente de Seguran\u00e7a que a MAPSLY puder divulgar ao Cliente, levando em considera\u00e7\u00e3o a natureza do processamento, as informa\u00e7\u00f5es dispon\u00edveis para a MAPSLY e quaisquer restri\u00e7\u00f5es \u00e0 divulga\u00e7\u00e3o das informa\u00e7\u00f5es, como confidencialidade. Levando em considera\u00e7\u00e3o a natureza do processamento, o Cliente concorda que \u00e9 quem melhor pode determinar as consequ\u00eancias prov\u00e1veis de um Incidente de Seguran\u00e7a.<\/p>

5.3.3 Unsuccessful Security Incidents.<\/span><\/b> O cliente concorda que:<\/p>

(i) an unsuccessful Security Incident will not be subject to this Section 5.3. An unsuccessful Security Incident is one that results in no unauthorized access to Customer Data or to any of MAPSLY\u2019s equipment or facilities storing Customer Data, and could include, without limitation, pings and other broadcast attacks on firewalls or edge servers, port scans, unsuccessful log-on attempts, denial of service attacks, packet sniffing (or other unauthorized access to traffic data that does not result in access beyond headers) or similar incidents; and<\/p>

(ii) MAPSLY\u2019s obligation to report or respond to a Security Incident under this Section 5.3 is not and will not be construed as an acknowledgment by MAPSLY of any fault or liability of MAPSLY with respect to the Security Incident.<\/p>

5.3.4 Communication.<\/span><\/b> Notifica\u00e7\u00f5es de Incidentes de Seguran\u00e7a, se houver, ser\u00e3o enviadas a um ou mais administradores do Cliente por quaisquer meios selecionados pela MAPSLY, incluindo e-mail. \u00c9 \u00fanica e exclusiva responsabilidade do Cliente garantir que os administradores mantenham informa\u00e7\u00f5es de contato precisas no console de Configura\u00e7\u00e3o do MAPSLY e assegurem a transmiss\u00e3o segura em todos os momentos.<\/p>

5.3.5 Notification Obligations.<\/span><\/b> Se a MAPSLY notificar o Cliente sobre um Incidente de Seguran\u00e7a, ou se o Cliente tomar conhecimento de qualquer destrui\u00e7\u00e3o, perda, altera\u00e7\u00e3o, divulga\u00e7\u00e3o n\u00e3o autorizada ou acesso aos Dados do Cliente que seja acidental ou ilegal, o Cliente ser\u00e1 respons\u00e1vel por (a) determinar se h\u00e1 alguma obriga\u00e7\u00e3o de notifica\u00e7\u00e3o ou outra obriga\u00e7\u00e3o de acordo com a Lei Aplic\u00e1vel de Prote\u00e7\u00e3o de Dados e (b) tomar as medidas necess\u00e1rias para cumprir tais obriga\u00e7\u00f5es. Isso n\u00e3o limita as obriga\u00e7\u00f5es da MAPSLY nos termos desta Se\u00e7\u00e3o 5.3.<\/p>

6. Sub-processing<\/h2>

6.1 Authorized Sub-processors.<\/span><\/b> Customer provides general authorization to MAPSLY\u2019s use of sub-processors to provide processing activities on Customer Data on behalf of Customer (\u201cSub-processors\u201d) in accordance with this Section. The MAPSLY website (currently posted at https:\/\/mapsly.com\/sub-processors\/<\/a>) lists Sub-processors that are currently engaged by MAPSLY. At least 30 days before MAPSLY engages a Sub-processor, MAPSLY will update the applicable website and provide Customer with a mechanism to obtain notice of that update. To object to a Sub-processor, Customer can: (i) cease using the functionality of the MAPSLY Service for which MAPSLY has engaged the Sub-processor, or (ii) terminate the Agreement pursuant to its terms. If Customer objects to a new Sub-processor on reasonable grounds relating to data protection and the parties are unable to resolve the objection within thirty (30) days, Customer may terminate the Agreement with respect to the affected Services by written notice, and MAPSLY will refund Customer the prepaid fees prorated for the unused portion of the then-current Billing Period following the effective date of termination. If the affected functionality cannot reasonably be separated from the remainder of the Services, Customer may terminate the Agreement in its entirety on the same terms.<\/p>

6.2 Sub-processor Obligations.<\/span><\/b> Quando a MAPSLY autoriza um Subprocessador conforme descrito na Se\u00e7\u00e3o 6.1:<\/p>

(i) MAPSLY will restrict the Sub-processor\u2019s access to Customer Data only to what is necessary to provide or maintain the Services in accordance with the Documentation, and MAPSLY will prohibit the Sub-processor from accessing Customer Data for any other purpose;<\/p>

(ii) MAPSLY will enter into a written agreement with the Sub-processor and, to the extent that the Sub-processor performs the same data processing services provided by MAPSLY under this DPA, MAPSLY will impose on the Sub-processor the same contractual obligations that MAPSLY has under this DPA; and<\/p>

(iii) MAPSLY will remain responsible for its compliance with the obligations of this DPA and for any acts or omissions of the Sub-processor that cause MAPSLY to breach any of MAPSLY\u2019s obligations under this DPA.<\/p>

7. MAPSLY Assistance with Data Subject Requests<\/h2>

Tendo em conta a natureza do tratamento, os Controles de Servi\u00e7o s\u00e3o as medidas t\u00e9cnicas e organizacionais pelas quais a MAPSLY auxiliar\u00e1 o Cliente no cumprimento das suas obriga\u00e7\u00f5es de responder aos pedidos dos titulares dos dados ao abrigo da Lei de Prote\u00e7\u00e3o de Dados Aplic\u00e1vel. Se um titular dos dados fizer um pedido \u00e0 MAPSLY, a MAPSLY encaminhar\u00e1 prontamente tal pedido ao Cliente assim que identificar que o pedido \u00e9 de um titular dos dados pelo qual o Cliente \u00e9 respons\u00e1vel. O Cliente autoriza, em seu nome e em nome de seus controladores quando o Cliente atua como Processador, a MAPSLY a responder a qualquer titular dos dados que fizer um pedido \u00e0 MAPSLY, para confirmar que a MAPSLY encaminhou o pedido ao Cliente. As partes concordam que o uso dos Controles de Servi\u00e7o pelo Cliente e o encaminhamento pela MAPSLY dos pedidos dos titulares dos dados ao Cliente, de acordo com esta se\u00e7\u00e3o, representam o alcance e a extens\u00e3o da assist\u00eancia requerida do Cliente.<\/p>

8. Compliance Verification<\/h2>

8.1 MAPSLY Audits.<\/span><\/b> MAPSLY uses external auditors to verify the adequacy of its security measures. This audit: (a) will be performed at least annually; (b) will be performed according to a widely recognized standard (such as SOC 2 Type II); (c) will be performed by independent third-party security professionals at MAPSLY\u2019s selection and expense; and (d) will result in the generation of an audit report (\u201cReport\u201d), which will be MAPSLY\u2019s Confidential Information.<\/p>

8.2 Audit Reports.<\/span><\/b> A pedido escrito do Cliente, e desde que as partes tenham um NDA aplic\u00e1vel em vigor, a MAPSLY fornecer\u00e1 ao Cliente uma c\u00f3pia do Relat\u00f3rio para que o Cliente possa verificar razoavelmente o cumprimento da MAPSLY das suas obriga\u00e7\u00f5es nos termos deste DPA.<\/p>

8.3 Privacy Impact Assessment and Prior Consultation.<\/span><\/b> Tendo em conta a natureza do processamento e as informa\u00e7\u00f5es dispon\u00edveis para a MAPSLY, esta auxiliar\u00e1 o Cliente no cumprimento das suas obriga\u00e7\u00f5es relativas \u00e0s avalia\u00e7\u00f5es de impacto na prote\u00e7\u00e3o de dados e \u00e0 consulta pr\u00e9via, fornecendo as informa\u00e7\u00f5es que a MAPSLY disponibiliza ao abrigo desta Sec\u00e7\u00e3o 8.<\/p>

9. Transfers of Personal Data<\/h2>

9.1 Locations.<\/span><\/b> MAPSLY stores and processes Customer Data within the MAPSLY Network in the USA. MAPSLY personnel and Sub-processors may remotely access Customer Data from other countries in which they operate solely as necessary to provide, maintain, and support the Services; any such access constitutes a Data Transfer governed by this Section 9. MAPSLY will not otherwise transfer Customer Data outside of the EEA, the United Kingdom, Switzerland, and the USA except as necessary to provide the Services initiated by Customer, or as necessary to comply with the law or valid and binding order of a governmental body.<\/p>

9.2 Application of Standard Contractual Clauses.<\/span><\/b> Subject to Section 9.3, the Standard Contractual Clauses will only apply to Customer Data subject to the GDPR, the UK GDPR, or the FADP that is transferred, either directly or via onward transfer, to any Third Country (each a \u201cData Transfer\u201d).<\/p>

9.2.1<\/span><\/b> Quando o Cliente atua como Controlador, as Cl\u00e1usulas de Controlador para Processador se aplicar\u00e3o a uma Transfer\u00eancia de Dados.<\/p>

9.2.2<\/span><\/b> Quando o Cliente atua como Processador, as Cl\u00e1usulas de Processador para Processador aplicar-se-\u00e3o a uma Transfer\u00eancia de Dados. Tendo em conta a natureza do processamento, o Cliente concorda que \u00e9 pouco prov\u00e1vel que a MAPSLY conhe\u00e7a a identidade dos Controladores do Cliente porque a MAPSLY n\u00e3o tem rela\u00e7\u00e3o direta com os Controladores do Cliente e, portanto, o Cliente cumprir\u00e1 as obriga\u00e7\u00f5es da MAPSLY para com os Controladores do Cliente ao abrigo das Cl\u00e1usulas de Processador para Processador.<\/p>

9.2.3<\/span><\/b> For Data Transfers subject to the UK GDPR, the Standard Contractual Clauses apply as supplemented by the UK Addendum, completed as set forth in Section 9.4.<\/p>

9.2.4<\/span><\/b> For Data Transfers subject to the FADP, the Standard Contractual Clauses apply with the following adaptations: (i) references to the GDPR are to be read as references to the FADP; (ii) the competent supervisory authority is the Swiss Federal Data Protection and Information Commissioner; (iii) the term \u201cMember State\u201d is interpreted to include Switzerland, so that data subjects in Switzerland may enforce their rights in their place of habitual residence; and (iv) references to EU law are to be read as references to Swiss law where the transfer is exclusively subject to the FADP.<\/p>

9.3 Alternative Transfer Mechanism.<\/span><\/b> To the extent MAPSLY has adopted a valid alternative transfer mechanism recognized under Applicable Data Protection Law \u2014 including MAPSLY\u2019s certification under the EU-U.S. Data Privacy Framework, the UK Extension to the EU-U.S. Data Privacy Framework, and the Swiss-U.S. Data Privacy Framework \u2014 such mechanism will apply to a Data Transfer in place of the Standard Contractual Clauses for so long as it remains valid. If such alternative mechanism is invalidated, suspended, withdrawn, or otherwise ceases to provide a lawful basis for a Data Transfer, the Standard Contractual Clauses (as completed in Section 9.4) will automatically apply to that Data Transfer without further action by either party. MAPSLY will maintain its Data Privacy Framework certification for so long as it relies on the Data Privacy Framework for Data Transfers.<\/p>

9.4 Completion of the Standard Contractual Clauses.<\/span><\/b> For each Data Transfer to which the Standard Contractual Clauses apply, the Standard Contractual Clauses are deemed completed as follows: (i) Module Two (transfer controller to processor) applies where Customer acts as a Controller, and Module Three (transfer processor to processor) applies where Customer acts as a Processor; (ii) in Clause 7, the optional docking clause does not apply; (iii) in Clause 9, Option 2 (general written authorisation) applies, and the time period for prior notice of Sub-processor changes is thirty (30) days, in accordance with Section 6.1; (iv) in Clause 11, the optional language does not apply; (v) in Clauses 17 and 18, the governing law and the competent courts are those of Ireland; and (vi) Annex I of the Standard Contractual Clauses is deemed completed with the information set out in Annex B to this DPA, Annex II is deemed completed with Annex A to this DPA, and Annex III is deemed completed with the Sub-processor list referenced in Section 6.1. Where the UK Addendum applies: Table 1 is deemed completed with the parties\u2019 details under the Agreement; Table 2 with the Standard Contractual Clauses as completed above; Table 3 with the Annex information above; and, for Table 4, neither party may end the UK Addendum as set out in Section 19 of the UK Addendum.<\/p>

10. Termination of the DPA<\/h2>

This DPA will continue in force until the termination of the Agreement (the \u201cTermination Date\u201d).<\/p>

11. Deletion of Customer Data<\/h2>

Upon termination or expiration of the Agreement, MAPSLY shall delete Customer Data from its active systems at Customer\u2019s request, and in any event not later than within a 90-day period after termination, except and to the extent MAPSLY is required by applicable law to retain some or all of the Customer Data, in which case MAPSLY shall securely isolate this Data, protect it from any further processing, and delete it in accordance with applicable retention periods. Customer Data held in backup systems will be deleted or overwritten in the ordinary course of MAPSLY\u2019s backup rotation cycles following deletion from active systems and will be protected from any further processing until deleted.<\/p>

12. Duties to Inform<\/h2>

Quando os Dados do Cliente forem sujeitos a confisco durante processos de fal\u00eancia, insolv\u00eancia ou medidas similares por terceiros enquanto estiverem sendo processados pela MAPSLY, a MAPSLY informar\u00e1 o Cliente sem demora indevida. A MAPSLY notificar\u00e1, sem demora indevida, todas as partes relevantes nessa a\u00e7\u00e3o (por exemplo, credores, administrador da fal\u00eancia) de que quaisquer Dados do Cliente sujeitos a esses processos s\u00e3o propriedade e responsabilidade do Cliente e que os Dados do Cliente est\u00e3o \u00e0 disposi\u00e7\u00e3o exclusiva do Cliente.<\/p>

13. Entire Agreement; Conflict; Amendment<\/h2>

This DPA incorporates the Standard Contractual Clauses by reference. Except as amended by this DPA, the Agreement will remain in full force and effect. If there is a conflict among the Standard Contractual Clauses, this DPA, and the Agreement concerning the processing of Customer Data, the Standard Contractual Clauses will control first, this DPA will control second, and the Agreement will control third. For all other matters, the Agreement controls. Nothing in this document varies or modifies the Standard Contractual Clauses. This DPA may be amended in accordance with Section 14.1 of the Agreement, provided that MAPSLY will provide Customer with advance notice of any amendment that materially reduces the protections afforded to Customer Data under this DPA.<\/p>

14. Google Workspace API Data<\/h2>

The use of raw or derived user data received from Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.<\/p>

Annex A \u2014 Technical and Organizational Measures<\/h2>

MAPSLY maintains the following technical and organizational measures to protect Customer Data. MAPSLY may update these measures from time to time, provided that no update materially reduces the overall security of the Services.<\/p>