Data Processing Agreement

Last updated: 13 November 2026

This is the Article 28 GDPR contract between your business (the controller) and LoyalMT (the processor). It applies automatically to every account — you do not need to request it, sign it or negotiate it — and it forms part of the Terms of Service.

1. Parties and status

This Data Processing Agreement (the “DPA”) is entered into between:

  • The Controller — the business that holds a LoyalMT account (referred to as “you”); and
  • The Processor — LoyalMT, a trading name of Roden Muscat (sole trader), Malta, VAT MT 3003-3731 (referred to as “we”, “us” or “LoyalMT”).

Registered address: Address supplied on request. Registration: Sole trader — no company registration number separate from the VAT number.

This DPA is already in force — there is nothing to sign

By creating or continuing to use a LoyalMT account you accept this DPA, and it is incorporated into the Terms of Service. It applies to free accounts, trials and paid plans alike, from the moment the account exists.

We take this approach because Article 28(3) requires processing to be governed by a contract. A DPA that only exists for customers who request one leaves everyone else processing personal data with no Article 28 contract in place — which would put both of us in breach. If your organisation needs a counter-signed copy for its own records, email hello@loyalmt.com and we will sign and return one.

2. Definitions

“Data Protection Law” means Regulation (EU) 2016/679 (the “GDPR”), the Maltese Data Protection Act (Chapter 586), the Processing of Personal Data (Electronic Communications Sector) Regulations (S.L. 586.01) and any other applicable data protection or privacy legislation, each as amended.

“Controller”, “Processor”, “Data Subject”, “Personal Data”, “Personal Data Breach”, “Processing”, “Special Categories of Personal Data” and “Supervisory Authority” have the meanings given in the GDPR.

“Customer Personal Data” means Personal Data that we Process on your behalf through the Service — principally the personal data of your end-customers, guests, patients, clients, staff and contacts.

“Sub-processor” means any processor we engage to Process Customer Personal Data on our behalf.

“Service” has the meaning given in the Terms of Service.

3. Roles of the parties

For Customer Personal Data, you are the Controller and we are the Processor. You determine the purposes and means of the processing; we act only on your instructions and as set out in this DPA.

Separately, we act as a Controller in our own right for the personal data of the individual who administers your account, for our billing records, for our security and audit logs, and for our own marketing to businesses. That processing is not governed by this DPA — it is described in the Privacy Policy. The GDPR page contains a table allocating roles activity by activity.

Where you are jointly responsible with another party

If you use a LoyalMT integration with a third-party platform you control (for example a POS, a booking engine or a delivery marketplace), that platform’s provider is a separate processor or controller under its own contract with you. We are not responsible for its processing, and it is not our sub-processor.

4. Scope and subject matter of the processing

The subject-matter, duration, nature and purpose of the processing, the types of Personal Data and the categories of Data Subject are set out in Annex I below. We Process Customer Personal Data only:

  1. to provide, maintain and support the Service in accordance with the Terms;
  2. in accordance with your documented instructions, including your use of the Service’s own settings and features (which constitute instructions);
  3. as described in this DPA and its Annexes; and
  4. where required by Union or Maltese law, in which case we will inform you before processing unless that law prohibits us from doing so.

We will not Process Customer Personal Data for our own purposes. In particular, we do not sell Customer Personal Data, we do not use it to build advertising or marketing profiles, we do not market to your end-customers, and we do not combine the end-customer lists of different businesses into any shared or cross-business database.

If we believe an instruction from you infringes Data Protection Law, we will tell you promptly and may suspend the affected processing until the instruction is withdrawn, amended or confirmed.

5. Your obligations as Controller

You are responsible for the lawfulness of the data you put into the Service and of the instructions you give us. Specifically, you warrant and undertake that:

  • you have a valid lawful basis under Article 6 for every category of processing you carry out through the Service, and a valid Article 9 condition for any Special Categories of Personal Data;
  • you have provided the Data Subjects with the information required by Articles 13 and 14, including the identity of your business as controller and a privacy notice of your own — linking to the LoyalMT Privacy Policy is not a substitute for yours;
  • where you rely on consent, that consent was freely given, specific, informed and unambiguous, that you can evidence it, and that it has not been withdrawn;
  • any contact list you import was lawfully collected and the individuals have not objected to or withdrawn consent for the processing you intend;
  • you will not use the Service to send direct marketing in breach of the ePrivacy rules or S.L. 586.01;
  • you have assessed whether any of your processing requires a Data Protection Impact Assessment under Article 35, and carried one out where it does; and
  • you will respond to Data Subject requests relating to Customer Personal Data as the controller, using the tools we provide.

Special category data deserves particular attention

Several parts of the Service can be configured to collect data that falls within Article 9 — intake and consultation forms, treatment or medical notes, before-and-after photos, accessibility requirements, and allergen or dietary information linked to a named person. The Service does not stop you collecting that data, and we do not inspect what you put into a form field.

If you collect it, you are the controller of it, you need an Article 9 condition (explicit consent under Article 9(2)(a) is the usual one in a hospitality or wellness setting), and you are likely to need a DPIA. Please read Section 13 of the Terms of Service before switching these features on.

6. Confidentiality and personnel

We will keep Customer Personal Data confidential and will ensure that any person we authorise to Process it:

  • is subject to a binding duty of confidentiality that survives the end of their engagement;
  • Processes it only to the extent necessary for their role (least privilege);
  • has received appropriate data protection and security guidance; and
  • has their access removed promptly when it is no longer required.

Access to production data is limited to the minimum number of people needed to operate and support the Service, and is used for support, debugging, security and legal-compliance purposes only.

7. Security measures (Article 32)

We implement appropriate technical and organisational measures to protect Customer Personal Data against accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access. The measures in force are described in Annex II.

We may update those measures as the Service and the threat landscape evolve, provided we do not materially reduce the overall level of protection.

What we do not claim

We do not hold an ISO/IEC 27001 certification or a SOC 2 report, and we do not claim compliance with PCI DSS beyond what applies to us as a merchant that never touches card data. We would rather state that plainly than let a procurement questionnaire be answered by implication. Card payments are handled entirely by Stripe and Viva.com, both of which are PCI DSS Level 1 service providers; card numbers are never transmitted to or stored on our systems.

8. Sub-processors

You give us general written authorisation to engage Sub-processors for the purpose of providing the Service. The current list is maintained at loyalmt.com/subprocessors, which forms Annex III to this DPA.

In respect of each Sub-processor we will:

  1. carry out proportionate due diligence before engaging it;
  2. impose data protection obligations by written contract that are no less protective than those in this DPA, as required by Article 28(4);
  3. remain fully liable to you for the Sub-processor’s performance of its data protection obligations; and
  4. ensure a valid Chapter V transfer mechanism is in place where the Sub-processor Processes Customer Personal Data outside the EEA.

Notice of changes and your right to object

We will give you at least 30 days’ notice before adding or replacing a Sub-processor that Processes Customer Personal Data. Notice is given by updating the sub-processor page and by emailing the account’s registered address. You can also subscribe to change notices from that page.

You may object within those 30 days on reasonable data protection grounds, by emailing hello@loyalmt.com and explaining the grounds. We will work with you in good faith to find an alternative. If no reasonable alternative exists, you may terminate the affected part of the Service without penalty and we will refund any fees you have prepaid for the unused remainder of the term on a pro-rata basis. Continuing to use the Service after the notice period without objecting constitutes approval.

An urgent replacement needed to maintain security or service continuity may be made with shorter notice, in which case we will notify you as soon as reasonably possible afterwards and your objection right still applies.

9. International transfers

Customer Personal Data is stored in the European Union. Some Sub-processors Process it outside the EEA — principally in the United States — in which case we rely on one or more of:

  • an adequacy decision under Article 45, including the EU–US Data Privacy Framework where the recipient is certified;
  • the European Commission’s Standard Contractual Clauses under Article 46(2)(c), supplemented by a transfer impact assessment and additional measures where needed; or
  • another lawful mechanism under Chapter V.

The transfer basis for each Sub-processor is stated on the sub-processor page. Where we act as data exporter and you as data importer, or vice versa, the SCCs are incorporated into this DPA by reference, with Module Two (controller to processor) applying and the governing law and forum being Malta.

If you instruct us to send Customer Personal Data to a destination of your choosing — for example by connecting an integration, exporting a file or configuring a webhook — you are the exporter for that transfer and responsible for its lawfulness.

10. Assisting you with data subject requests

The Service gives you direct access to Customer Personal Data so that you can respond to Data Subject requests yourself: you can search, view, correct, export and delete end-customer records from your dashboard, and export data in a structured, commonly used, machine-readable format.

If a request cannot be satisfied with those tools, we will provide reasonable assistance within the scope of the processing and the information available to us. Contact hello@loyalmt.com. We will respond substantively within 5 working days and complete reasonable assistance within 15 working days, so that you can meet your own one-month deadline under Article 12(3).

If a Data Subject approaches us directly about data we Process on your behalf, we will not respond to the substance of the request. We will tell them to contact you, and we will forward the request to you without undue delay — unless you have instructed us otherwise in writing.

11. Personal data breach notification

We will notify you of a Personal Data Breach affecting Customer Personal Data without undue delay after becoming aware of it, and in any event within 48 hours.

Why 48 hours and not 72

Article 33(1) gives you, as controller, 72 hours to notify the supervisory authority. Article 33(2) requires us, as processor, to notify you without undue delay — with no 72-hour allowance, because a processor that takes 72 hours has consumed your entire window before you even hear about it. The 48-hour outer limit here is a commitment to leave you usable time, not a licence to wait.

Our notification will include, to the extent known at the time:

  • the nature of the breach and when it is believed to have occurred and been detected;
  • the categories and approximate number of Data Subjects and records affected;
  • the likely consequences;
  • the measures taken or proposed to address it and mitigate adverse effects; and
  • a point of contact for further information.

Where we cannot provide all of that at once we will provide it in phases without further undue delay. We will cooperate with you and take the steps you reasonably request to assist your investigation and your notifications to the supervisory authority and to Data Subjects.

Notification is not an admission of fault or liability by either party. We will not notify a supervisory authority or Data Subjects about a breach of Customer Personal Data on your behalf unless you ask us to in writing — that duty is yours as controller.

12. Audit and information rights (Article 28(3)(h))

We will make available to you the information reasonably necessary to demonstrate our compliance with this DPA, and will allow for and contribute to audits.

In practice, the first line of response is documentary: this DPA, the GDPR page, the sub-processor register, Annex II, and written answers to your security or data protection questionnaire. We will respond to a reasonable questionnaire within 30 days.

If documentation genuinely does not satisfy a requirement you are under, you may request an audit on 30 days’ written notice, no more than once in any 12-month period (unless a Personal Data Breach or a supervisory authority requires otherwise). An audit must be conducted during business hours, must not unreasonably disrupt the Service, must be subject to confidentiality, and must not involve access to data belonging to other customers or to our infrastructure in a way that would compromise its security. You bear your own costs; we may charge for our reasonable time where the audit goes beyond providing documentation.

13. Assistance with DPIAs and consultation

Taking into account the nature of the processing and the information available to us, we will provide reasonable assistance with:

  • your Data Protection Impact Assessments under Article 35; and
  • prior consultation with a supervisory authority under Article 36.

We maintain descriptions of how the relevant features work — notably the wallet proximity mechanism, the AI-assisted features and the messaging channels — specifically so that they can be dropped into your own DPIA. Request them from hello@loyalmt.com.

14. Return and deletion

On termination or expiry of your account, and at your choice, we will delete or return Customer Personal Data and delete existing copies, unless Union or Maltese law requires continued storage.

In practical terms:

  • your data remains available for export for 30 days after termination;
  • after that window we delete Customer Personal Data from active production systems within 90 days of termination;
  • encrypted backups age out on their own rotation and are fully expired within 12 months; and
  • we may retain records we are independently required to keep — for example invoices and VAT records, which Maltese tax law requires us to keep for longer — and anonymised or aggregated data that can no longer identify a Data Subject.

On written request we will provide confirmation that deletion has taken place.

15. Liability, precedence and term

Each party’s liability under this DPA is subject to the limitations and exclusions of liability in the Terms of Service, except to the extent Data Protection Law does not permit those limitations to apply. Nothing in this DPA limits a Data Subject’s rights under Article 82.

If there is a conflict between this DPA and the Terms of Service on a data protection matter, this DPA prevails. If there is a conflict between this DPA and the Standard Contractual Clauses, the SCCs prevail.

This DPA takes effect when your account is created and continues for as long as we Process Customer Personal Data, and thereafter for so long as any obligation in it remains outstanding. It is governed by the laws of Malta, with the courts of Malta having jurisdiction, as set out in the Terms of Service.

We may update this DPA to reflect changes in law, guidance from supervisory authorities, or changes to the Service. Material changes will be notified at least 30 days in advance to the account’s registered email address.

Annex I — Description of the processing

Subject matter and duration

Subject matter: the provision of the LoyalMT hospitality, loyalty, ordering, booking and operations platform. Duration: the term of your account, plus the retention and deletion periods in Section 14.

Nature and purpose of the processing

Collection, recording, organisation, structuring, storage, retrieval, consultation, use, disclosure to Sub-processors, transmission to the Data Subject, alignment, combination, restriction, erasure and destruction — in each case for the purpose of operating the features you have enabled: loyalty and stamp cards, digital wallet passes, QR and WhatsApp ordering, menus, table and venue reservations, appointments, event ticketing, accommodation bookings, payments, forms and intake, transactional and marketing messaging, reviews and feedback, warranties and receipts, vouchers and gift cards, staff and rostering records, reporting and analytics, and support.

Categories of Data Subject

  • Your end-customers, guests, diners, patients and clients, including loyalty members and holders of wallet passes
  • People who order, book, reserve or buy a ticket without joining a loyalty programme
  • Recipients of your marketing or transactional messages
  • Your staff users and the people named in your rostering and operations records
  • Your business contacts, suppliers and any other individuals whose data you choose to enter

Types of Personal Data

CategoryExamples
Identity and contactName, email address, mobile number, preferred language, and date of birth where you collect it
Loyalty and membershipMembership and card identifiers, stamp and point balances, tier, stored-value balance, redemption history, referral links
Transaction and orderOrder and basket contents, table or room number, amounts, currency, timestamps, tips, payment status, payment-provider reference and card brand plus last four digits (no full card number)
Booking and appointmentDate, time, party size, service or treatment selected, assigned staff member, status, arrival and no-show records, notes you add
AccommodationStay dates, room and rate, guest names, requests, and any identity details you record for guest registration
Free-text and form contentAnything a Data Subject or your staff types into a form, note, request or review field
ImagesPhotos uploaded to a booking, appointment, form, review, warranty claim or menu import, and receipt images submitted for scanning
CommunicationsEmail, SMS and WhatsApp message content and metadata, delivery and failure status, opens and clicks where tracked, push subscription tokens
Consent and preferenceMarketing consent state and timestamp, unsubscribe and objection records, notification preferences, language preference
Device and technicalIP address, user agent, session identifiers, wallet device registration tokens, timestamps and security logs
Staff and operationalStaff name, role, contact details, PIN or login credentials, shift and rota records, hours worked, performance and sales attribution
Staff clock-in verification (only if you enable it)Device coordinates and reported accuracy captured at clock-in and clock-out, whether the punch fell inside the job-site radius, and a photograph taken at clock-in or clock-out. Captured only at the moment of each punch, and only where you switch geofenced or photo clock-in on. This is employee monitoring data: you are the Controller and the employer, and the lawful basis, staff notice, proportionality assessment and any worker-consultation duty are yours.
Special categories (only if you enable and collect them)Health, medical, treatment or dietary information; allergen details tied to a named person; accessibility requirements; before-and-after or clinical photographs

We do not process device location data relating to Data Subjects. Section 9 of the Privacy Policy explains why wallet proximity notifications do not involve any location data reaching us or you.

Frequency and sensitivity

Processing is continuous for the duration of the account. Special Categories of Personal Data are processed only where you choose to collect them through configurable features, as described in Section 5.

Annex II — Technical and organisational security measures

MeasureImplementation
Encryption in transitTLS 1.2 or higher enforced for all connections to the Service, its APIs and its database. HTTP Strict Transport Security is enabled.
Encryption at restDatabase volumes, object storage and backups are encrypted at rest by the hosting and database providers.
Access control — tenant isolationRow Level Security policies in the database scope every query to the owning business, so one account cannot read another account’s records even if an application-layer check were missed.
Access control — usersAuthenticated sessions with role-based permissions for owner, manager and staff roles; short-lived tokens; re-authentication required for destructive account actions.
Access control — our personnelLeast-privilege administrative access limited to the minimum number of people needed to operate and support the Service, under a binding duty of confidentiality, revoked promptly when no longer needed.
Secret managementCredentials, API keys and signing certificates held in the hosting provider’s encrypted environment store, never in source control, rotated on compromise or personnel change.
Payment dataCard details are collected and processed entirely by Stripe and Viva.com in their own hosted fields. Full card numbers never reach our systems; we retain only tokens, brand and last four digits.
PseudonymisationWallet passes, loyalty cards and public links reference opaque identifiers rather than personal details, so a scanned or shared link does not itself disclose identity.
Input handlingServer-side validation and parameterised queries; uploaded files constrained by type and size and served from isolated storage.
Rate limiting and abuse controlsRequest throttling on authentication, messaging, export and public endpoints to limit enumeration, scraping and abuse.
Logging and monitoringApplication, access and error logging with alerting on anomalies; audit records for sensitive administrative actions.
Backups and resilienceAutomated encrypted database backups with point-in-time recovery, held on the provider’s rotation and expiring within 12 months; managed, redundant hosting.
Change managementVersion-controlled source, reviewed changes, staged deployments with the ability to roll back.
Data minimisation by designFeatures are built to avoid collecting data that is not needed — most notably, no device location is requested or stored, and no proximity result is reported back from a customer’s phone.
DeletionPer-record deletion available from the dashboard; account-level deletion and export endpoints; documented post-termination deletion schedule.
Incident responseDocumented breach assessment and notification procedure with the 48-hour commitment in Section 11.
Sub-processor assuranceDue diligence before engagement, Article 28(4) contractual terms, Chapter V transfer mechanisms, and a public versioned register.

Measures are kept under review and may be strengthened or replaced; we will not materially reduce the overall level of protection. We do not currently hold ISO/IEC 27001 certification or a SOC 2 report.

Annex III — Sub-processors

The authorised Sub-processors, the service each provides, its processing location and the applicable Chapter V transfer mechanism are listed at loyalmt.com/subprocessors. That page is versioned and dated, and is incorporated into this DPA as Annex III. The notice and objection procedure in Section 8 applies to every change to it.

Contact

Data protection, DPA, contractual and legal queries: hello@loyalmt.com
LoyalMT, Address supplied on request, Malta

We have not appointed a Data Protection Officer. Our processing does not meet the Article 37 thresholds that would require one, and we say so rather than name a role that does not exist. The address above reaches the person responsible for data protection.

Revision history

  • 13 November 2026 — First published. Previously, a data processing agreement was offered “on request” to paid plans only; it now applies automatically to every account and is incorporated into the Terms of Service. Adds the Article 28(3) annexes, the 30-day sub-processor notice and objection right, the 48-hour breach notification commitment, and explicit statements of what we do not certify.