ePAL logoePAL Global
Merchant agreements

Data processing agreement

How ePAL handles personal data when providing cross-border calculation, integration, compliance and audit services on behalf of merchants.

Version 0.1 · 31 October 2026

What this agreement does. This Data Processing Agreement (DPA) forms part of the contractual terms between ePAL Global Limited (ePAL) and the business merchant or other customer engaging ePAL (Merchant). It governs the processing of personal data by ePAL on the Merchant's behalf when providing the ePAL services.

It applies across ePAL's WooCommerce integrations, Shopify integrations and direct API services, to the extent that ePAL processes personal data for the Merchant. The Merchant is ordinarily the controller and ePAL the processor for that processing. Each party may also act as an independent controller for personal data it processes for its own purposes.

1. Definitions

Data Protection Laws means the EU General Data Protection Regulation (Regulation (EU) 2016/679), applicable Irish data protection law and, where applicable to the processing, the UK GDPR and other applicable data protection legislation.

Personal Data, Controller, Processor, Processing, Data Subject, Personal Data Breach and Supervisory Authority have the meanings given to them in the applicable Data Protection Laws.

Merchant Personal Data means Personal Data processed by ePAL on the Merchant's behalf under the Services.

Services means the ePAL cross-border eCommerce services subscribed to or enabled by the Merchant, including calculations, integrations, compliance screening, order and fulfilment support, reporting and audit evidence where applicable.

Merchant-designated provider means a third party chosen and contracted directly by the Merchant and connected to ePAL on the Merchant's instructions.

Sub-processor means another processor engaged by ePAL to process Merchant Personal Data on behalf of the Merchant.

2. Scope, roles and documented instructions

2.1. For Merchant Personal Data, the Merchant determines the purposes and essential means of processing and ePAL processes that data on its behalf. The Merchant's documented instructions consist of this DPA, the applicable services agreement, enabled features, configuration selections and written instructions supplied through authorised support or account channels.

2.2. ePAL shall process Merchant Personal Data only on documented instructions from the Merchant, including with regard to transfers of Personal Data to a third country or international organisation, unless required to do otherwise by applicable EU or Member State law. In that case, ePAL shall inform the Merchant before processing unless the law prohibits doing so on important grounds of public interest.

2.3. The Merchant instructs ePAL to process the types of data described in Schedule A for the agreed Services. Only information relevant to an enabled feature should be accessed or shared. Where an integration makes additional fields technically accessible, that access does not authorise unrelated use.

2.4. ePAL shall inform the Merchant promptly if, in ePAL's opinion, an instruction infringes applicable Data Protection Laws. ePAL is not required to carry out an unlawful instruction.

2.5. Each party acts as an independent controller for its own account administration, business contact, billing and other genuinely independent purposes. Such processing is governed by applicable law and the relevant party's privacy information, not by this processor DPA.

3. Merchant-designated third-party providers

3.1. The Merchant may connect its existing service providers to ePAL, such as a shipping carrier with which it already holds an account. For example, ePAL may transmit shipment parameters to DHL using the Merchant's authorised integration to obtain shipping rates.

3.2. The Merchant instructs and authorises ePAL to send data to and receive data from providers it selects or configures, solely to deliver the relevant integration and Services. ePAL does not acquire the right to use that data for unrelated purposes merely because it acts as a technical routing or integration layer.

3.3. A merchant-designated provider is not automatically an ePAL Sub-processor. Its GDPR role depends on the actual services, contractual relationships and purposes of processing. Where the provider acts directly for the Merchant, the Merchant is responsible for establishing the necessary contractual and lawful arrangements with that provider. Where the facts instead make it an ePAL-appointed Sub-processor, Section 4 applies.

3.4. ePAL remains responsible for the security and lawfulness of its own processing and transmissions under this DPA. Nothing in this Section excludes responsibilities imposed by Data Protection Laws.

4. ePAL-appointed sub-processors

4.1. The Merchant grants ePAL general written authorisation to engage Sub-processors where needed to deliver the particular Services enabled, configured or otherwise agreed with the Merchant on a case-by-case basis. This authorisation does not mean that every Sub-processor or processing activity is used for every Merchant.

4.2. The categories of Sub-processors may include hosting and technical infrastructure, compliance and sanctions screening, integration support and other specialist providers necessary for the agreed Services. ePAL shall share Merchant Personal Data with a Sub-processor only where relevant to the Services actually provided to that Merchant and on documented instructions.

4.3. ePAL shall have a written agreement with each Sub-processor imposing data protection obligations providing at least the level of protection required by Article 28(3) GDPR. ePAL remains liable to the Merchant for the performance of applicable Sub-processor obligations as required by Article 28(4) GDPR.

4.4. ePAL shall maintain and make available an up-to-date list identifying its authorised Sub-processors and their processing functions. Under this general authorisation, ePAL shall give the Merchant advance notice of intended additions or replacements affecting its Services and a genuine opportunity to object before the change takes effect. The relevant notice period and objection procedure shall be communicated to the Merchant as part of the agreed service arrangements.

4.5. The parties shall address a reasoned data protection objection in good faith, including considering a suitable alternative where reasonably available. If no practicable solution is available, the Merchant may discontinue the affected Service in accordance with the applicable services agreement, without prejudice to mandatory rights.

4.6. Where a third-party provider processes Personal Data as an independent controller rather than as ePAL’s Sub-processor, ePAL shall treat that disclosure according to the provider’s actual legal role and applicable data protection requirements.

5. Security and confidentiality

5.1. ePAL shall implement appropriate technical and organisational measures under Article 32 GDPR, taking account of the nature, scope, context and purposes of processing and the risks to individuals. The applicable categories of measures are described in Schedule D.

5.2. ePAL shall ensure that persons authorised to process Merchant Personal Data are subject to confidentiality obligations and receive access only where necessary for their responsibilities.

5.3. ePAL shall periodically review its safeguards and maintain appropriate controls over its systems and Sub-processors. The Merchant remains responsible for securely configuring and controlling its own accounts, credentials and Merchant-appointed providers.

6. Data subject rights and merchant assistance

6.1. Taking into account the nature of the processing, ePAL shall assist the Merchant by appropriate technical and organisational measures, insofar as possible, in responding to requests from individuals exercising their data protection rights.

6.2. Where ePAL receives a request relating to Merchant Personal Data, it shall refer the request to the Merchant without undue delay, unless legally prohibited, and shall not independently determine the Merchant's response.

6.3. Taking into account the information available to ePAL and the nature of processing, ePAL shall assist the Merchant in meeting its obligations under Articles 32 to 36 GDPR, including security, breach assessment and notification, data protection impact assessments and prior consultation where relevant.

7. Personal data breaches

7.1. ePAL shall notify the Merchant without undue delay after becoming aware of a Personal Data Breach affecting Merchant Personal Data. Notification shall be made through the Merchant's registered or designated security or administrative contact.

7.2. ePAL shall provide available information reasonably required for the Merchant to assess and fulfil its legal obligations, including the nature of the breach, affected data where known, likely consequences and measures taken or proposed. Information may be provided in stages as an investigation progresses.

7.3. ePAL shall take appropriate steps to contain, investigate and remediate a breach and cooperate with the Merchant. The Merchant remains responsible for determining and making any notifications required of it as controller, without prejudice to any independent legal obligations of ePAL.

8. International transfers

8.1. ePAL shall not transfer Merchant Personal Data outside the European Economic Area, or permit such transfers by Sub-processors, unless the transfer is authorised and supported by a lawful transfer mechanism where required, including an adequacy decision or appropriate safeguards under Chapter V GDPR.

8.2. Where applicable, the parties shall enter into the relevant European Commission standard contractual clauses for international transfers and implement supplementary measures as necessary. UK-restricted transfers shall use an applicable UK transfer mechanism where required.

8.3. The relevant locations, providers and safeguards shall be identified in the operational Sub-processor Register. Merely listing a provider in this DPA does not establish that a transfer is lawful.

9. Audit evidence, retention and end of services

9.1. The Merchant remains responsible for its own sanctions, customs, tax and other regulatory compliance obligations. ePAL may carry out screening and retain records on the Merchant's behalf to help demonstrate which checks were performed and support later enquiries, audits or disputes. ePAL does not thereby assume the Merchant's substantive regulatory responsibilities.

9.2. As part of the Services, the Merchant instructs ePAL to retain the relevant recipient details, results, decision information, transaction references and related audit evidence for the applicable periods set out in ePAL’s Data Retention Schedule referenced in Schedule B. Such periods are set by ePAL as standard service parameters and adopted by the Merchant through acceptance of this DPA. The periods must be proportionate and supported by a documented retention rationale.

9.3. Personal Data retained for audit purposes shall not be used for unrelated commercial purposes. Access shall be controlled, retention periods reviewed as necessary and data deleted or anonymised when no longer needed for an authorised purpose, subject to applicable law.

9.4. At the end of provision of processing services, ePAL shall, at the Merchant's choice, delete or return Merchant Personal Data and delete existing copies unless EU or Member State law requires storage. The Merchant's choice shall be obtained through a suitable termination or account-closure process. A standard contractual retention period does not independently override this requirement.

9.5. Where deletion from backups cannot be immediate, ePAL shall keep affected data beyond ordinary use, protect it against further processing and delete it through a documented backup expiry or deletion cycle, subject to applicable law. ePAL shall explain relevant practical constraints to the Merchant.

9.6. If ePAL independently needs certain data for its own lawful purposes, such processing shall be separately identified and governed by an appropriate controller basis and transparency information. It shall not be presented as Merchant-instructed processing merely to avoid end-of-contract deletion obligations.

10. Information, compliance and audits

10.1. ePAL shall make available to the Merchant information necessary to demonstrate compliance with Article 28 GDPR and allow for and contribute to audits and inspections conducted by the Merchant or an auditor mandated by the Merchant.

10.2. The parties shall coordinate audits in good faith to protect confidentiality, security and the rights of other customers. ePAL may offer reasonably adequate independent assurance reports and relevant documentation in the first instance, but shall not use that process to negate the Merchant's rights under Article 28(3)(h).

10.3. ePAL shall cooperate with competent supervisory authorities as required by law.

11. Responsibilities of the Merchant

11.1. The Merchant is responsible for identifying a valid legal basis for its processing and disclosures, providing required notices to individuals, ensuring its instructions are lawful and supplying accurate information necessary for the Services.

11.2. The Merchant is responsible for choosing and maintaining lawful arrangements with its Merchant-designated providers and for configuring enabled Services and their data flows appropriately.

11.3. The Merchant shall not submit unnecessary sensitive or special-category information to ePAL and shall notify ePAL in advance if a service requires processing materially outside Schedule A so that the parties can agree appropriate safeguards.

12. General contractual terms

12.1. This DPA forms part of the applicable Terms of Service or separately executed services agreement. In the event of a conflict concerning protection of Merchant Personal Data, this DPA prevails to the extent necessary to comply with Data Protection Laws.

12.2. This DPA does not remove any obligations or liabilities imposed directly on either party by Data Protection Laws. Any commercial liability terms must be interpreted consistently with applicable law.

12.3. ePAL may propose amendments to reflect changes in law or the Services, subject to contractual notice and agreement mechanisms. Material changes to processing instructions, Sub-processor arrangements or retention schedules must not be treated as retrospectively authorised solely by updating a webpage.

12.4. This DPA is governed by Irish law, subject to mandatory applicable data protection law. The competent Irish courts shall have jurisdiction to the extent permitted by law.

Schedule A: description of processing

A1. Subject matter, nature and duration

Processing of Merchant Personal Data to provide enabled cross-border eCommerce, checkout, shipping, regulatory screening, fulfilment, reporting and compliance evidence services. Processing continues for the duration of the Services and any lawful, authorised retention period subject to Section 9.

A2. Categories of data subjects

Shoppers, purchasers, consignees, delivery recipients, Merchant personnel and authorised business contacts, where their details form part of the agreed workflow.

A3. Categories of personal data

Where required by an enabled service: recipient name, delivery address, destination country, relevant contact details, shipment or order identifiers, transaction values and order information, recipient information needed for sanctions checks, screening inputs and results, relevant timestamps, audit trails and authorised account-user details. Product codes, descriptions and aggregate calculation data are not necessarily Personal Data unless linked to an identifiable person.

A4. Operations and purposes

Receiving, accessing, transmitting, consulting, calculating, validating, storing, retrieving, disclosing to authorised providers, reporting, auditing, returning and deleting data for configured services. Shopify order access should be restricted to fields needed for enabled ePAL functions. ePAL does not receive a blanket right to exploit incidental customer information for independent analytics or marketing.

A5. Controller instructions

Instructions comprise accepted services terms and this DPA, selected integrations, configured checks, the agreed retention schedule and subsequent documented lawful instructions.

Schedule B: standard retention schedule

The applicable standard retention periods and triggering events are documented in ePAL’s Data Retention Schedule, incorporated by reference to the extent agreed for the Merchant’s enabled services.

Record categoryPurposeRetention arrangements
Recipient details and sanctions screening inputsEvidence supporting the Merchant's screening obligationsAs specified in the applicable ePAL Data Retention Schedule
Sanctions screening outcomes, timestamps and decision evidenceDemonstrate checks undertaken and support later enquiriesAs specified in the applicable ePAL Data Retention Schedule
Order, customs and transaction audit records containing personal dataAudit, reporting, reconciliation and merchant supportAs specified in the applicable ePAL Data Retention Schedule
Integration request and operational logs containing personal dataDiagnostics, system security and traceabilityAs specified in the applicable ePAL Data Retention Schedule
Backups containing Merchant Personal DataDisaster recovery, subject to access restrictionsAs specified in the applicable ePAL Data Retention Schedule

Applicable retention periods and their triggering events are set out in ePAL’s Data Retention Schedule, as agreed with the Merchant. The Merchant’s end-of-service rights in Section 9 apply regardless of the standard schedule.

Schedule C: third-party providers

C1. Merchant-designated integrations

Where the Merchant connects an existing third-party account or service, ePAL may exchange the information necessary to deliver that integration as instructed by the Merchant. Such providers are not automatically ePAL Sub-processors; their legal role depends on the actual arrangements.

C2. ePAL-appointed Sub-processors

Depending on the Services agreed or enabled for the individual Merchant, ePAL may engage Sub-processors for hosting and infrastructure, regulatory or sanctions screening, technical integrations and other specialist functions. Not every category, provider or activity applies to every Merchant. Processing is limited to the purposes and data necessary for the relevant agreed Service.

C3. Identification and changes

ePAL shall make available a current Sub-processor list identifying the relevant providers and their functions, with processing locations and international transfer safeguards where applicable. The list may be maintained separately from this DPA so it can be updated without rewriting the agreement. Additions and replacements are subject to the advance notice and objection mechanism in Section 4. Merchant-specific arrangements may be recorded in enabled-service configurations, an order form or other documented instructions.

Schedule D: technical and organisational security measures

ePAL shall document and maintain measures appropriate to the risks, including as applicable:

Acceptance and contact

This DPA forms part of the applicable merchant agreement when incorporated into the Terms of Service or otherwise accepted through the designated registration, onboarding or contractual mechanism. ePAL records the Merchant account, agreement version, date and method of acceptance.

Data protection enquiries and requests under this DPA can be directed to epal@epalglobal.com.