Data Processing Agreement (DPA)
DRAFT pending review by UAE counsel · Version 2026-11-09.1 · 9 November 2026
Parties and roles
- Controller: the Customer named in the order, with the registered office stated in the order, contact the e-mail address stated in the order ("Customer").
- Processor: XEPA INTERNATIONAL TRADING FZ-LLC, a Free Zone Limited Liability Company registered with RAKEZ under No. 0000004091239, registered office CWEP4314, Compass Building, Al Shohada Road, Al Hamra Industrial Zone-FZ, Ras Al Khaimah, United Arab Emirates; privacy contact: info@getwafra.com ("XEPA International").
This agreement forms part of the Wafra contract and applies to the personal data that XEPA International processes on behalf of the Customer through the Booking Page (the page with booking calendar built for the Customer), the dashboard and the Modules. It is made under Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data (the "PDPL"); terms such as controller, processor, processing and personal data breach have the meaning given in the PDPL.
1. Subject, duration, nature and purpose
- XEPA International processes the personal data of the Customer's clients and contacts collected through the Booking Page and the dashboard: bookings, any requests from the form, client records, transactional confirmation and reminder e-mails, transactional WhatsApp messages to clients who chose them, clients' replies to WhatsApp messages, notifications to the Customer, the loyalty card if the Customer uses it, and e-mail mailboxes on the Customer's domain when the Customer activates them.
- Nature and purpose: hosting the Booking Page, managing bookings and client records, sending transactional confirmation and reminder messages (by e-mail and, with the client's consent, on WhatsApp), forwarding clients' WhatsApp replies to the Customer by e-mail, running the loyalty card, providing mailboxes, counting visits in aggregate form.
- Duration: for the whole term of the contract and until deletion under §7.
- Details are in Annex I.
2. Documented instructions
- XEPA International processes the data only on the Customer's documented instructions, including transfers outside the United Arab Emirates (§9). Documented instructions are: this agreement, the contract, the configuration of the Booking Page and Modules chosen by the Customer, and written requests sent by e-mail.
- If, in XEPA International's opinion, an instruction infringes the PDPL or other data protection rules, XEPA International informs the Customer at once and may suspend it until the Customer confirms or changes it.
3. Confidentiality
The persons authorised by XEPA International to process the data are bound by confidentiality and access only the data needed for their task.
4. Security
XEPA International applies the technical and organisational measures described in Annex II, appropriate to the risks as required by Article 20 of the PDPL, and updates them in line with the state of the art without reducing their overall level.
5. Sub-processors
- The Customer gives a general written authorisation to use the sub-processors listed in Annex III, published at getwafra.com/sub-processors with its version number.
- XEPA International informs the Customer by e-mail of any addition or replacement at least 30 days in advance. Within that period the Customer may object in writing, giving reasons. If the objection is not resolved, the Customer may terminate the contract with effect from the date of the change; termination gives no right to refunds (No-Refund Policy; art. 11 of the Terms).
- XEPA International imposes on each sub-processor, by written contract, data protection obligations equivalent to those of this agreement and remains fully responsible to the Customer for their performance.
6. Assistance to the Customer
- XEPA International provides tools to export, correct and delete the data of individual data subjects, or carries out these operations on the Customer's written request, and assists the Customer in answering data subjects exercising their rights under the PDPL. If a data subject writes directly to XEPA International, XEPA International forwards the request to the Customer without answering on the merits.
- XEPA International notifies the Customer of any personal data breach as soon as it becomes aware of it and in any case within 48 hours, with the information available at that time (nature and causes, likely effects, measures taken or proposed), and completes it as soon as possible, so that the Customer can notify the competent authority and the data subjects as required by Article 9 of the PDPL.
- XEPA International assists the Customer, as far as it is concerned, with any data protection impact assessment (Article 21 of the PDPL) and with requests from the competent authority.
7. Deletion and return
- When the contract ends, for any reason, the Customer may export the data in CSV or JSON for 30 days (art. 21 of the Terms). XEPA International then deletes them from active systems and, on request, confirms the deletion in writing.
- Backup copies are encrypted and kept for 90 days, then deleted. If a backup is restored, XEPA International re-applies all deletions made after the date of the backup before using the data.
- Any obligation to keep data imposed on XEPA International by applicable law is not affected.
8. Information and audits
XEPA International makes available the information needed to demonstrate compliance with this agreement and allows checks and inspections by the Customer or by an auditor it appoints, bound by confidentiality, with at least 30 days' notice, no more than once a year except after a breach or at the request of an authority, at the Customer's expense.
9. Data location and transfers outside the United Arab Emirates
- The databases and files are stored with providers under EU jurisdiction (Annex I, point B). Storing the data in the European Union is a transfer of personal data outside the United Arab Emirates, which the Customer instructs by entering into this agreement.
- Not all processing takes place in the EU: XEPA International accesses the data from the United Arab Emirates; Cloudflare's network processes requests in transit in the data centre closest to the visitor; some technical logs of providers and some services (for example WhatsApp) may be outside the EU.
- Transfers are made under Articles 22 and 23 of the PDPL: each sub-processor is bound by a written agreement to apply data protection measures at least equivalent to those required by the PDPL and this agreement, and the transfers are necessary to provide the service the Customer has ordered. If the competent UAE authority adopts requirements for transfers, XEPA International applies them and may update this section by written notice to the Customer.
10. Customer obligations
- The Customer determines the lawful basis of the processing under the PDPL, approves the privacy notice of the Booking Page prepared by XEPA International before publication, obtains and records any consents (including consent to WhatsApp messages and any marketing consent through an optional, unticked box) and gives only lawful instructions.
- The Customer does not use Wafra to process health data or other sensitive personal data and does not enter such data in notes or client records. Health businesses are not accepted on Wafra (art. 2.3 of the Terms).
- The Customer uses Wafra's messages only for transactional communications about appointments and complies with the rules of the Telecommunications and Digital Government Regulatory Authority (TDRA) on electronic communications; it does not use Wafra for promotional WhatsApp messages.
11. Precedence, liability and disputes
- In case of conflict with the contract, this agreement prevails.
- Between the parties, liability follows art. 23 of the Terms, to the extent compatible with mandatory provisions of law. The rights of data subjects are not limited.
- Disputes under this agreement follow art. 24 of the Terms.
12. Activity log and platform security
- For the security of the platform as a whole (protection against abuse affecting more than one Customer, locks and unlocks of accounts, sign-in notices to owners, sign-ins of its own support staff) XEPA International acts as an independent controller and informs the data subjects with its own privacy notice for dashboard users. Otherwise the activity log is processed on behalf of the Customer under this agreement.
- XEPA International records the access of its own staff to the Customer's data and keeps those records for 24 months, also after the end of the contract.
- A report «It wasn’t me» on an account of the Customer is treated as a possible personal data breach: XEPA International informs the Customer without undue delay and makes available to it the summary of the reported sign-in.
- An anomaly in the integrity check of the log is shown to the Customer at once (or within 24 hours of a refusal by the independent witness); XEPA International assesses it within 48 hours and tells the Customer the outcome.
- The Customer declares in the dashboard whether there are employees in its team and, if so, whether the employees have agreed to these checks or the employment law that applies to the Customer allows them; the declaration decides what the Customer sees of its staff members' sign-ins and is under its responsibility. The Customer informs its staff members before they start using the dashboard, also with the template that XEPA International makes available in the Documents section, and does not use the log to assess people's performance.
Annex I: Details of processing
A. Parties
- Controller: the Customer, as stated at the top. Activity: managing bookings of its own clients through the Booking Page.
- Processor: XEPA International, as stated at the top; contact info@getwafra.com; Manager Matteo Pedrini. No data protection officer appointed. Activity: building and hosting booking pages with booking calendar (Wafra service).
B. Description of processing
- Data subjects: clients, prospective clients and contacts of the Customer who use the Booking Page; the owner and the staff members of the Customer to whom the Customer gives access to the dashboard; XEPA International staff who work on the Customer's data for support; anyone who tries to sign in to an account of the Customer; persons shown in materials provided by the Customer; correspondents of the Customer's mailboxes.
- Data: name, e-mail, phone, message, service requested, date and time of the booking, answers to form questions, booking notes, notes and tags the Customer enters in the CRM, source of the request (utm or advert), marketing-consent choice with date and text version; loyalty-card stamps and rewards if the Customer uses the loyalty card; images provided by the Customer, which may show people; with mailboxes, the messages and their attachments. No cookies and no stored IP address for counting visits.
- Activity log and sign-ins: for each operation on the Customer's data (changes and viewings: client records, appointments, payments, calendar, lists and searches, of which only the number of results and never the text searched, downloads, exports, domain, mail and billing data, viewings of the log) who, what, when and which data it refers to, never the content of the data; sign-in events of dashboard accounts (code requests, successful and failed sign-ins, sign-outs, sessions, locks and unlocks); network data (prefix of the IP address, network operator, full IP address encrypted, approximate location estimated from the network, type of device and browser); recognised devices; security notices sent; requests refused by the dashboard because of the role or because the data do not belong to the account (area, outcome and number, grouped by 10 minutes). What the Customer sees of its staff members' sign-ins depends on the declaration about the team that the Customer makes in the dashboard (§12.5).
- WhatsApp: only to clients who chose them with the consent on the Booking Page (or whom the Customer marks as consenting on a booking it enters itself), with date, source and version of the consent text; only messages about the appointment (confirmation, reminder, reschedule, cancellation, request received or declined), never promotional. The providers in Annex III receive: phone number, client name, business name, date and time of the appointment, service name and a short link to the appointment page; delivery statuses come back. The client may stop at any time from the link in the messages or by replying STOP on WhatsApp (exclusion list per Customer). A client's reply to a WhatsApp message is forwarded by e-mail only to the Customer it is certainly addressed to and is not stored; to link a reply to the business, XEPA International keeps only a cryptographic hash (HMAC) of the number and of the WhatsApp identifier, for 7 days from the last message or until the day after the appointment if later.
- Sensitive data: none expected; the Customer does not use Wafra for health data (§10.2).
- Frequency: continuous, for the term of the contract.
- Nature and purpose: hosting, collecting requests, bookings, CRM, transactional messages (e-mail and, with consent, WhatsApp), forwarding WhatsApp replies to the Customer, loyalty card, mailboxes, aggregate visit counting.
- Retention: set by the Customer (default: 24 months from the last contact); deletion at the end of the contract after the 30-day export window; encrypted backups for 90 days with re-application of deletions.
- Retention of the log: changes and viewings for the period the Customer chooses among 6, 12, 18 and 24 months (default 12); sign-ins and security outcomes 12 months; if the Customer has not declared that there are no employees in the team, or that the employees have agreed or the applicable employment law allows these checks, staff members' unreported sign-ins and general viewings 21 days and the staff members' name on their other activity 21 days; activity of XEPA International support staff 24 months, also after the end of the contract; network data 90 days (21 for staff members and for failed sign-in attempts); full IP address encrypted 30 days (21 for staff members, 7 for failed attempts); devices 12 months from last use. A deletion reaches every copy within 30 days of expiry. The entries that the Customer or XEPA International freeze for a legal obligation or to establish or defend a legal claim stay until the freeze ends.
- Data location: Cloudflare D1 database under EU jurisdiction (
eu); files on Cloudflare R2 under EU jurisdiction; e-mail through Resend, EU regioneu-west-1(Ireland); encrypted backups on Backblaze B2, EU Central region (Amsterdam); the other providers as stated in Annex III. Cloudflare's network may process requests in transit in the data centre closest to the visitor, and XEPA International accesses the data from the United Arab Emirates (§9). - Transfers to sub-processors: subject, nature and duration as in Annex III, for the term of the contract.
C. Competent authority
The competent data protection authority of the United Arab Emirates.
Annex II: Technical and organisational measures
- Data isolation per customer: every read and write goes through a single function that filters by customer identifier.
- Encryption in transit (TLS) and at rest; end-customer contact data, keys and third-party secrets encrypted with AES-GCM.
- Internal tools protected by Cloudflare Access with multi-factor authentication, in addition to application credentials; support staff do not see contact data in clear.
- Backups encrypted with
age, separated per customer, kept outside the Cloudflare account, with keys held outside Cloudflare; the backup is run from a computer managed by XEPA International, which encrypts the data before sending; restore test twice a year. - Append-only activity log: each entry is linked to the previous one by a hash chain per Customer and by a global chain; the retention class of each entry is in the chain, so a deletion before expiry is visible at verification.
- Identity of the person acting kept separate from the entry, with a cryptographic commitment that allows it to be proved without showing it.
- Hashes of the chains signed several times a day, sent by e-mail and deposited outside the platform by an independent witness, in a write-protected archive in the European Union; a public copy of the daily hashes.
- Integrity check that the Customer can run from the dashboard, with the outcome shown at once, so the log is verifiable; an anomaly raises an alert visible to the Customer.
- Access of support staff only with a reason, recorded and visible to the Customer in its log; double approval for the most sensitive operations.
- Sign-in notice e-mails, account lock with «It wasn’t me», sign-in codes tied to the browser that asked for them, sessions tied to the device.
- Full IP address and export files of the log encrypted.
- In storage without EU jurisdiction (Cloudflare KV), in technical logs and in statistics no names, e-mails, phone numbers or addresses: at most non-reversible cryptographic hashes.
- Booking Page without cookies or tools that store or read information on the device; server-side aggregate visit counting, without IP.
- Data minimisation, retention with automatic deletion, strict input validation.
- Access to data limited to the persons who need it, bound by confidentiality.
Annex III: Sub-processors
Annex III is the list of Sub-processors published on getwafra.com, in the version in force under §5. Each version of the list has its number and date.