1. Who we are and what this policy covers
ePAL Global Limited (ePAL, we, us or our) provides cross-border calculation and related services to merchants and integration partners. This policy covers our public website, ePAL portal, WooCommerce integration, ePAL Basic for Shopify and direct API services. It explains the personal data we handle, why we handle it, how long we keep it and how to exercise privacy rights.
No. 1 Charlotte Quay
Limerick
Ireland
V94 TW5E
Privacy enquiries: epal@epalglobal.com
This policy applies to personal data. Removing a name does not necessarily stop a record from being personal data: order references, addresses and pseudonymous identifiers may still relate to an identifiable person.
2. Our role and the merchant’s role
We act as a data controller when deciding how to use personal data for our own website, business contacts, merchant-account administration, ePAL billing, support, security and legal obligations.
For buyer and order information processed to provide services on a merchant’s behalf, the merchant normally acts as controller and ePAL acts as data processor under the merchant’s documented instructions and the applicable Data Processing Agreement. Those instructions include any agreed continuing calculation and transaction-evidence service. The merchant determines the purposes and lawful basis for collecting buyer information and explains its own processing in its privacy notice.
The purpose of processing determines our role. Where we must retain particular records to meet ePAL’s own legal obligations or handle legal claims, we assess that purpose separately rather than treating every merchant order as our own business data.
3. Information we receive
We receive information directly from merchants, account users and people who contact us; from connected stores and APIs on the merchant’s instructions; and from providers used to deliver the requested service.
Merchant, account and support information
This includes names, business contact details, company and VAT information, business and dispatch addresses, account permissions, store identifiers, connection settings, authentication information and communications with ePAL support. Billing records include ePAL charges, subscriptions, usage counts, invoices, adjustments and payment status.
Buyer, order and calculation information
Depending on the integration and service enabled, this includes order and product references, descriptions, classifications, quantities, values, currency, discounts, origin and destination, shipping details, calculated taxes and duties, relevant compliance inputs, results and subsequent corrections or validation events. WooCommerce and API services can also receive buyer names, contact details and delivery addresses where needed to identify buyers, determine the destination or provide merchant-selected services.
Recipient sanctions checks where enabled
Some ePAL implementations include checking an order’s recipient against sanctions and related restrictions through downstream screening services. For an enabled check, we process and send only the recipient identity, address and other details needed by that service. We receive the screening result and retain the necessary recipient details and supporting evidence to show who was checked, when the check was made and what result was returned. This supports the merchant’s compliance audit and its response to enquiries, disputes or challenges. The applicable retention rules are explained in section 7.
ePAL Basic for Shopify
ePAL Basic uses product, Market, pricing and order information for its Shopify functionality, including reporting and ePAL usage or charge verification. Order information includes the amounts, taxes, duties, destination country and references needed for those functions.
Buyer details can be present incidentally in an order response even when ePAL does not need them. Accessing those details is still processing personal data. We limit requested fields to what the enabled functionality needs and exclude unnecessary fields where the platform permits. Incidental buyer names, email addresses, phone numbers and full addresses are not used for marketing or retained, logged or forwarded merely because they appear in an order response.
Where recipient sanctions checks are enabled for a Shopify integration, the screening and audit processing described in this policy applies. We explain the relevant processing and obtain any required merchant authorisation and platform permissions before enabling the service.
Website and technical information
Website and service operation can generate IP addresses, browser or device information, access times, authentication events, error and security records, and cookie preferences. Non-essential website cookies are subject to your choices as explained below.
We do not process the buyer’s payment for goods or hold their payment-card details. Shopify or other payment providers handle payments through their own services. Information needed to administer payment of ePAL’s own fees is separate from the buyer’s checkout payment.
4. Why we use information and our lawful bases
We use the minimum information needed for the relevant purpose. For processing where ePAL is controller, the lawful basis depends on the activity:
| Purpose | Lawful basis |
|---|---|
| Accounts and service administration | Performance of a contract where the individual is our contracting customer; otherwise our legitimate interest in managing the business relationship and enabling authorised users to use the service. |
| Enquiries and support | Steps requested before entering a contract, performance of that contract where applicable, or our legitimate interest in responding to business contacts and resolving service issues. |
| ePAL fees and financial records | Performance of the applicable contract, compliance with accounting and tax obligations, and our legitimate interest in verifying charges and resolving billing disputes. |
| Security and service integrity | Our legitimate interests in protecting accounts and information, detecting misuse, investigating faults and maintaining a reliable service, together with applicable legal security obligations. |
| Legal and privacy accountability | Compliance with applicable law; our legitimate interest in establishing, exercising or defending legal claims where necessary. |
| Optional website technologies | Consent for non-essential cookies and similar technologies where required. Essential technologies are used only where needed for the requested function. |
Where we rely on legitimate interests, we consider necessity and the effect on the individual’s rights. You can object as described in section 10. Where we process buyer or order data as processor, we follow the merchant’s lawful instructions; the merchant is responsible for its own lawful basis.
Where recipient screening is enabled, our processing on the merchant’s behalf includes the required provider checks and the agreed retention and retrieval of necessary screening evidence. These are specific service and audit purposes; they do not authorise unrelated use of recipient information.
Information required to operate an account, connect a store or perform a calculation must be supplied for that function to work. Optional information and non-essential cookies are not a condition of using unrelated functions. Acknowledging this privacy policy or accepting service terms does not provide blanket consent for all processing.
We do not sell personal data. Merchant or buyer service data is not reused for advertising, secondary marketing, unrelated product analytics or AI-model training. Real customer data is not sent to AI providers.
5. Who receives information
Access and disclosure are limited to what is needed for the service or another lawful purpose. Recipients can include:
- Hosting and infrastructure providers operating the systems, storage and communications needed to deliver ePAL.
- Tax, customs and shipping providers where needed for the merchant’s enabled services. Merchants can select or integrate optional providers; buyer data is sent to those providers only where needed for the requested function.
- Sanctions and restrictions screening providers receiving the recipient details needed to carry out an enabled check and return its result. This sharing applies only to implementations and services that include recipient screening.
- The merchant and authorised account users entitled to the relevant store’s information, reports and retained evidence.
- Shopify and other connected platforms where needed to operate the integration, publish requested changes, administer ePAL billing or fulfil platform privacy requests.
- Providers administering ePAL’s own fees and professional advisers where necessary for billing, accounting, legal advice or claims.
- Public authorities where disclosure is required by law or is part of a service the merchant has authorised, subject to the applicable legal requirements.
ePAL handles its own support. Staff access is limited to authorised work. Providers acting as processors are subject to contractual data-protection requirements. A merchant-selected provider may instead act as an independent controller under its own terms and privacy notice; its role and the requested service determine its responsibilities.
Where ePAL processes information on a merchant’s behalf, the Data Processing Agreement sets out the applicable provider-sharing safeguards. Contact us for information about the providers relevant to your service and their processing roles.
6. International processing
Cross-border services can involve providers or authorised access outside the European Economic Area. We do not treat a connection to an overseas destination as permission for unrestricted transfers of personal data.
Where an international transfer is subject to GDPR restrictions, we require an applicable lawful transfer mechanism, such as a relevant European Commission adequacy decision or approved Standard Contractual Clauses. Where required, we assess the destination and add safeguards before permitting the transfer. A provider or location is not approved simply because it is technically available.
You can ask epal@epalglobal.com which processing locations and safeguards apply to your information and request a copy or explanation of the relevant safeguards, with confidential details protected where necessary.
7. How long we keep information
Our default is six years for necessary substantive business, transaction, calculation, financial and supporting audit evidence. This does not mean every personal field or original request is kept for six years. We remove unnecessary information earlier and use a different period or start event where an applicable legal requirement governs the record. This policy does not replace a merchant’s own statutory record-keeping duties. For processing on a merchant’s behalf, the Data Processing Agreement also governs retention, return and deletion.
| Record | Retention and treatment |
|---|---|
| Transaction and calculation evidence | Normally six years from the transaction for the inputs, original result, applied rules and linked evidence needed to explain calculations or charges. Necessary customs, shipping and amendment evidence follows the relevant transaction or applicable statutory trigger. |
| Recipient screening and audit evidence | Where screening is enabled, normally six years from the relevant transaction, subject to an applicable legal trigger, valid earlier deletion or a justified hold. Keep the recipient details needed to establish who was screened, the check date, provider and result references, the original result and necessary review or follow-up evidence supplied to ePAL. Keep readable identity details only for as long as they are necessary to substantiate the check; remove or pseudonymise them earlier where the audit purpose can still be met. |
| Readable buyer identifiers | Pseudonymise eligible identifiers one year after the last substantive activity on the relevant order, such as a requested calculation, fulfilment revalidation or correction. Delete fields earlier when no purpose remains. Keep necessary readable destination or legal evidence, or a narrowly justified active-case subset, under its applicable rule. |
| ePAL financial and billing records | Normally six years, measured using the relevant transaction, entry or accounting-period trigger required for the record. Keep only the merchant and order detail needed to support the financial record. |
| Merchant accounts and configuration | Keep the minimum information needed during active service. Necessary relationship and configuration-history evidence is normally kept for six years after the relevant service ends. Revoke access and remove unnecessary credentials, sessions and operational copies earlier. |
| Agreements and privacy requests | Keep minimal accepted-version and agreement evidence during the agreement and for six years after termination; keep necessary privacy-request outcome evidence for six years after case closure. Remove identity-verification copies when verification is complete unless a separate reason requires retention. |
| Support and substantive incidents | Keep the minimum necessary service, dispute or incident evidence for six years from substantive case closure or the relevant event. Remove unnecessary attachments, buyer details and duplicate communications earlier. |
| Abandoned quotes and website enquiries | Remove personal payloads when their purpose ends. A minimal record is kept for six years only where a continuing service, contractual or dispute-evidence purpose justifies it; abandoned data does not automatically become a financial record. |
| Routine technical and debug logs | Delete after 90 days from original creation. Keep a necessary, specifically identified incident-evidence subset longer only under a documented justification. Authoritative transaction evidence is held separately. |
| Consent and record-management evidence | Keep minimal necessary consent evidence for six years after the choice is replaced or withdrawn, and minimal record-management evidence for six years from the action or completion; necessary hold evidence runs from release. Cookie and browser-identifier lifetimes are separate and are not automatically six years. |
| Backups and recovery copies | Use bounded recovery histories based on the information and failures they need to cover. Required evidence remains recoverable throughout its lawful retention, without keeping every snapshot for six years. Copies expire when no longer needed for recovery and are subject to the restoration safeguards below. |
Pseudonymisation
Where a buyer-linked reference remains necessary, we replace eligible readable identifiers with a repeatable one-way reference and remove the replaced originals. References are scoped to an individual store or equivalent API source, so different stores do not share a global buyer identifier, including stores owned by the same merchant. Pseudonymisation is not anonymisation: linkable references remain protected personal data and are still subject to rights requests and expiry.
Eligibility for pseudonymisation depends on the evidence purpose. Where a readable recipient identity remains necessary to substantiate a sanctions check, we document that need and retain only the required details under the screening-evidence rule rather than automatically removing them at the one-year point. This exception is reviewed and does not extend to unrelated buyer fields or override valid deletion requirements.
Neither viewing a record nor copying it, running routine checks, retrying processing or restoring a backup restarts its retention period. Pseudonymising buyer identifiers does not restart the six-year audit period.
Exceptions and periodic removal
Valid erasure requests, platform privacy requirements and the end of a processing purpose can require earlier action. Where law or a necessary active dispute or investigation requires longer retention, we restrict it to the relevant records and purpose, document the reason and review it. When the exception ends, we apply the original due date rather than grant a new retention period.
We evaluate approved retention rules daily and complete due actions within 24 hours of their due time, or sooner where an earlier legal or platform deadline applies. We monitor failures and overdue actions. A justified hold or restricted retained record is not treated as permission to keep unrelated personal data.
8. Disconnection, uninstall and retained evidence
Disconnecting a store or uninstalling an integration ends the relevant operational access. It does not necessarily close an ePAL account used by other stores or integrations. We keep store boundaries separate when processing removal requests.
Calculation and transaction-evidence retrieval is part of ePAL’s service for the applicable six-year retention period, including after disconnection. An authorised merchant can request retained evidence from ePAL without reconnecting the store. We verify the requester’s authority; we do not preserve revoked store credentials for this purpose.
This continuing service is subject to lawful processing instructions, minimisation, valid erasure and applicable platform requirements. It does not authorise a blanket six-year copy of buyer data or override Shopify deletion requirements.
For Shopify, we handle platform requests for customer data access, customer deletion and shop-data deletion, including after uninstall. The normal six-year schedule does not postpone those requests. Where particular information must legally be retained, we limit retention to that information and explain the applicable restriction. We apply Shopify’s required privacy-request protections to Shopify data regardless of the individual’s location.
9. Security and recovery
We protect personal data through access restrictions, secure authentication, encryption of data in transit and at rest, protection of necessary credentials and keys, separation of merchant/store information, and monitoring proportionate to the information and service.
These controls include encrypted backups, separation of test and production data, strong staff-password requirements, access logs for personal data, a data loss prevention strategy and a security incident response policy. Access is limited to the staff and services that need the information for authorised work.
Recovery arrangements protect customer, order and operating information across ePAL services while limiting unnecessary duplicate copies. Transaction processing is the first recovery priority. We test recovery and retain the evidence needed to account for transactions ePAL has acknowledged as accepted.
Restoration must respect subsequent deletion, expiry and pseudonymisation decisions before restored information is made available for normal use. Backups must not bring back removed readable identifiers, restart retention periods or revive revoked access. We handle personal-data incidents and required notifications under applicable law and our processing agreements.
10. Privacy rights and requests
Depending on the applicable law and circumstances, you can request access, correction, erasure, restriction, a portable copy of eligible information, or object to processing based on legitimate interests. Where we rely on consent, you can withdraw it without affecting earlier lawful processing. These rights have conditions and exceptions; we explain any applicable restriction rather than assume every request can be refused or must result in immediate deletion.
If you bought from a merchant using ePAL
Start with the merchant you bought from. The merchant normally controls the order data and must assess its own legal retention needs. ePAL assists the merchant in handling requests under its processing instructions; we do not decide on the merchant’s behalf that all order information can be deleted.
You can also contact ePAL. If we hold the information as processor, we route the request to the relevant merchant and assist rather than ignore it. If ePAL acts as controller for the processing concerned, we handle that part ourselves. A merchant’s justification for retaining one record does not automatically justify retaining every field or copy.
If you are a merchant, account user or website contact
Email epal@epalglobal.com. Requests are handled manually. Give enough context to locate the relevant account, store or interaction, but do not send passwords, API secrets or unnecessary identity documents. We request proportionate verification where needed and remove verification copies when no longer required.
We respond without undue delay, normally within one month where GDPR applies. If a lawful extension is necessary, we explain it within the initial period. We comply with any shorter applicable platform deadline; Shopify privacy actions are normally completed within 30 days, subject to a specific legal retention restriction.
You can complain to the Irish Data Protection Commission or another competent supervisory authority, including one in the EEA country where you live, work or believe an infringement occurred. Contacting ePAL first is helpful but is not a condition of making a complaint.
11. Cookies and similar technologies
Our website uses cookies and similar technologies. Essential technologies support requested website or account functions. Non-essential analytics or preference technologies are used only after the required consent and can be rejected through the cookie controls before use.
You can change or withdraw non-essential cookie choices through the website’s cookie controls and can also manage cookies in your browser. Refusing optional cookies does not prevent unrelated essential functions. See our separate Cookie Policy for cookie purposes, providers, lifetimes and controls. Service data is not repurposed for advertising.
12. Automated calculations
ePAL uses automated calculations and rules to produce pricing, tax, duty and related compliance information from merchant-supplied transaction and product data. Merchants use the results in their own sales and fulfilment processes. ePAL does not block transactions or make the merchant’s decision to accept a buyer’s order. Contact the merchant about its own decisions and ePAL about questions concerning our processing.
Where recipient screening is enabled, a downstream screening result informs the merchant’s review. The result does not itself represent an ePAL decision to accept, reject or block an order. Necessary screening evidence is retained as described in section 7.
13. Changes and contact
We update this policy when our services, processing or legal requirements change and show the revision date above. Where required, we provide additional notice of material changes and obtain consent for any new consent-based purpose. Continuing to use ePAL is not treated as consent to processing that legally requires a separate choice.
For questions about this policy, retention, providers, transfer safeguards or your personal data, contact epal@epalglobal.com or write to ePAL Global Limited at the registered address in section 1.