Last updated: July 31, 2026. This version supersedes the version last updated September 15, 2023.

Este Anexo de Procesamiento de Datos (“DPA”) es un acuerdo entre usted y la entidad que representa (“Cliente”, “usted” o “su”) y Mapsly LLC (“MAPSLY”). Este DPA complementa los Términos de Servicio de MAPSLY disponibles en https://mapsly.com/terms, as updated from time to time between Customer and MAPSLY, or other agreements between Customer and MAPSLY that govern Customer’s use of the MAPSLY Services (the “Agreement”). “Customer” refers to the entity defined as “User” under the MAPSLY Terms of Service. This DPA applies to the extent MAPSLY processes Customer Data on Customer’s behalf in providing the Services.

Definiciones. Todos los términos en mayúsculas utilizados en este DPA tendrán los significados que se les asignan a continuación, salvo que se definan de otra manera en el Acuerdo:

“API” significa una interfaz de programación de aplicaciones.

“Applicable Data Protection Law” 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 (“FADP”), and applicable United States federal and state privacy laws (including the California Consumer Privacy Act, as amended).

“Binding Corporate Rules” tiene el significado que se le da en el GDPR.

“Controller” tiene el significado que se le da en el GDPR.

“Controller-to-Processor Clauses” significa las cláusulas contractuales estándar entre los Controladores y Procesadores para Transferencias de Datos, según lo aprobado por la Decisión de Implementación de la Comisión Europea (UE) 2021/914 del 4 de junio de 2021.

“Customer Data” means the Personal Data that is uploaded to or generated within the Services under Customer’s MAPSLY accounts, excluding the End-User account and usage information described in Section 1.5.

“Data Privacy Framework” or “DPF” 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.

“Documentation” significa la documentación vigente en ese momento para los Servicios ubicados en https://help.mapsly.com (y cualquier ubicación sucesora designada por MAPSLY).

“EEA” significa el Espacio Económico Europeo.

“End Users” se refiere a los usuarios de la cuenta Mapsly del Cliente, incluidos los empleados y contratistas del Cliente que fueron asignados por el Cliente para usar Mapsly.

“GDPR” significa el Reglamento 2016/679 del Parlamento Europeo y del Consejo de 27 de abril de 2016 sobre la protección de las personas físicas en lo que respecta al tratamiento de datos personales y a la libre circulación de estos datos, y que deroga la Directiva 95/46/CE (Reglamento General de Protección de Datos).

“MAPSLY Network” significa los servidores, los equipos de red y los sistemas de software host (por ejemplo, cortafuegos virtuales) que están bajo el control de MAPSLY y se usan para proporcionar los Servicios.

“MAPSLY Setup console” significa la sección Configuración en el servicio Mapsly disponible en “Configuración” en el menú principal.

“Personal Data” significa datos personales, información personal, información de identificación personal u otro término equivalente (cada uno según lo definido en la Ley de Protección de Datos Aplicable).

“Processing” tiene el significado que se le da en el RGPD y “procesar”, “procesos” y “procesado” se interpretarán en consecuencia.

“Processor” tiene el significado que se le da en el GDPR.

Cláusulas de Procesador a Procesador 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.

Incidente de seguridad significa una violación de la seguridad de MAPSLY que conduce a la destrucción, pérdida, alteración accidental o ilegal, divulgación no autorizada o acceso a los Datos del Cliente.

Controles de Servicio se refiere a los controles, incluidas las funciones y características de seguridad, que los Servicios proporcionan, tal como se describe en la Documentación.

“Standard Contractual Clauses” 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).

Tercer país 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).

“UK Addendum” means the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses issued by the UK Information Commissioner, in force 21 March 2022.

“UK GDPR” 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.

1. Data Processing

1.1 Scope and Roles. Este DPA se aplica cuando MAPSLY procesa los Datos del Cliente. En este contexto, MAPSLY actuará como Procesador para el Cliente, quien puede actuar como Controlador o Procesador de los Datos del Cliente.

1.2 Customer Controls. El Cliente puede usar los Controles de Servicio para ayudarle con sus obligaciones bajo la Ley de Protección de Datos Aplicable, incluyendo sus obligaciones de responder solicitudes de los titulares de datos. Teniendo en cuenta la naturaleza del procesamiento, el Cliente acuerda que es poco probable que MAPSLY se dé cuenta de que los Datos del Cliente transferidos bajo las Cláusulas Contractuales Estándar sean inexactos o estén desactualizados. No obstante, si MAPSLY se da cuenta de que los Datos del Cliente transferidos bajo las Cláusulas Contractuales Estándar son inexactos o están desactualizados, informará al Cliente sin demora indebida. MAPSLY cooperará con el Cliente para borrar o rectificar Datos del Cliente inexactos o desactualizados transferidos bajo las Cláusulas Contractuales Estándar proporcionando los Controles de Servicio que el Cliente puede usar para borrar o rectificar los Datos del Cliente.

1.3 Details of Data Processing.

1.3.1 Subject matter. El objeto del procesamiento de datos bajo este DPA son los Datos del Cliente.

1.3.2 Duration. 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.

1.3.3 Purpose. El propósito del procesamiento de datos bajo este DPA es la provisión de los Servicios iniciados por el Cliente de vez en cuando.

1.3.4 Nature of the processing. Compute, storage, geocoding, routing, synchronization with Customer’s 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.

1.3.5 Type of Customer Data. Customer Data uploaded to or generated within the Services under Customer’s 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.

1.3.6 Categories of data subjects. The data subjects could include Customer’s customers, prospects and leads, employees, suppliers and End Users.

1.4 Compliance with Laws. Cada parte cumplirá con todas las leyes, normas y regulaciones que le sean aplicables y vinculantes en el cumplimiento de este DPA, incluyendo la Ley de Protección de Datos Aplicable.

1.5 Mapsly as Controller. Customer acknowledges that Mapsly collects certain information about Customer’s End Users — such as account, authentication, billing, support, and usage information — as described in the MAPSLY Privacy Policy (currently published at https://mapsly.com/privacy-policy). 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.

2. Customer Instructions

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’s documented instructions regarding MAPSLY’s processing of Customer Data (“Documented Instructions”). 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’s 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.

3. Confidentiality of Customer Data

MAPSLY no accederá, usará ni divulgará a ningún tercero ningún Dato del Cliente, excepto, en cada caso, según sea necesario para mantener o proporcionar los Servicios, o según sea necesario para cumplir con la ley o una orden válida y vinculante de un organismo gubernamental (como una citación o una orden judicial). Si un organismo gubernamental envía a MAPSLY una solicitud de Datos del Cliente, MAPSLY intentará redirigir al organismo gubernamental para que solicite esos datos directamente al Cliente. Como parte de este esfuerzo, MAPSLY podrá proporcionar al organismo gubernamental la información de contacto básica del Cliente. Si se ve obligado a divulgar Datos del Cliente a un organismo gubernamental, MAPSLY dará al Cliente un aviso razonable de la solicitud para permitir que el Cliente busque una orden de protección u otro remedio apropiado, a menos que MAPSLY tenga prohibido legalmente hacerlo.

4. Confidentiality Obligations of MAPSLY Personnel

MAPSLY restringe a su personal de procesar Datos de Clientes sin autorización por parte de MAPSLY. MAPSLY impone obligaciones contractuales apropiadas a su personal, incluidas las obligaciones relevantes relativas a la confidencialidad, la protección de datos y la seguridad de los datos.

5. Security of Data Processing

5.1 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’s 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.

5.2 Customer Responsibilities and Optional Security Features. MAPSLY pone a disposición muchos Controles de Servicio que el Cliente puede elegir usar para fortalecer aún más la seguridad de los Datos del Cliente. El Cliente es responsable de (a) usar los Servicios de manera segura, incluyendo asegurar las credenciales de autenticación de su cuenta, (b) proteger la seguridad de los Datos del Cliente mientras están en tránsito hacia y desde los Servicios, (c) tomar las medidas adecuadas para cifrar o respaldar de manera segura los Datos del Cliente cargados en los Servicios, (d) configurar correctamente los Servicios y los Controles de Servicio, y (e) tomar otras medidas que el Cliente considere adecuadas para asegurar la seguridad, protección y eliminación de los Datos del Cliente.

5.3 Security Incident Notification.

5.3.1 Security Incident. MAPSLY (a) notificará al Cliente sobre un Incidente de Seguridad sin demora indebida después de tener conocimiento del Incidente de Seguridad, y (b) tomará las medidas adecuadas para abordar el Incidente de Seguridad, incluyendo medidas para mitigar cualquier efecto adverso resultante del Incidente de Seguridad.

5.3.2 MAPSLY Assistance. Para permitir que el Cliente notifique un Incidente de Seguridad a las autoridades supervisoras o a los sujetos de datos (según corresponda), MAPSLY cooperará con el Cliente y le asistirá incluyendo en la notificación la información sobre el Incidente de Seguridad que MAPSLY pueda revelar al Cliente, teniendo en cuenta la naturaleza del procesamiento, la información disponible para MAPSLY y cualquier restricción para divulgar la información, como la confidencialidad. Teniendo en cuenta la naturaleza del procesamiento, el Cliente acepta que es el más capacitado para determinar las posibles consecuencias de un Incidente de Seguridad.

5.3.3 Unsuccessful Security Incidents. El cliente acepta que:

(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’s 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

(ii) MAPSLY’s 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.

5.3.4 Communication. La(s) notificación(es) de incidentes de seguridad, si las hubiera, se entregarán a uno o más administradores del Cliente por cualquier medio que MAPSLY seleccione, incluido el correo electrónico. Es exclusiva responsabilidad del Cliente asegurarse de que los administradores mantengan información de contacto precisa en la consola de configuración de MAPSLY y una transmisión segura en todo momento.

5.3.5 Notification Obligations. Si MAPSLY notifica al Cliente sobre un Incidente de Seguridad, o si el Cliente se entera de cualquier destrucción accidental o ilegal, pérdida, alteración, divulgación no autorizada o acceso a los Datos del Cliente, el Cliente será responsable de (a) determinar si existe alguna obligación de notificación u otra obligación conforme a la Ley de Protección de Datos Aplicable y (b) tomar las medidas necesarias para cumplir con dichas obligaciones. Esto no limita las obligaciones de MAPSLY según esta Sección 5.3.

6. Sub-processing

6.1 Authorized Sub-processors. Customer provides general authorization to MAPSLY’s use of sub-processors to provide processing activities on Customer Data on behalf of Customer (“Sub-processors”) in accordance with this Section. The MAPSLY website (currently posted at https://mapsly.com/sub-processors/) 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.

6.2 Sub-processor Obligations. Cuando MAPSLY autoriza a un Subprocesador como se describe en la Sección 6.1:

(i) MAPSLY will restrict the Sub-processor’s 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;

(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

(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’s obligations under this DPA.

7. MAPSLY Assistance with Data Subject Requests

Teniendo en cuenta la naturaleza del procesamiento, los Controles del Servicio son las medidas técnicas y organizativas mediante las cuales MAPSLY asistirá al Cliente para cumplir con sus obligaciones de responder a las solicitudes de los sujetos de datos conforme a la Ley de Protección de Datos Aplicable. Si un sujeto de datos realiza una solicitud a MAPSLY, MAPSLY reenviará dicha solicitud al Cliente una vez que MAPSLY haya identificado que la solicitud proviene de un sujeto de datos por el cual el Cliente es responsable. El Cliente autoriza en su nombre, y en nombre de sus controladores cuando actúa como Procesador, a MAPSLY para responder a cualquier sujeto de datos que realice una solicitud a MAPSLY, para confirmar que MAPSLY ha reenviado la solicitud al Cliente. Las partes acuerdan que el uso por parte del Cliente de los Controles del Servicio y el reenvío por parte de MAPSLY de las solicitudes de los sujetos de datos al Cliente de conformidad con esta sección representan el alcance y la extensión de la asistencia requerida por el Cliente.

8. Compliance Verification

8.1 MAPSLY Audits. 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’s selection and expense; and (d) will result in the generation of an audit report (“Report”), which will be MAPSLY’s Confidential Information.

8.2 Audit Reports. A solicitud escrita del Cliente, y siempre que las partes tengan un NDA aplicable en vigor, MAPSLY proporcionará al Cliente una copia del Informe para que el Cliente pueda verificar razonablemente el cumplimiento de MAPSLY con sus obligaciones bajo este DPA.

8.3 Privacy Impact Assessment and Prior Consultation. Teniendo en cuenta la naturaleza del tratamiento y la información disponible para MAPSLY, MAPSLY ayudará al Cliente a cumplir con sus obligaciones en relación con las evaluaciones de impacto en la protección de datos y la consulta previa proporcionando la información que MAPSLY pone a disposición en virtud de esta Sección 8.

9. Transfers of Personal Data

9.1 Locations. 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.

9.2 Application of Standard Contractual Clauses. 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 “Data Transfer”).

9.2.1 Cuando el Cliente actúa como Controlador, las Cláusulas de Controlador a Procesador se aplicarán a una Transferencia de Datos.

9.2.2 Cuando el Cliente actúa como Procesador, las Cláusulas de Procesador a Procesador se aplicarán a una Transferencia de Datos. Teniendo en cuenta la naturaleza del procesamiento, el Cliente acepta que es poco probable que MAPSLY conozca la identidad de los Controladores del Cliente porque MAPSLY no tiene una relación directa con los Controladores del Cliente y, por lo tanto, el Cliente cumplirá con las obligaciones de MAPSLY hacia los Controladores del Cliente en virtud de las Cláusulas de Procesador a Procesador.

9.2.3 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.

9.2.4 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 “Member State” 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.

9.3 Alternative Transfer Mechanism. To the extent MAPSLY has adopted a valid alternative transfer mechanism recognized under Applicable Data Protection Law — including MAPSLY’s 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 — 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.

9.4 Completion of the Standard Contractual Clauses. 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’ 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.

10. Termination of the DPA

This DPA will continue in force until the termination of the Agreement (the “Termination Date”).

11. Deletion of Customer Data

Upon termination or expiration of the Agreement, MAPSLY shall delete Customer Data from its active systems at Customer’s 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’s backup rotation cycles following deletion from active systems and will be protected from any further processing until deleted.

12. Duties to Inform

Cuando los Datos del Cliente estén sujetos a confiscación durante procedimientos de quiebra, insolvencia o medidas similares por terceros mientras se procesan por MAPSLY, MAPSLY informará al Cliente sin demora indebida. MAPSLY notificará, sin demora indebida, a todas las partes relevantes en dicha acción (por ejemplo, acreedores, síndico de quiebra) que cualquier Dato del Cliente sujeto a dichos procedimientos es propiedad y responsabilidad del Cliente y que los Datos del Cliente están bajo la disposición exclusiva del Cliente.

13. Entire Agreement; Conflict; Amendment

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.

14. Google Workspace API Data

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.

Annex A — Technical and Organizational Measures

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.

• Hosting and resilience: the Services are hosted on Amazon Web Services in the United States across multiple availability zones; backups are taken daily and stored in a separate availability zone; backup restoration is tested at least annually.
• Encryption: Customer Data is encrypted at rest and in transit using industry-standard encryption protocols.
• Access control: access to production systems is role-based, restricted to authorized personnel on a least-privilege basis, revoked promptly upon role change or termination, and reviewed periodically.
• Authentication: single sign-on and multi-factor authentication are supported.
• Secure development: documented secure development practices, including code review and segregation of development, testing, and production environments.
• Vulnerability management: periodic vulnerability scanning and at least annual penetration testing by independent third parties, with remediation according to documented severity-based timelines.
• Logging and monitoring: security-relevant events are logged, retained, and monitored.
• Personnel: personnel are bound by confidentiality obligations and receive security awareness training.
• Incident response: a documented incident response plan is maintained; Security Incidents are handled in accordance with Section 5.3.
• Business continuity: documented business continuity and disaster recovery plans are maintained.
• Governance: a documented information security policy suite is maintained and reviewed periodically; personnel accept applicable policies.
• Independent assurance: security controls are audited at least annually by independent third parties against a widely recognized standard (currently SOC 2 Type II).

Annex B — Standard Contractual Clauses Information

For the purposes of Annex I of the Standard Contractual Clauses, the following information applies to each Data Transfer:

• Data exporter: Customer (name, address, and contact details as provided in Customer’s MAPSLY account and the Agreement), acting as a Controller or as a Processor on behalf of its Controllers, as described in Section 9.2. Contact: Customer’s administrator contact on record.
• Data importer: Mapsly LLC, 440 N Barranca Ave #4985, Covina, CA 91723, USA; [email protected]; acting as a Processor.
• Signature and date: each party is deemed to have signed the Standard Contractual Clauses, including their Annexes, upon acceptance or execution of the Agreement, with effect from the effective date of the Agreement.
• Categories of data subjects: as described in Section 1.3.6.
• Categories of personal data: as described in Section 1.3.5.
• Sensitive data: the Services are not specifically designed to require special categories of personal data. To the extent Customer chooses to submit such data, Customer is responsible for its compliance with Applicable Data Protection Law in doing so, and the data is processed only in accordance with Customer’s Documented Instructions and protected by the measures described in Annex A.
• Frequency of the transfer: continuous, for the duration described in Section 1.3.2.
• Nature and purpose of the processing: as described in Sections 1.3.3 and 1.3.4. Transfers to Sub-processors: as described in Section 6, for the same duration.
• Retention period: as described in Section 11.
• Competent supervisory authority (Clause 13): where the data exporter is established in an EEA Member State, the supervisory authority of that Member State; where the data exporter is not established in the EEA but falls within the territorial scope of the GDPR and has appointed an EU representative, the supervisory authority of the Member State in which the representative is established; where the data exporter falls within the territorial scope of the GDPR under Article 3(2) but has not appointed an EU representative, the supervisory authority of one of the Member States in which the data subjects whose personal data is transferred are located. For Data Transfers subject to the UK GDPR, the UK Information Commissioner’s Office; for Data Transfers subject to the FADP, the Swiss Federal Data Protection and Information Commissioner.