{"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-10T12:11:08","modified_gmt":"2026-08-10T09:11:08","slug":"dpa","status":"publish","type":"page","link":"https:\/\/mapsly.com\/vi\/dpa\/","title":{"rendered":"PH\u1ee4 L\u1ee4C X\u1eec L\u00dd D\u1eee LI\u1ec6U 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

Ph\u1ee5 l\u1ee5c x\u1eed l\u00fd d\u1eef li\u1ec7u<\/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>\n\n

Ph\u1ee5 l\u1ee5c X\u1eed l\u00fd D\u1eef li\u1ec7u n\u00e0y (\u201cDPA\u201d) l\u00e0 m\u1ed9t th\u1ecfa thu\u1eadn gi\u1eefa b\u1ea1n v\u00e0 t\u1ed5 ch\u1ee9c b\u1ea1n \u0111\u1ea1i di\u1ec7n (\u201cKh\u00e1ch h\u00e0ng\u201d, \u201cb\u1ea1n\u201d ho\u1eb7c \u201cc\u1ee7a b\u1ea1n\u201d) v\u00e0 Mapsly LLC (\u201cMAPSLY\u201d). DPA n\u00e0y b\u1ed5 sung cho \u0110i\u1ec1u kho\u1ea3n D\u1ecbch v\u1ee5 c\u1ee7a MAPSLY c\u00f3 t\u1ea1i 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>\n\n

\u0110\u1ecbnh ngh\u0129a. T\u1ea5t c\u1ea3 c\u00e1c thu\u1eadt ng\u1eef vi\u1ebft hoa \u0111\u01b0\u1ee3c s\u1eed d\u1ee5ng trong DPA n\u00e0y s\u1ebd c\u00f3 \u00fd ngh\u0129a \u0111\u01b0\u1ee3c quy \u0111\u1ecbnh d\u01b0\u1edbi \u0111\u00e2y, tr\u1eeb khi \u0111\u01b0\u1ee3c \u0111\u1ecbnh ngh\u0129a kh\u00e1c trong Th\u1ecfa thu\u1eadn:<\/p>\n\n

\u201cAPI\u201d<\/span><\/b> c\u00f3 ngh\u0129a l\u00e0 giao di\u1ec7n l\u1eadp tr\u00ecnh \u1ee9ng d\u1ee5ng.<\/p>\n\n

\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>\n\n

\u201cBinding Corporate Rules\u201d<\/span><\/b> c\u00f3 ngh\u0129a \u0111\u01b0\u1ee3c quy \u0111\u1ecbnh trong GDPR.<\/p>\n\n

\u201cController\u201d<\/span><\/b> c\u00f3 ngh\u0129a \u0111\u01b0\u1ee3c quy \u0111\u1ecbnh trong GDPR.<\/p>\n\n

\u201cController-to-Processor Clauses\u201d<\/span><\/b> ch\u1ec9 c\u00e1c \u0111i\u1ec1u kho\u1ea3n h\u1ee3p \u0111\u1ed3ng ti\u00eau chu\u1ea9n gi\u1eefa c\u00e1c B\u00ean Ki\u1ec3m so\u00e1t v\u00e0 B\u1ed9 x\u1eed l\u00fd cho vi\u1ec7c Chuy\u1ec3n d\u1eef li\u1ec7u, \u0111\u00e3 \u0111\u01b0\u1ee3c Quy\u1ebft \u0111\u1ecbnh Th\u1ef1c hi\u1ec7n c\u1ee7a \u1ee6y ban Ch\u00e2u \u00c2u (EU) 2021\/914 ng\u00e0y 4 th\u00e1ng 6 n\u0103m 2021 ph\u00ea duy\u1ec7t.<\/p>\n\n

\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>\n\n

\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>\n\n

\u201cDocumentation\u201d<\/span><\/b> c\u00f3 ngh\u0129a l\u00e0 t\u00e0i li\u1ec7u hi\u1ec7n h\u00e0nh v\u00e0o th\u1eddi \u0111i\u1ec3m \u0111\u00f3 d\u00e0nh cho D\u1ecbch v\u1ee5 n\u1eb1m t\u1ea1i https:\/\/help.mapsly.com<\/a> (v\u00e0 b\u1ea5t k\u1ef3 v\u1ecb tr\u00ed k\u1ebf nhi\u1ec7m n\u00e0o do MAPSLY ch\u1ec9 \u0111\u1ecbnh).<\/p>\n\n

\u201cEEA\u201d<\/span><\/b> c\u00f3 ngh\u0129a l\u00e0 Khu v\u1ef1c Kinh t\u1ebf Ch\u00e2u \u00c2u.<\/p>\n\n

\u201cEnd Users\u201d<\/span><\/b> c\u00f3 ngh\u0129a l\u00e0 ng\u01b0\u1eddi d\u00f9ng c\u1ee7a t\u00e0i kho\u1ea3n Mapsly c\u1ee7a Kh\u00e1ch h\u00e0ng bao g\u1ed3m nh\u00e2n vi\u00ean v\u00e0 nh\u00e0 th\u1ea7u c\u1ee7a Kh\u00e1ch h\u00e0ng \u0111\u01b0\u1ee3c Kh\u00e1ch h\u00e0ng ch\u1ec9 \u0111\u1ecbnh s\u1eed d\u1ee5ng Mapsly.<\/p>\n\n

\u201cGDPR\u201d<\/span><\/b> ch\u1ec9 th\u1ecb Quy \u0111\u1ecbnh 2016\/679 c\u1ee7a Ngh\u1ecb vi\u1ec7n v\u00e0 H\u1ed9i \u0111\u1ed3ng Ch\u00e2u \u00c2u ng\u00e0y 27 th\u00e1ng 4 n\u0103m 2016 v\u1ec1 b\u1ea3o v\u1ec7 c\u00e1c c\u00e1 nh\u00e2n li\u00ean quan \u0111\u1ebfn vi\u1ec7c x\u1eed l\u00fd d\u1eef li\u1ec7u c\u00e1 nh\u00e2n v\u00e0 v\u1ec1 t\u1ef1 do l\u01b0u chuy\u1ec3n d\u1eef li\u1ec7u \u0111\u00f3, \u0111\u1ed3ng th\u1eddi b\u00e3i b\u1ecf Ch\u1ec9 th\u1ecb 95\/46\/EC (Quy \u0111\u1ecbnh chung v\u1ec1 b\u1ea3o v\u1ec7 d\u1eef li\u1ec7u).<\/p>\n\n

\u201cMAPSLY Network\u201d<\/span><\/b> c\u00f3 ngh\u0129a l\u00e0 c\u00e1c m\u00e1y ch\u1ee7, thi\u1ebft b\u1ecb m\u1ea1ng v\u00e0 h\u1ec7 th\u1ed1ng ph\u1ea7n m\u1ec1m m\u00e1y ch\u1ee7 (v\u00ed d\u1ee5: t\u01b0\u1eddng l\u1eeda \u1ea3o) n\u1eb1m trong quy\u1ec1n ki\u1ec3m so\u00e1t c\u1ee7a MAPSLY v\u00e0 \u0111\u01b0\u1ee3c s\u1eed d\u1ee5ng \u0111\u1ec3 cung c\u1ea5p D\u1ecbch v\u1ee5.<\/p>\n\n

\u201cMAPSLY Setup console\u201d<\/span><\/b> c\u00f3 ngh\u0129a l\u00e0 ph\u1ea7n C\u00e0i \u0111\u1eb7t trong d\u1ecbch v\u1ee5 Mapsly c\u00f3 s\u1eb5n d\u01b0\u1edbi m\u1ee5c \u201cC\u00e0i \u0111\u1eb7t\u201d trong menu ch\u00ednh.<\/p>\n\n

\u201cPersonal Data\u201d<\/span><\/b> ngh\u0129a l\u00e0 d\u1eef li\u1ec7u c\u00e1 nh\u00e2n, th\u00f4ng tin c\u00e1 nh\u00e2n, th\u00f4ng tin \u0111\u1ecbnh danh c\u00e1 nh\u00e2n ho\u1eb7c thu\u1eadt ng\u1eef t\u01b0\u01a1ng \u0111\u01b0\u01a1ng kh\u00e1c (t\u1eebng thu\u1eadt ng\u1eef \u0111\u01b0\u1ee3c \u0111\u1ecbnh ngh\u0129a trong Lu\u1eadt B\u1ea3o v\u1ec7 D\u1eef li\u1ec7u \u00c1p d\u1ee5ng).<\/p>\n\n

\u201cProcessing\u201d<\/span><\/b> c\u00f3 ngh\u0129a \u0111\u01b0\u1ee3c quy \u0111\u1ecbnh trong GDPR v\u00e0 c\u00e1c t\u1eeb \u201cx\u1eed l\u00fd\u201d, \u201cqu\u00e1 tr\u00ecnh x\u1eed l\u00fd\u201d v\u00e0 \u201c\u0111\u00e3 x\u1eed l\u00fd\u201d s\u1ebd \u0111\u01b0\u1ee3c hi\u1ec3u t\u01b0\u01a1ng \u1ee9ng.<\/p>\n\n

\u201cProcessor\u201d<\/span><\/b> c\u00f3 ngh\u0129a \u0111\u01b0\u1ee3c quy \u0111\u1ecbnh trong GDPR.<\/p>\n\n

C\u00e1c \u0111i\u1ec1u kho\u1ea3n t\u1eeb b\u1ed9 x\u1eed l\u00fd \u0111\u1ebfn b\u1ed9 x\u1eed l\u00fd<\/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>\n\n

S\u1ef1 c\u1ed1 b\u1ea3o m\u1eadt<\/span><\/b> c\u00f3 ngh\u0129a l\u00e0 vi ph\u1ea1m an ninh c\u1ee7a MAPSLY d\u1eabn \u0111\u1ebfn vi\u1ec7c ph\u00e1 h\u1ee7y, m\u1ea5t m\u00e1t, thay \u0111\u1ed5i, ti\u1ebft l\u1ed9 tr\u00e1i ph\u00e9p ho\u1eb7c truy c\u1eadp tr\u00e1i ph\u00e1p lu\u1eadt \u0111\u1ed1i v\u1edbi D\u1eef li\u1ec7u Kh\u00e1ch h\u00e0ng.<\/p>\n\n

\u0110i\u1ec1u khi\u1ec3n D\u1ecbch v\u1ee5<\/span><\/b> c\u00f3 ngh\u0129a l\u00e0 c\u00e1c ki\u1ec3m so\u00e1t, bao g\u1ed3m c\u00e1c t\u00ednh n\u0103ng v\u00e0 ch\u1ee9c n\u0103ng b\u1ea3o m\u1eadt, m\u00e0 D\u1ecbch v\u1ee5 cung c\u1ea5p, nh\u01b0 \u0111\u01b0\u1ee3c m\u00f4 t\u1ea3 trong T\u00e0i li\u1ec7u.<\/p>\n\n

\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>\n\n

Qu\u1ed1c gia th\u1ee9 ba<\/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>\n\n

\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>\n\n

\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>\n\n

1. Data Processing<\/h2>\n\n

1.1 Scope and Roles.<\/span><\/b> DPA n\u00e0y \u00e1p d\u1ee5ng khi MAPSLY x\u1eed l\u00fd D\u1eef li\u1ec7u Kh\u00e1ch h\u00e0ng. Trong b\u1ed1i c\u1ea3nh n\u00e0y, MAPSLY s\u1ebd \u0111\u00f3ng vai tr\u00f2 l\u00e0 B\u1ed9 x\u1eed l\u00fd \u0111\u1ed1i v\u1edbi Kh\u00e1ch h\u00e0ng, ng\u01b0\u1eddi c\u00f3 th\u1ec3 \u0111\u00f3ng vai tr\u00f2 l\u00e0 Ng\u01b0\u1eddi ki\u1ec3m so\u00e1t ho\u1eb7c B\u1ed9 x\u1eed l\u00fd D\u1eef li\u1ec7u Kh\u00e1ch h\u00e0ng.<\/p>\n\n

1.2 Customer Controls.<\/span><\/b> Kh\u00e1ch h\u00e0ng c\u00f3 th\u1ec3 s\u1eed d\u1ee5ng c\u00e1c Ki\u1ec3m so\u00e1t D\u1ecbch v\u1ee5 \u0111\u1ec3 h\u1ed7 tr\u1ee3 kh\u00e1ch h\u00e0ng th\u1ef1c hi\u1ec7n c\u00e1c ngh\u0129a v\u1ee5 theo Lu\u1eadt B\u1ea3o v\u1ec7 D\u1eef li\u1ec7u \u00c1p d\u1ee5ng, bao g\u1ed3m ngh\u0129a v\u1ee5 ph\u1ea3n h\u1ed3i c\u00e1c y\u00eau c\u1ea7u t\u1eeb c\u00e1c ch\u1ee7 th\u1ec3 d\u1eef li\u1ec7u. X\u00e9t \u0111\u1ebfn t\u00ednh ch\u1ea5t c\u1ee7a vi\u1ec7c x\u1eed l\u00fd, Kh\u00e1ch h\u00e0ng \u0111\u1ed3ng \u00fd r\u1eb1ng r\u1ea5t \u00edt kh\u1ea3 n\u0103ng MAPSLY s\u1ebd nh\u1eadn bi\u1ebft \u0111\u01b0\u1ee3c D\u1eef li\u1ec7u Kh\u00e1ch h\u00e0ng \u0111\u01b0\u1ee3c chuy\u1ec3n giao theo c\u00e1c \u0110i\u1ec1u kho\u1ea3n H\u1ee3p \u0111\u1ed3ng Chu\u1ea9n kh\u00f4ng ch\u00ednh x\u00e1c ho\u1eb7c \u0111\u00e3 l\u1ed7i th\u1eddi. Tuy nhi\u00ean, n\u1ebfu MAPSLY nh\u1eadn bi\u1ebft \u0111\u01b0\u1ee3c r\u1eb1ng D\u1eef li\u1ec7u Kh\u00e1ch h\u00e0ng \u0111\u01b0\u1ee3c chuy\u1ec3n giao theo c\u00e1c \u0110i\u1ec1u kho\u1ea3n H\u1ee3p \u0111\u1ed3ng Chu\u1ea9n kh\u00f4ng ch\u00ednh x\u00e1c ho\u1eb7c \u0111\u00e3 l\u1ed7i th\u1eddi, MAPSLY s\u1ebd th\u00f4ng b\u00e1o cho Kh\u00e1ch h\u00e0ng m\u00e0 kh\u00f4ng ch\u1eadm tr\u1ec5 kh\u00f4ng c\u1ea7n thi\u1ebft. MAPSLY s\u1ebd h\u1ee3p t\u00e1c v\u1edbi Kh\u00e1ch h\u00e0ng \u0111\u1ec3 x\u00f3a ho\u1eb7c ch\u1ec9nh s\u1eeda D\u1eef li\u1ec7u Kh\u00e1ch h\u00e0ng kh\u00f4ng ch\u00ednh x\u00e1c ho\u1eb7c l\u1ed7i th\u1eddi \u0111\u01b0\u1ee3c chuy\u1ec3n giao theo c\u00e1c \u0110i\u1ec1u kho\u1ea3n H\u1ee3p \u0111\u1ed3ng Chu\u1ea9n b\u1eb1ng c\u00e1ch cung c\u1ea5p c\u00e1c Ki\u1ec3m so\u00e1t D\u1ecbch v\u1ee5 m\u00e0 Kh\u00e1ch h\u00e0ng c\u00f3 th\u1ec3 s\u1eed d\u1ee5ng \u0111\u1ec3 x\u00f3a ho\u1eb7c ch\u1ec9nh s\u1eeda D\u1eef li\u1ec7u Kh\u00e1ch h\u00e0ng.<\/p>\n\n

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

1.3.1 Subject matter.<\/span><\/b> N\u1ed9i dung x\u1eed l\u00fd d\u1eef li\u1ec7u theo DPA n\u00e0y l\u00e0 D\u1eef li\u1ec7u Kh\u00e1ch h\u00e0ng.<\/p>\n\n

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>\n\n

1.3.3 Purpose.<\/span><\/b> M\u1ee5c \u0111\u00edch x\u1eed l\u00fd d\u1eef li\u1ec7u theo DPA n\u00e0y l\u00e0 cung c\u1ea5p D\u1ecbch v\u1ee5 do Kh\u00e1ch h\u00e0ng kh\u1edfi x\u01b0\u1edbng theo t\u1eebng th\u1eddi \u0111i\u1ec3m.<\/p>\n\n

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>\n\n

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>\n\n

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>\n\n

1.4 Compliance with Laws.<\/span><\/b> M\u1ed7i b\u00ean s\u1ebd tu\u00e2n th\u1ee7 t\u1ea5t c\u1ea3 c\u00e1c lu\u1eadt, quy \u0111\u1ecbnh v\u00e0 quy t\u1eafc \u00e1p d\u1ee5ng v\u00e0 r\u00e0ng bu\u1ed9c \u0111\u1ed1i v\u1edbi m\u00ecnh trong vi\u1ec7c th\u1ef1c hi\u1ec7n DPA n\u00e0y, bao g\u1ed3m c\u1ea3 Lu\u1eadt B\u1ea3o v\u1ec7 D\u1eef li\u1ec7u \u00c1p d\u1ee5ng.<\/p>\n\n

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>\n\n

2. Customer Instructions<\/h2>\n\n

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>\n\n

3. Confidentiality of Customer Data<\/h2>\n\n

MAPSLY s\u1ebd kh\u00f4ng truy c\u1eadp ho\u1eb7c s\u1eed d\u1ee5ng, ho\u1eb7c ti\u1ebft l\u1ed9 cho b\u00ean th\u1ee9 ba b\u1ea5t k\u1ef3 D\u1eef li\u1ec7u Kh\u00e1ch h\u00e0ng n\u00e0o, ngo\u1ea1i tr\u1eeb trong m\u1ed7i tr\u01b0\u1eddng h\u1ee3p c\u1ea7n thi\u1ebft \u0111\u1ec3 duy tr\u00ec ho\u1eb7c cung c\u1ea5p D\u1ecbch v\u1ee5, ho\u1eb7c khi c\u1ea7n thi\u1ebft \u0111\u1ec3 tu\u00e2n th\u1ee7 ph\u00e1p lu\u1eadt ho\u1eb7c l\u1ec7nh h\u1ee3p l\u1ec7 v\u00e0 r\u00e0ng bu\u1ed9c c\u1ee7a c\u01a1 quan ch\u00ednh ph\u1ee7 (ch\u1eb3ng h\u1ea1n nh\u01b0 tr\u00e1t h\u1ea7u t\u00f2a ho\u1eb7c l\u1ec7nh c\u1ee7a t\u00f2a \u00e1n). N\u1ebfu c\u01a1 quan ch\u00ednh ph\u1ee7 g\u1eedi y\u00eau c\u1ea7u D\u1eef li\u1ec7u Kh\u00e1ch h\u00e0ng \u0111\u1ebfn MAPSLY, MAPSLY s\u1ebd c\u1ed1 g\u1eafng h\u01b0\u1edbng c\u01a1 quan \u0111\u00f3 y\u00eau c\u1ea7u d\u1eef li\u1ec7u tr\u1ef1c ti\u1ebfp t\u1eeb Kh\u00e1ch h\u00e0ng. L\u00e0 m\u1ed9t ph\u1ea7n c\u1ee7a n\u1ed7 l\u1ef1c n\u00e0y, MAPSLY c\u00f3 th\u1ec3 cung c\u1ea5p th\u00f4ng tin li\u00ean h\u1ec7 c\u01a1 b\u1ea3n c\u1ee7a Kh\u00e1ch h\u00e0ng cho c\u01a1 quan ch\u00ednh ph\u1ee7. N\u1ebfu b\u1ecb bu\u1ed9c ph\u1ea3i ti\u1ebft l\u1ed9 D\u1eef li\u1ec7u Kh\u00e1ch h\u00e0ng cho c\u01a1 quan ch\u00ednh ph\u1ee7, MAPSLY s\u1ebd th\u00f4ng b\u00e1o h\u1ee3p l\u00fd cho Kh\u00e1ch h\u00e0ng v\u1ec1 y\u00eau c\u1ea7u \u0111\u1ec3 Kh\u00e1ch h\u00e0ng c\u00f3 th\u1ec3 t\u00ecm ki\u1ebfm l\u1ec7nh b\u1ea3o v\u1ec7 ho\u1eb7c ph\u01b0\u01a1ng ph\u00e1p kh\u1eafc ph\u1ee5c th\u00edch h\u1ee3p kh\u00e1c, tr\u1eeb khi MAPSLY b\u1ecb ph\u00e1p lu\u1eadt c\u1ea5m l\u00e0m nh\u01b0 v\u1eady.<\/p>\n\n

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

MAPSLY h\u1ea1n ch\u1ebf nh\u00e2n s\u1ef1 c\u1ee7a m\u00ecnh x\u1eed l\u00fd D\u1eef li\u1ec7u Kh\u00e1ch h\u00e0ng m\u00e0 kh\u00f4ng c\u00f3 s\u1ef1 \u1ee7y quy\u1ec1n c\u1ee7a MAPSLY. MAPSLY \u00e1p \u0111\u1eb7t c\u00e1c ngh\u0129a v\u1ee5 h\u1ee3p \u0111\u1ed3ng ph\u00f9 h\u1ee3p \u0111\u1ed1i v\u1edbi nh\u00e2n s\u1ef1, bao g\u1ed3m c\u00e1c ngh\u0129a v\u1ee5 li\u00ean quan \u0111\u1ebfn b\u1ea3o m\u1eadt, b\u1ea3o v\u1ec7 d\u1eef li\u1ec7u v\u00e0 an ninh d\u1eef li\u1ec7u.<\/p>\n\n

5. Security of Data Processing<\/h2>\n\n

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>\n\n

5.2 Customer Responsibilities and Optional Security Features.<\/span><\/b> MAPSLY cung c\u1ea5p nhi\u1ec1u Ki\u1ec3m so\u00e1t D\u1ecbch v\u1ee5 m\u00e0 Kh\u00e1ch h\u00e0ng c\u00f3 th\u1ec3 l\u1ef1a ch\u1ecdn s\u1eed d\u1ee5ng \u0111\u1ec3 t\u0103ng c\u01b0\u1eddng b\u1ea3o m\u1eadt D\u1eef li\u1ec7u Kh\u00e1ch h\u00e0ng. Kh\u00e1ch h\u00e0ng ch\u1ecbu tr\u00e1ch nhi\u1ec7m v\u1ec1 (a) vi\u1ec7c s\u1eed d\u1ee5ng d\u1ecbch v\u1ee5 m\u1ed9t c\u00e1ch an to\u00e0n, bao g\u1ed3m b\u1ea3o v\u1ec7 th\u00f4ng tin x\u00e1c th\u1ef1c t\u00e0i kho\u1ea3n c\u1ee7a m\u00ecnh, (b) b\u1ea3o v\u1ec7 t\u00ednh b\u1ea3o m\u1eadt c\u1ee7a D\u1eef li\u1ec7u Kh\u00e1ch h\u00e0ng khi truy\u1ec1n \u0111i v\u00e0 nh\u1eadn t\u1eeb D\u1ecbch v\u1ee5, (c) th\u1ef1c hi\u1ec7n c\u00e1c b\u01b0\u1edbc ph\u00f9 h\u1ee3p \u0111\u1ec3 m\u00e3 h\u00f3a ho\u1eb7c sao l\u01b0u D\u1eef li\u1ec7u Kh\u00e1ch h\u00e0ng \u0111\u01b0\u1ee3c t\u1ea3i l\u00ean D\u1ecbch v\u1ee5 m\u1ed9t c\u00e1ch an to\u00e0n, (d) c\u1ea5u h\u00ecnh ch\u00ednh x\u00e1c D\u1ecbch v\u1ee5 v\u00e0 c\u00e1c Ki\u1ec3m so\u00e1t D\u1ecbch v\u1ee5, v\u00e0 (e) th\u1ef1c hi\u1ec7n c\u00e1c b\u01b0\u1edbc kh\u00e1c m\u00e0 Kh\u00e1ch h\u00e0ng cho l\u00e0 \u0111\u1ee7 \u0111\u1ec3 \u0111\u1ea3m b\u1ea3o an ninh, b\u1ea3o v\u1ec7 v\u00e0 x\u00f3a D\u1eef li\u1ec7u Kh\u00e1ch h\u00e0ng.<\/p>\n\n

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

5.3.1 Security Incident.<\/span><\/b> MAPSLY s\u1ebd (a) th\u00f4ng b\u00e1o cho Kh\u00e1ch h\u00e0ng v\u1ec1 s\u1ef1 c\u1ed1 An ninh m\u00e0 kh\u00f4ng ch\u1eadm tr\u1ec5 sau khi bi\u1ebft v\u1ec1 s\u1ef1 c\u1ed1 \u0111\u00f3, v\u00e0 (b) th\u1ef1c hi\u1ec7n c\u00e1c bi\u1ec7n ph\u00e1p th\u00edch h\u1ee3p \u0111\u1ec3 gi\u1ea3i quy\u1ebft s\u1ef1 c\u1ed1 An ninh, bao g\u1ed3m c\u00e1c bi\u1ec7n ph\u00e1p gi\u1ea3m thi\u1ec3u b\u1ea5t k\u1ef3 t\u00e1c \u0111\u1ed9ng ti\u00eau c\u1ef1c n\u00e0o ph\u00e1t sinh t\u1eeb s\u1ef1 c\u1ed1 An ninh.<\/p>\n\n

5.3.2 MAPSLY Assistance.<\/span><\/b> \u0110\u1ec3 cho ph\u00e9p Kh\u00e1ch h\u00e0ng th\u00f4ng b\u00e1o m\u1ed9t S\u1ef1 c\u1ed1 B\u1ea3o m\u1eadt cho c\u00e1c c\u01a1 quan gi\u00e1m s\u00e1t ho\u1eb7c c\u00e1c \u0111\u1ed1i t\u01b0\u1ee3ng d\u1eef li\u1ec7u (n\u1ebfu \u00e1p d\u1ee5ng), MAPSLY s\u1ebd h\u1ee3p t\u00e1c v\u00e0 h\u1ed7 tr\u1ee3 Kh\u00e1ch h\u00e0ng b\u1eb1ng c\u00e1ch bao g\u1ed3m trong th\u00f4ng b\u00e1o c\u00e1c th\u00f4ng tin v\u1ec1 S\u1ef1 c\u1ed1 B\u1ea3o m\u1eadt m\u00e0 MAPSLY c\u00f3 th\u1ec3 ti\u1ebft l\u1ed9 cho Kh\u00e1ch h\u00e0ng, c\u00e2n nh\u1eafc t\u00ednh ch\u1ea5t c\u1ee7a vi\u1ec7c x\u1eed l\u00fd, th\u00f4ng tin m\u00e0 MAPSLY c\u00f3 \u0111\u01b0\u1ee3c, v\u00e0 c\u00e1c h\u1ea1n ch\u1ebf trong vi\u1ec7c ti\u1ebft l\u1ed9 th\u00f4ng tin, ch\u1eb3ng h\u1ea1n nh\u01b0 t\u00ednh b\u1ea3o m\u1eadt. C\u00e2n nh\u1eafc t\u00ednh ch\u1ea5t c\u1ee7a vi\u1ec7c x\u1eed l\u00fd, Kh\u00e1ch h\u00e0ng \u0111\u1ed3ng \u00fd r\u1eb1ng h\u1ecd l\u00e0 ng\u01b0\u1eddi c\u00f3 kh\u1ea3 n\u0103ng x\u00e1c \u0111\u1ecbnh h\u1eadu qu\u1ea3 c\u00f3 th\u1ec3 x\u1ea3y ra c\u1ee7a m\u1ed9t S\u1ef1 c\u1ed1 B\u1ea3o m\u1eadt.<\/p>\n\n

5.3.3 Unsuccessful Security Incidents.<\/span><\/b> Kh\u00e1ch h\u00e0ng \u0111\u1ed3ng \u00fd r\u1eb1ng:<\/p>\n\n

(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>\n\n

(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>\n\n

5.3.4 Communication.<\/span><\/b> Th\u00f4ng b\u00e1o v\u1ec1 S\u1ef1 c\u1ed1 An ninh, n\u1ebfu c\u00f3, s\u1ebd \u0111\u01b0\u1ee3c g\u1eedi \u0111\u1ebfn m\u1ed9t ho\u1eb7c nhi\u1ec1u qu\u1ea3n tr\u1ecb vi\u00ean c\u1ee7a Kh\u00e1ch h\u00e0ng b\u1eb1ng b\u1ea5t k\u1ef3 ph\u01b0\u01a1ng th\u1ee9c n\u00e0o do MAPSLY ch\u1ecdn, bao g\u1ed3m qua email. \u0110\u00e2y l\u00e0 tr\u00e1ch nhi\u1ec7m duy nh\u1ea5t c\u1ee7a Kh\u00e1ch h\u00e0ng \u0111\u1ec3 \u0111\u1ea3m b\u1ea3o c\u00e1c qu\u1ea3n tr\u1ecb vi\u00ean c\u1ee7a h\u1ecd duy tr\u00ec th\u00f4ng tin li\u00ean h\u1ec7 ch\u00ednh x\u00e1c tr\u00ean b\u1ea3ng \u0111i\u1ec1u khi\u1ec3n C\u00e0i \u0111\u1eb7t MAPSLY v\u00e0 \u0111\u1ea3m b\u1ea3o truy\u1ec1n t\u1ea3i an to\u00e0n m\u1ecdi l\u00fac.<\/p>\n\n

5.3.5 Notification Obligations.<\/span><\/b> N\u1ebfu MAPSLY th\u00f4ng b\u00e1o cho Kh\u00e1ch h\u00e0ng v\u1ec1 m\u1ed9t S\u1ef1 c\u1ed1 B\u1ea3o m\u1eadt, ho\u1eb7c Kh\u00e1ch h\u00e0ng bi\u1ebft \u0111\u01b0\u1ee3c b\u1ea5t k\u1ef3 vi\u1ec7c ph\u00e1 ho\u1ea1i, m\u1ea5t m\u00e1t, thay \u0111\u1ed5i, ti\u1ebft l\u1ed9 tr\u00e1i ph\u00e9p ho\u1eb7c truy c\u1eadp tr\u00e1i ph\u00e9p n\u00e0o \u0111\u1ed1i v\u1edbi D\u1eef li\u1ec7u Kh\u00e1ch h\u00e0ng, Kh\u00e1ch h\u00e0ng s\u1ebd ch\u1ecbu tr\u00e1ch nhi\u1ec7m (a) x\u00e1c \u0111\u1ecbnh xem c\u00f3 b\u1ea5t k\u1ef3 ngh\u0129a v\u1ee5 th\u00f4ng b\u00e1o ho\u1eb7c ngh\u0129a v\u1ee5 n\u00e0o kh\u00e1c theo Lu\u1eadt B\u1ea3o v\u1ec7 D\u1eef li\u1ec7u \u00c1p d\u1ee5ng kh\u00f4ng v\u00e0 (b) th\u1ef1c hi\u1ec7n c\u00e1c h\u00e0nh \u0111\u1ed9ng c\u1ea7n thi\u1ebft \u0111\u1ec3 tu\u00e2n th\u1ee7 c\u00e1c ngh\u0129a v\u1ee5 \u0111\u00f3. \u0110i\u1ec1u n\u00e0y kh\u00f4ng gi\u1edbi h\u1ea1n c\u00e1c ngh\u0129a v\u1ee5 c\u1ee7a MAPSLY theo M\u1ee5c 5.3 n\u00e0y.<\/p>\n\n

6. Sub-processing<\/h2>\n\n

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>\n\n

6.2 Sub-processor Obligations.<\/span><\/b> Khi MAPSLY \u1ee7y quy\u1ec1n cho m\u1ed9t \u0110\u01a1n v\u1ecb x\u1eed l\u00fd ph\u1ee5 nh\u01b0 m\u00f4 t\u1ea3 trong M\u1ee5c 6.1:<\/p>\n\n

(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>\n\n

(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>\n\n

(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>\n\n

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

Xem x\u00e9t \u0111\u1ebfn t\u00ednh ch\u1ea5t c\u1ee7a vi\u1ec7c x\u1eed l\u00fd, C\u00f4ng c\u1ee5 Ki\u1ec3m so\u00e1t D\u1ecbch v\u1ee5 l\u00e0 c\u00e1c bi\u1ec7n ph\u00e1p k\u1ef9 thu\u1eadt v\u00e0 t\u1ed5 ch\u1ee9c m\u00e0 MAPSLY s\u1ebd h\u1ed7 tr\u1ee3 Kh\u00e1ch h\u00e0ng trong vi\u1ec7c ho\u00e0n th\u00e0nh ngh\u0129a v\u1ee5 c\u1ee7a Kh\u00e1ch h\u00e0ng \u0111\u1ec3 ph\u1ea3n h\u1ed3i c\u00e1c y\u00eau c\u1ea7u t\u1eeb ch\u1ee7 th\u1ec3 d\u1eef li\u1ec7u theo Lu\u1eadt B\u1ea3o v\u1ec7 D\u1eef li\u1ec7u \u00c1p d\u1ee5ng. N\u1ebfu m\u1ed9t ch\u1ee7 th\u1ec3 d\u1eef li\u1ec7u g\u1eedi y\u00eau c\u1ea7u \u0111\u1ebfn MAPSLY, MAPSLY s\u1ebd nhanh ch\u00f3ng chuy\u1ec3n ti\u1ebfp y\u00eau c\u1ea7u \u0111\u00f3 t\u1edbi Kh\u00e1ch h\u00e0ng ngay khi MAPSLY x\u00e1c \u0111\u1ecbnh r\u1eb1ng y\u00eau c\u1ea7u \u0111\u00f3 \u0111\u1ebfn t\u1eeb ch\u1ee7 th\u1ec3 d\u1eef li\u1ec7u m\u00e0 Kh\u00e1ch h\u00e0ng ch\u1ecbu tr\u00e1ch nhi\u1ec7m. Kh\u00e1ch h\u00e0ng \u1ee7y quy\u1ec1n thay m\u1eb7t m\u00ecnh, v\u00e0 thay m\u1eb7t c\u00e1c b\u1ed9 \u0111i\u1ec1u khi\u1ec3n c\u1ee7a m\u00ecnh khi Kh\u00e1ch h\u00e0ng \u0111\u00f3ng vai tr\u00f2 l\u00e0 B\u1ed9 x\u1eed l\u00fd, cho MAPSLY \u0111\u1ec3 ph\u1ea3n h\u1ed3i b\u1ea5t k\u1ef3 ch\u1ee7 th\u1ec3 d\u1eef li\u1ec7u n\u00e0o g\u1eedi y\u00eau c\u1ea7u \u0111\u1ebfn MAPSLY, nh\u1eb1m x\u00e1c nh\u1eadn r\u1eb1ng MAPSLY \u0111\u00e3 chuy\u1ec3n ti\u1ebfp y\u00eau c\u1ea7u \u0111\u00f3 \u0111\u1ebfn Kh\u00e1ch h\u00e0ng. C\u00e1c b\u00ean \u0111\u1ed3ng \u00fd r\u1eb1ng vi\u1ec7c Kh\u00e1ch h\u00e0ng s\u1eed d\u1ee5ng C\u00f4ng c\u1ee5 Ki\u1ec3m so\u00e1t D\u1ecbch v\u1ee5 v\u00e0 MAPSLY chuy\u1ec3n ti\u1ebfp c\u00e1c y\u00eau c\u1ea7u t\u1eeb ch\u1ee7 th\u1ec3 d\u1eef li\u1ec7u \u0111\u1ebfn Kh\u00e1ch h\u00e0ng theo ph\u1ea7n n\u00e0y \u0111\u1ea1i di\u1ec7n cho ph\u1ea1m vi v\u00e0 m\u1ee9c \u0111\u1ed9 h\u1ed7 tr\u1ee3 c\u1ea7n thi\u1ebft c\u1ee7a Kh\u00e1ch h\u00e0ng.<\/p>\n\n

8. Compliance Verification<\/h2>\n\n

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>\n\n

8.2 Audit Reports.<\/span><\/b> Theo y\u00eau c\u1ea7u b\u1eb1ng v\u0103n b\u1ea3n c\u1ee7a Kh\u00e1ch h\u00e0ng, v\u00e0 v\u1edbi \u0111i\u1ec1u ki\u1ec7n c\u00e1c b\u00ean c\u00f3 th\u1ecfa thu\u1eadn NDA \u00e1p d\u1ee5ng, MAPSLY s\u1ebd cung c\u1ea5p cho Kh\u00e1ch h\u00e0ng m\u1ed9t b\u1ea3n sao B\u00e1o c\u00e1o \u0111\u1ec3 Kh\u00e1ch h\u00e0ng c\u00f3 th\u1ec3 ki\u1ec3m tra h\u1ee3p l\u00fd vi\u1ec7c MAPSLY tu\u00e2n th\u1ee7 c\u00e1c ngh\u0129a v\u1ee5 c\u1ee7a m\u00ecnh theo DPA n\u00e0y.<\/p>\n\n

8.3 Privacy Impact Assessment and Prior Consultation.<\/span><\/b> Xem x\u00e9t t\u00ednh ch\u1ea5t c\u1ee7a vi\u1ec7c x\u1eed l\u00fd v\u00e0 th\u00f4ng tin MAPSLY c\u00f3 \u0111\u01b0\u1ee3c, MAPSLY s\u1ebd h\u1ed7 tr\u1ee3 Kh\u00e1ch h\u00e0ng trong vi\u1ec7c tu\u00e2n th\u1ee7 c\u00e1c ngh\u0129a v\u1ee5 c\u1ee7a Kh\u00e1ch h\u00e0ng li\u00ean quan \u0111\u1ebfn \u0111\u00e1nh gi\u00e1 t\u00e1c \u0111\u1ed9ng b\u1ea3o v\u1ec7 d\u1eef li\u1ec7u v\u00e0 tham v\u1ea5n tr\u01b0\u1edbc b\u1eb1ng c\u00e1ch cung c\u1ea5p c\u00e1c th\u00f4ng tin m\u00e0 MAPSLY cung c\u1ea5p theo M\u1ee5c 8 n\u00e0y.<\/p>\n\n

9. Transfers of Personal Data<\/h2>\n\n

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>\n\n

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>\n\n

9.2.1<\/span><\/b> Khi Kh\u00e1ch h\u00e0ng \u0111\u00f3ng vai tr\u00f2 l\u00e0 Ng\u01b0\u1eddi ki\u1ec3m so\u00e1t, c\u00e1c \u0110i\u1ec1u kho\u1ea3n t\u1eeb Ng\u01b0\u1eddi ki\u1ec3m so\u00e1t t\u1edbi Ng\u01b0\u1eddi x\u1eed l\u00fd s\u1ebd \u00e1p d\u1ee5ng cho Vi\u1ec7c chuy\u1ec3n d\u1eef li\u1ec7u.<\/p>\n\n

9.2.2<\/span><\/b> Khi Kh\u00e1ch h\u00e0ng ho\u1ea1t \u0111\u1ed9ng nh\u01b0 m\u1ed9t B\u1ed9 x\u1eed l\u00fd, c\u00e1c \u0110i\u1ec1u kho\u1ea3n B\u1ed9 x\u1eed l\u00fd-\u0111\u1ebfn-B\u1ed9 x\u1eed l\u00fd s\u1ebd \u00e1p d\u1ee5ng cho Vi\u1ec7c Chuy\u1ec3n d\u1eef li\u1ec7u. Xem x\u00e9t \u0111\u1ebfn t\u00ednh ch\u1ea5t c\u1ee7a vi\u1ec7c x\u1eed l\u00fd, Kh\u00e1ch h\u00e0ng \u0111\u1ed3ng \u00fd r\u1eb1ng MAPSLY kh\u00f3 c\u00f3 th\u1ec3 bi\u1ebft \u0111\u01b0\u1ee3c danh t\u00ednh c\u1ee7a c\u00e1c B\u1ed9 \u0111i\u1ec1u khi\u1ec3n c\u1ee7a Kh\u00e1ch h\u00e0ng v\u00ec MAPSLY kh\u00f4ng c\u00f3 m\u1ed1i quan h\u1ec7 tr\u1ef1c ti\u1ebfp v\u1edbi c\u00e1c B\u1ed9 \u0111i\u1ec1u khi\u1ec3n c\u1ee7a Kh\u00e1ch h\u00e0ng v\u00e0 do \u0111\u00f3, Kh\u00e1ch h\u00e0ng s\u1ebd th\u1ef1c hi\u1ec7n c\u00e1c ngh\u0129a v\u1ee5 c\u1ee7a MAPSLY \u0111\u1ed1i v\u1edbi c\u00e1c B\u1ed9 \u0111i\u1ec1u khi\u1ec3n c\u1ee7a Kh\u00e1ch h\u00e0ng theo c\u00e1c \u0110i\u1ec1u kho\u1ea3n B\u1ed9 x\u1eed l\u00fd-\u0111\u1ebfn-B\u1ed9 x\u1eed l\u00fd.<\/p>\n\n

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>\n\n

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>\n\n

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>\n\n

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>\n\n

10. Termination of the DPA<\/h2>\n\n

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

11. Deletion of Customer Data<\/h2>\n\n

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>\n\n

12. Duties to Inform<\/h2>\n\n

Khi D\u1eef li\u1ec7u Kh\u00e1ch h\u00e0ng tr\u1edf th\u00e0nh \u0111\u1ed1i t\u01b0\u1ee3ng b\u1ecb t\u1ecbch thu trong c\u00e1c th\u1ee7 t\u1ee5c ph\u00e1 s\u1ea3n ho\u1eb7c v\u1ee1 n\u1ee3 ho\u1eb7c c\u00e1c bi\u1ec7n ph\u00e1p t\u01b0\u01a1ng t\u1ef1 b\u1edfi b\u00ean th\u1ee9 ba trong qu\u00e1 tr\u00ecnh \u0111\u01b0\u1ee3c x\u1eed l\u00fd b\u1edfi MAPSLY, MAPSLY s\u1ebd th\u00f4ng b\u00e1o cho Kh\u00e1ch h\u00e0ng m\u00e0 kh\u00f4ng ch\u1eadm tr\u1ec5 kh\u00f4ng c\u1ea7n thi\u1ebft. MAPSLY s\u1ebd, kh\u00f4ng ch\u1eadm tr\u1ec5 kh\u00f4ng c\u1ea7n thi\u1ebft, th\u00f4ng b\u00e1o cho t\u1ea5t c\u1ea3 c\u00e1c b\u00ean li\u00ean quan trong h\u00e0nh \u0111\u1ed9ng \u0111\u00f3 (v\u00ed d\u1ee5, ch\u1ee7 n\u1ee3, qu\u1ea3n t\u00e0i vi\u00ean ph\u00e1 s\u1ea3n) r\u1eb1ng b\u1ea5t k\u1ef3 D\u1eef li\u1ec7u Kh\u00e1ch h\u00e0ng n\u00e0o b\u1ecb t\u00e1c \u0111\u1ed9ng b\u1edfi c\u00e1c th\u1ee7 t\u1ee5c \u0111\u00f3 l\u00e0 t\u00e0i s\u1ea3n v\u00e0 tr\u00e1ch nhi\u1ec7m c\u1ee7a Kh\u00e1ch h\u00e0ng v\u00e0 D\u1eef li\u1ec7u Kh\u00e1ch h\u00e0ng thu\u1ed9c quy\u1ec1n ki\u1ec3m so\u00e1t duy nh\u1ea5t c\u1ee7a Kh\u00e1ch h\u00e0ng.<\/p>\n\n

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

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>\n\n

14. Google Workspace API Data<\/h2>\n\n

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>\n\n

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

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>\n\n