メインコンテンツにスキップ

Data Processing Agreement

This Data Processing Agreement (the "DPA") supplements the Reseller Agreement, the Commercial Agreement or any other agreement in force between LIVA DOT COM (ASIA) CO., LTD. ("Liva") and the Agent, operator or partner accepting it (the "Counterparty") (together, the "Principal Agreement"). Liva Core SASU (France, SIREN 908 471 303) operates the Liva platform and is a controller of its customer data under the Liva Privacy Policy. It is a party to this DPA for data on the platform and may enforce it. "Liva" includes Liva Core SASU where the context requires.

It applies whenever one party processes personal data on behalf of the other, or shares it with the other, in connection with the Principal Agreement. Where it conflicts with the Principal Agreement on data protection, this DPA prevails.

1. Definitions

"Applicable Data Protection Law" means the Thai Personal Data Protection Act B.E. 2562 (2019) ("PDPA"), Regulation (EU) 2016/679 ("EU GDPR"), the EU GDPR as it forms part of the law of the United Kingdom ("UK GDPR") with the UK Data Protection Act 2018, where they apply, and any other data protection law applicable to a party's processing under the Principal Agreement. "GDPR" means the EU GDPR and UK GDPR as the context requires. "Controller", "Processor", "Data Subject", "Personal Data", "Processing" and "Personal Data Breach" have the meanings in the GDPR and the equivalents under the PDPA. "Sub-processor" means a third party engaged by a Processor.

2. Roles of the parties

Ordinarily each party is an independent Controller of the Personal Data it holds for its own purposes. For a Booking made through an Agent: Liva is a Controller for the booking transaction, payment, refunds and its customer relationship; the Agent is a Controller for its own customer relationship, its own legal duties, and the passenger data it collects and uses to make and service the Booking. Neither party is the other's Processor by default. A processing relationship arises only where the parties agree in writing that one party processes specified Personal Data on the other's behalf on documented instructions; then clauses 3 to 12 apply with the instructing party as Controller. A transfer between independent Controllers is not a disclosure to a Processor. Each party is responsible for its own lawful basis, notice and retention.

3. Details of processing

Unless recorded otherwise in writing: Data Subjects are passengers and travellers and each party's staff and contact persons. Data types are name; contact details; booking, journey and itinerary details; passenger manifest details required by the Provider or by law; payment reference and status; correspondence about a Booking; and identification or travel-document data that law requires. Duration is the term of the Principal Agreement and any legally required retention. Special category data is not processed under this DPA, except where a party must process accessibility or medical-assistance information by law to carry a passenger safely, in which case it does so as an independent Controller.

4. Processor obligations

Where acting as Processor, a party shall: process only on the Controller's documented instructions, including on international transfers, unless law requires otherwise (then informing the Controller first unless the law forbids it); immediately tell the Controller if an instruction in its opinion infringes the law; ensure those authorised to process are bound by confidentiality; and not sell the data or use it for its own purposes, including its own marketing. Whether acting as Processor or Controller, a party shall not use Personal Data received from the other to train any artificial-intelligence model.

5. Security

Each party shall apply appropriate technical and organisational measures for the risk, including those in Annex 2 as a minimum.

6. Sub-processors

A Processor engages a Sub-processor only with the Controller's prior written authorisation, which may be general. Where general, it informs the Controller of changes in time to object. It binds each Sub-processor by contract to no less protective terms and stays fully liable. Liva's sub-processors are named in its Privacy Policy.

7. Data Subject rights

Each party handles requests about the Personal Data it holds as Controller. A Processor assists the Controller, as far as possible, with requests, and forwards without undue delay any request about data for which the other is Controller, without answering substantively unless legally required.

8. Personal Data Breach

Each party shall notify the other without undue delay, and within seventy-two (72) hours, of becoming aware of a Personal Data Breach affecting Personal Data exchanged under the Principal Agreement, giving, as far as known, the nature, categories and number of Data Subjects and records, likely consequences, measures taken and a contact point. Information not yet available may follow in phases. Neither party names the other in a public statement about a breach without consulting it, unless law or a regulator requires.

9. Assistance, deletion, audit

Where acting as Processor, a party gives reasonable help with impact assessments and prior consultation, deletes or returns the data at the Controller's choice when the Principal Agreement ends (except where law requires retention), and makes available the information needed to show compliance, allowing audits on at least thirty (30) days' notice, at most once a year unless a breach or regulator requires otherwise, in business hours and under confidentiality, each side bearing its own costs. Each party as Controller applies its own retention schedule.

10. International transfers

10.1 Neither party transfers Personal Data exchanged under the Principal Agreement outside the country where it was collected unless a lawful transfer mechanism is in place (for the GDPR an adequacy decision, Standard Contractual Clauses or another Chapter V mechanism; for the PDPA a mechanism under sections 28 and 29). On request each party shows the other the mechanism it relies on.

10.2 Transfers to Thailand and from the EEA or UK. Liva Core SASU operates the platform in the European Union; Personal Data is made available to Liva in Thailand, which has no European Commission adequacy decision. Where Personal Data is transferred from the EEA to the Counterparty or Liva outside the EEA, the parties agree the Standard Contractual Clauses in the Annex to Commission Implementing Decision (EU) 2021/914 ("SCCs"), Module One (controller to controller) or, where this DPA creates a processing relationship, Module Two (controller to processor), incorporated by reference with these choices: clause 7 (docking clause) applies; clause 11(a) optional wording does not apply; clause 17 Option 1 (the law of France); clause 18(b) (the courts of France); the competent supervisory authority is that of the exporter's EU Member State, and for Liva Core SASU the CNIL; Annex I and Annex II are Annexes 1 and 2 to this DPA. For transfers from the United Kingdom the parties incorporate the UK International Data Transfer Addendum to the SCCs (version B1.0 issued by the ICO under section 119A of the Data Protection Act 2018), with the tables completed by Annex 1 and the "importer" and "exporter" as the transferring and receiving parties; either party may end the Addendum as its section 19 allows. If the SCCs and this DPA conflict, the SCCs prevail.

10.3 Transfers from Thailand. Where Liva transfers Personal Data to the Counterparty outside Thailand, the parties rely on the performance of the contract with the Data Subject (PDPA section 28), and the Counterparty applies the protections in this DPA and the SCC terms in clause 10.2 as appropriate safeguards.

10.4 The parties acknowledge that making a journey requires the Provider to receive passenger details in the country of travel, which is a transfer for the performance of a contract with the Data Subject.

11. Liability, term, language and law

Each party is responsible for its own compliance and for any fine or claim arising from its own act or omission. Liability under this DPA is subject to the limits in the Principal Agreement, except where it cannot lawfully be limited, including liability to a Data Subject or supervisory authority. This DPA starts when accepted and lasts while either party processes Personal Data under the Principal Agreement. Liva may publish a new version for a change in law or processing; the Agent Account shows it as requiring acceptance and records the version, date and name. It is in English and the English version prevails. It is governed by the law of the Principal Agreement, except that the SCCs are governed by the law stated in clause 10.2. If a provision is invalid the rest continues.

Annex 1 — Description of the transfer (SCC Annex I and UK Addendum Tables 1 and 3)

A. Parties - Data exporter and importer: each of Liva Core SASU, 2 avenue du Président Pierre Angot, 64000 Pau, France; LIVA DOT COM (ASIA) CO., LTD., Thailand; and the Counterparty named in the Agent Account, as transferor or recipient according to the flow. Contact: the data protection contact recorded in the Agent Account and in Liva's Privacy Policy. Role: independent controllers (Module One), or exporter controller and importer processor where a processing relationship is agreed (Module Two). - Signature and date: acceptance of this DPA in the Agent Account, recorded with the date, version and name.

B. Description of transfer - Data Subjects: passengers and travellers; the parties' staff and contact persons. - Data: as clause 3. - Sensitive data: none, except as clause 3 allows. - Frequency: continuous, each Booking. - Nature and purpose: making, servicing, changing, refunding and reconciling Bookings, customer service, fraud prevention, accounting and legal compliance. - Retention: for the Principal Agreement and each party's own schedule, and as law requires. - Transfers to Sub-processors: as clause 6 and the Privacy Policy.

C. Competent supervisory authority: the authority of the EU Member State of the exporter; for Liva Core SASU the CNIL (France). For the United Kingdom, the Information Commissioner's Office.

Annex 2 — Technical and organisational measures (SCC Annex II and UK Addendum Table 3)

  • Encryption in transit (TLS) and, where available, at rest.
  • Individual accounts, multi-factor authentication for administrative access, role-based least-privilege access, no shared credentials.
  • Access logging and review.
  • Vulnerability and patch management.
  • Backups and restore testing; the ability to restore availability after an incident.
  • Incident response with notice under clause 8.
  • Staff confidentiality and training; supplier checks.
  • Data minimisation and retention limits.