{"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-24T18:45:22","modified_gmt":"2026-08-24T15:45:22","slug":"dpa","status":"publish","type":"page","link":"https:\/\/mapsly.com\/it\/dpa\/","title":{"rendered":"Mapsly Data Processing Addendum"},"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

Addendum al trattamento dei dati<\/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>

Il presente Addendum al Trattamento dei Dati (\u201cDPA\u201d) \u00e8 un accordo tra te e l'entit\u00e0 che rappresenti (\u201cCliente\u201d, \u201ctu\u201d o \u201ctuo\u201d) e Mapsly LLC (\u201cMAPSLY\u201d). Questo DPA integra i Termini di Servizio MAPSLY disponibili su 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>

Definitions.<\/strong> All capitalized terms used in this DPA will have the meanings given to them below, unless otherwise defined in the Agreement:<\/p>

\u201cAPI\u201d<\/span><\/b> significa un'interfaccia di programmazione delle applicazioni.<\/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> ha il significato a lui attribuito nel GDPR.<\/p>

\u201cController\u201d<\/span><\/b> ha il significato a lui attribuito nel GDPR.<\/p>

\u201cController-to-Processor Clauses\u201d<\/span><\/b> indica le clausole contrattuali standard tra Titolari e Responsabili del trattamento per i trasferimenti di dati, come approvato dalla Decisione di esecuzione della Commissione Europea (UE) 2021\/914 del 4 giugno 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 la documentazione vigente per i Servizi situata in https:\/\/help.mapsly.com<\/a> (e qualsiasi ubicazione successiva designata da MAPSLY).<\/p>

\u201cEEA\u201d<\/span><\/b> significa lo Spazio Economico Europeo.<\/p>

\u201cEnd Users\u201d<\/span><\/b> indica gli utenti dell'account Mapsly del Cliente, inclusi i dipendenti e i collaboratori assegnati dal Cliente per utilizzare Mapsly.<\/p>

\u201cGDPR\u201d<\/span><\/b> indica il Regolamento 2016\/679 del Parlamento Europeo e del Consiglio del 27 aprile 2016 relativo alla protezione delle persone fisiche con riguardo al trattamento dei dati personali e alla libera circolazione di tali dati, e che abroga la Direttiva 95\/46\/CE (Regolamento generale sulla protezione dei dati).<\/p>

\u201cMAPSLY Network\u201d<\/span><\/b> indica i server, le apparecchiature di rete e i sistemi software host (ad esempio, firewall virtuali) che sono sotto il controllo di MAPSLY e vengono utilizzati per fornire i Servizi.<\/p>

\u201cMAPSLY Setup console\u201d<\/span><\/b> significa la sezione Configurazione nel servizio Mapsly disponibile sotto \u201cConfigurazione\u201d nel menu principale.<\/p>

\u201cPersonal Data\u201d<\/span><\/b> significa dati personali, informazioni personali, informazioni identificabili personalmente o altro termine equivalente (ciascuno come definito nella Legge Applicabile sulla Protezione dei Dati).<\/p>

\u201cProcessing\u201d<\/span><\/b> ha il significato attribuito dal GDPR e \u201cprocessare\u201d, \u201cprocessi\u201d e \u201cprocessato\u201d saranno interpretati di conseguenza.<\/p>

\u201cProcessor\u201d<\/span><\/b> ha il significato a lui attribuito nel GDPR.<\/p>

Clausole da processore a processore<\/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 di sicurezza<\/span><\/b> significa una violazione della sicurezza di MAPSLY che comporta la distruzione, perdita, alterazione accidentale o illecita, la divulgazione non autorizzata o l'accesso ai Dati del Cliente.<\/p>

Controlli del servizio<\/span><\/b> indica i controlli, comprese le funzionalit\u00e0 e le caratteristiche di sicurezza, che i Servizi forniscono, come descritto nella Documentazione.<\/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>

Paese terzo<\/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<\/strong><\/h2>

1.1 Scope and Roles.<\/span><\/b> Questo DPA si applica quando MAPSLY elabora i Dati del Cliente. In questo contesto, MAPSLY agir\u00e0 come Processore per il Cliente, che pu\u00f2 agire come Titolare o Processore dei Dati del Cliente.<\/p>

1.2 Customer Controls.<\/span><\/b> Il Cliente pu\u00f2 utilizzare i Controlli del Servizio per assisterlo nelle proprie obbligazioni ai sensi della Legge sulla Protezione dei Dati Applicabile, inclusi gli obblighi di rispondere alle richieste degli interessati. Tenendo conto della natura del trattamento, il Cliente concorda sul fatto che \u00e8 improbabile che MAPSLY venga a conoscenza che i Dati del Cliente trasferiti ai sensi delle Clausole Contrattuali Standard siano inaccurati o obsoleti. Tuttavia, se MAPSLY viene a conoscenza che i Dati del Cliente trasferiti ai sensi delle Clausole Contrattuali Standard sono inaccurati o obsoleti, informer\u00e0 il Cliente senza indugio indebido. MAPSLY collaborer\u00e0 con il Cliente per cancellare o rettificare i Dati del Cliente inaccurati o obsoleti trasferiti ai sensi delle Clausole Contrattuali Standard fornendo i Controlli del Servizio che il Cliente pu\u00f2 utilizzare per cancellare o rettificare i Dati del Cliente.<\/p>

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

1.3.1 Subject matter.<\/span><\/b> L'oggetto del trattamento dei dati ai sensi di questo DPA \u00e8 rappresentato dai Dati del 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> Lo scopo del trattamento dei dati previsto dal presente DPA \u00e8 la fornitura dei Servizi avviati dal Cliente di volta in volta.<\/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> Ciascuna parte si conformer\u00e0 a tutte le leggi, norme e regolamenti applicabili e vincolanti per essa nell\u2019esecuzione del presente DPA, inclusa la normativa applicabile in materia di protezione dei dati.<\/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<\/strong><\/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<\/strong><\/h2>

MAPSLY non acceder\u00e0, user\u00e0 o divulgher\u00e0 a terzi alcun Dato del Cliente, eccetto, in ogni caso, ove necessario per mantenere o fornire i Servizi, o ove necessario per conformarsi alla legge o a un ordine valido e vincolante di un ente governativo (come un mandato o un ordine del tribunale). Se un ente governativo invia a MAPSLY una richiesta di Dati del Cliente, MAPSLY cercher\u00e0 di indirizzare l'ente governativo a richiedere direttamente tali dati al Cliente. Nell'ambito di questo sforzo, MAPSLY pu\u00f2 fornire all'ente governativo le informazioni di contatto di base del Cliente. Se costretta a divulgare i Dati del Cliente a un ente governativo, MAPSLY fornir\u00e0 al Cliente un preavviso ragionevole della richiesta per consentire al Cliente di cercare un ordine di protezione o altro rimedio appropriato, salvo che MAPSLY sia legalmente vietata dal farlo.<\/p>

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

MAPSLY limita il proprio personale dal trattare i Dati dei Clienti senza autorizzazione da parte di MAPSLY. MAPSLY impone al proprio personale adeguati obblighi contrattuali, inclusi gli obblighi pertinenti relativi alla riservatezza, alla protezione dei dati e alla sicurezza dei dati.<\/p>

5. Security of Data Processing<\/strong><\/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 mette a disposizione molti Controlli del Servizio che il Cliente pu\u00f2 scegliere di utilizzare per rafforzare ulteriormente la sicurezza dei Dati del Cliente. Il Cliente \u00e8 responsabile di (a) un uso sicuro dei Servizi, inclusa la protezione delle credenziali di autenticazione del proprio account, (b) proteggere la sicurezza dei Dati del Cliente durante il trasferimento da e verso i Servizi, (c) adottare adeguate misure per crittografare o eseguire il backup in modo sicuro dei Dati del Cliente caricati sui Servizi, (d) configurare correttamente i Servizi e i Controlli del Servizio, e (e) adottare altri provvedimenti che il Cliente ritenga adeguati per garantire la sicurezza, la protezione e la cancellazione dei Dati del Cliente.<\/p>

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

5.3.1 Security Incident.<\/span><\/b> MAPSLY notificher\u00e0 (a) il Cliente di un Incidente di Sicurezza senza ingiustificato ritardo dopo averne avuto conoscenza, e (b) adotter\u00e0 le misure appropriate per affrontare l'Incidente di Sicurezza, comprese le misure per mitigare eventuali effetti negativi derivanti dall'Incidente di Sicurezza.<\/p>

5.3.2 MAPSLY Assistance.<\/span><\/b> Per consentire al Cliente di notificare un Incidente di Sicurezza alle autorit\u00e0 di vigilanza o ai soggetti interessati (se applicabile), MAPSLY collaborer\u00e0 e assister\u00e0 il Cliente includendo nella notifica le informazioni sull'Incidente di Sicurezza che MAPSLY \u00e8 in grado di divulgare al Cliente, tenendo conto della natura del trattamento, delle informazioni disponibili a MAPSLY e di eventuali restrizioni sulla divulgazione delle informazioni, quali la riservatezza. Tenendo conto della natura del trattamento, il Cliente concorda che \u00e8 il pi\u00f9 adatto a determinare le probabili conseguenze di un Incidente di Sicurezza.<\/p>

5.3.3 Unsuccessful Security Incidents.<\/span><\/b> Il cliente accetta che:<\/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> La\/notifica delle eventuali violazioni di sicurezza sar\u00e0 inviata a uno o pi\u00f9 amministratori del Cliente tramite qualsiasi mezzo scelto da MAPSLY, inclusa la posta elettronica. \u00c8 esclusiva responsabilit\u00e0 del Cliente assicurarsi che gli amministratori mantengano informazioni di contatto accurate nella console di configurazione MAPSLY e garantiscano una trasmissione sicura in ogni momento.<\/p>

5.3.5 Notification Obligations.<\/span><\/b> Se MAPSLY notifica il Cliente di un Incidente di Sicurezza, oppure se il Cliente viene a conoscenza di qualsiasi distruzione accidentale o illecita, perdita, alterazione, divulgazione non autorizzata o accesso ai Dati del Cliente, il Cliente sar\u00e0 responsabile di (a) determinare se esiste un obbligo di notifica o altro ai sensi della Legge sulla Protezione dei Dati Applicabile e (b) adottare le misure necessarie per adempiere a tali obblighi. Ci\u00f2 non limita gli obblighi di MAPSLY ai sensi della presente Sezione 5.3.<\/p>

6. Sub-processing<\/strong><\/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 MAPSLY autorizza un Sub-responsabile come descritto nella Sezione 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<\/strong><\/h2>

Tenendo conto della natura del trattamento, i Controlli del Servizio sono le misure tecniche e organizzative con cui MAPSLY assister\u00e0 il Cliente nell'adempiere agli obblighi di rispondere alle richieste degli interessati ai sensi della Legge sulla Protezione dei Dati applicabile. Se un interessato presenta una richiesta a MAPSLY, MAPSLY inoltrer\u00e0 tempestivamente tale richiesta al Cliente non appena avr\u00e0 identificato che la richiesta proviene da un interessato di cui il Cliente \u00e8 responsabile. Il Cliente autorizza a proprio nome, e a nome dei suoi responsabili quando agisce come Responsabile del trattamento, MAPSLY a rispondere a qualsiasi interessato che faccia una richiesta a MAPSLY, per confermare che MAPSLY ha inoltrato la richiesta al Cliente. Le parti convengono che l'uso da parte del Cliente dei Controlli del Servizio e l'inoltro da parte di MAPSLY delle richieste degli interessati al Cliente ai sensi di questa sezione rappresentano l'ambito e la portata dell'assistenza richiesta al Cliente.<\/p>

8. Compliance Verification<\/strong><\/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> Su richiesta scritta del Cliente, e a condizione che le parti abbiano un NDA applicabile in vigore, MAPSLY fornir\u00e0 al Cliente una copia del Rapporto in modo che il Cliente possa verificare ragionevolmente la conformit\u00e0 di MAPSLY ai suoi obblighi ai sensi del presente DPA.<\/p>

8.3 Privacy Impact Assessment and Prior Consultation.<\/span><\/b> Tenendo conto della natura del trattamento e delle informazioni disponibili a MAPSLY, MAPSLY assister\u00e0 il Cliente nell'adempimento degli obblighi relativi alle valutazioni d'impatto sulla protezione dei dati e alla consultazione preventiva fornendo le informazioni che MAPSLY rende disponibili ai sensi della presente Sezione 8.<\/p>

9. Transfers of Personal Data<\/strong><\/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 il Cliente agisce come Titolare del trattamento, le Clausole da Titolare a Responsabile si applicheranno a un Trasferimento di Dati.<\/p>

9.2.2<\/span><\/b> Quando il Cliente agisce come Responsabile del trattamento, le Clausole da Responsabile a Responsabile si applicheranno a un Trasferimento di Dati. Tenendo conto della natura del trattamento, il Cliente concorda che \u00e8 improbabile che MAPSLY conosca l'identit\u00e0 dei Titolari del Cliente perch\u00e9 MAPSLY non ha un rapporto diretto con i Titolari del Cliente e, pertanto, il Cliente assolver\u00e0 gli obblighi di MAPSLY nei confronti dei Titolari del Cliente ai sensi delle Clausole da Responsabile a Responsabile.<\/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<\/strong><\/h2>

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

11. Deletion of Customer Data<\/strong><\/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<\/strong><\/h2>

Qualora i Dati del Cliente diventino soggetti a sequestro durante procedure di fallimento o insolvenza o misure simili da parte di terzi mentre sono trattati da MAPSLY, MAPSLY informer\u00e0 il Cliente senza indugio ingiustificato. MAPSLY notificher\u00e0, senza indugio ingiustificato, tutte le parti rilevanti coinvolte in tale azione (ad esempio, creditori, curatore fallimentare) che qualsiasi Dato del Cliente soggetto a tali procedure \u00e8 di propriet\u00e0 del Cliente ed \u00e8 di sua responsabilit\u00e0, e che i Dati del Cliente sono a disposizione esclusiva del Cliente.<\/p>

13. Entire Agreement; Conflict; Amendment<\/strong><\/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<\/strong><\/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<\/strong><\/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>