Sub-processors
Last updated: 13 November 2026
These are the third-party providers that may process personal data on our behalf when we provide the Service to your business. This page is Annex III to the Data Processing Agreement, and changing it triggers a 30-day notice period and your right to object.
Register version
Version 2026.11.1, effective 13 November 2026.
To be notified before this register changes, email hello@loyalmt.com with the subject line Subscribe — sub-processor notices and the email address you want notices sent to. We also email the address registered on each account.
How to read this page
A sub-processor is a company we engage to process personal data on our behalf so that we can provide the Service to you. Under Article 28(4) of the GDPR we remain fully responsible to you for each of them, we hold a written data protection contract with each of them, and we are required to tell you before the list changes.
The list is in two parts. The first part applies to every account. The second applies only if you switch on the relevant feature — if you never send an SMS, no SMS provider ever processes your data.
There is then a third section covering platforms you connect yourself. Those are not our sub-processors, and the section explains why that distinction matters to you legally.
Your rights when this list changes
We give at least 30 days’ notice before adding or replacing a sub-processor. You may object on reasonable data protection grounds within that period by emailing hello@loyalmt.com. If we cannot offer a reasonable alternative you may terminate the affected part of the Service without penalty and receive a pro-rata refund of prepaid fees. The full procedure is in Section 8 of the Data Processing Agreement.
Part 1 — Engaged for every account
| Provider | Purpose | Data processed | Location | Transfer basis |
|---|---|---|---|---|
| Vercel Inc. | Application hosting, content delivery, serverless function execution and product analytics | All data transiting the Service; IP address, user agent, request metadata; aggregated page-view analytics | United States (processing), EU edge regions | EU–US Data Privacy Framework and Standard Contractual Clauses |
| Supabase Inc. | Primary database, authentication, file storage and encrypted backups | All Customer Personal Data stored by the Service | European Union (Frankfurt region) | No transfer — data at rest remains in the EU. US-based support access under Standard Contractual Clauses. |
| Stripe Payments Europe, Ltd. / Stripe, Inc. | Subscription billing for your LoyalMT plan, and card payment processing where you use Stripe as your gateway | Business billing contact and VAT details; for end-customer payments: amount, currency, card token, brand and last four digits, email where provided | Ireland and United States | EU–US Data Privacy Framework and Standard Contractual Clauses |
| Resend, Inc. | Transactional email delivery — account emails, order and booking confirmations, wallet pass links, password resets | Recipient name and email address, message subject and body, delivery and bounce status | United States | Standard Contractual Clauses |
| Apple Inc. / Apple Distribution International Ltd. | Apple Wallet pass issuance and delivery, and Apple Push Notification service for pass updates | Pass contents (member name, balance, card identifier, venue coordinates), device registration token | United States and Ireland | EU–US Data Privacy Framework and Standard Contractual Clauses |
| Google Ireland Ltd. / Google LLC | Google Wallet pass issuance and delivery | Pass contents (member name, balance, card identifier, venue coordinates) | Ireland and United States | EU–US Data Privacy Framework and Standard Contractual Clauses |
Apple and Google receive venue addresses — never customer locations
The wallet pass we hand to Apple or Google contains the coordinates of your premises, so that the platform can decide whether to surface the card on a lock screen. It contains nothing about where any customer is.
The proximity comparison happens on the customer’s own device, by Apple’s or Google’s operating system, and the result is never reported back to us, to you, or to anyone else. We have no endpoint that could receive it. Section 9 of the Privacy Policy sets out the mechanism in full.
Apple and Google will process the customer’s device data under their own privacy policies as controllers in their own right once a pass is added to a wallet. That part is their relationship with the customer, not ours.
Part 2 — Engaged only if you enable the feature
| Provider | Enabled by | Purpose | Data processed | Location | Transfer basis |
|---|---|---|---|---|---|
| Viva Payments SA (Viva.com) | Choosing Viva.com as your payment gateway | Card and local payment processing for end-customer orders, bookings and tickets | Amount, currency, payment token, card brand and last four digits, order reference, email where provided | Greece (European Union) | No transfer — processing remains within the EEA |
| Twilio Inc. / Twilio Ireland Ltd. | Enabling SMS or WhatsApp messaging and ordering | Outbound and inbound SMS and WhatsApp delivery, and the WhatsApp ordering conversation | Recipient mobile number, message content, delivery status, conversation history for the ordering flow | United States and Ireland | EU–US Data Privacy Framework and Standard Contractual Clauses |
| Bird (MessageBird B.V.) | SMS sending, where used as the delivery route or fallback | SMS delivery | Recipient mobile number, message content, delivery status | Netherlands (European Union) | No transfer — processing remains within the EEA |
| Google LLC — Gemini API | Using an AI-assisted feature | Reading text and structure out of an uploaded menu photo or document, or out of a receipt image submitted for a loyalty claim | The image or document submitted, and the text extracted from it. Whatever personal data happens to appear in the image is included. | United States | Standard Contractual Clauses. Submissions are not used to train the model. |
| Google Ireland Ltd. — Places and Maps APIs | Using address lookup, venue search or an embedded map | Suggesting and resolving addresses, and rendering map tiles | The search text typed and the approximate area being viewed. No identified customer record is sent. | Ireland and United States | EU–US Data Privacy Framework and Standard Contractual Clauses |
| OpenStreetMap Foundation — Nominatim | Saving a premises address, where this route is used | Converting a street address into coordinates for the venue record | The address text submitted. No customer personal data. | United Kingdom and European Union | UK adequacy decision; EU processing involves no transfer |
Where more than one provider can serve the same function — SMS, for example, or card payments — the one actually used depends on your configuration and on routing. Both are listed so that the register is complete either way.
Part 3 — Integrations you connect yourself (not our sub-processors)
The Service can connect to platforms you already use. When you authorise one of these connections, you are instructing us to exchange data with a provider you have a contract with. That provider is not our sub-processor, and this distinction has real consequences for you:
- the provider processes that data under your agreement with it, not ours, so its terms, its security posture and its transfer mechanisms are the ones that apply;
- you need your own Article 28 contract with it, and you are the controller for the transfer;
- we are not liable under Article 28(4) for its processing, and we cannot answer for its retention, security or breach handling; and
- disconnecting the integration stops further data flowing, but does not delete what it has already received — you have to ask the provider for that.
Platforms currently supported
| Platform | What it is used for |
|---|---|
| Lightspeed | Point-of-sale menu, product and transaction synchronisation |
| Epos Now | Point-of-sale menu, product and transaction synchronisation |
| Shopify | Product catalogue and order synchronisation for retail |
| Wolt | Delivery marketplace menu and order synchronisation |
| Fresha | Appointment and client synchronisation for salon and wellness businesses |
| Bsport | Class, booking and member synchronisation for studios and fitness businesses |
If you connect an integration we have not listed, the same principles apply. Section 17 of the Terms of Service covers integrations in more detail.
What we do not do
- We do not engage advertising networks, data brokers, audience platforms or cross-site tracking providers, and we never have.
- We do not sell or share personal data for anyone else’s commercial purposes.
- We do not use a provider that receives device location data about your end-customers, because no such data exists in the Service to pass on.
- We do not allow a sub-processor to use Customer Personal Data for its own purposes, or to train a model on it.
Due diligence and contracts
Before engaging a sub-processor we assess its security posture, its data protection terms, its processing locations and its transfer mechanism, in proportion to the sensitivity and volume of data involved. Each one is engaged under a written contract containing obligations no less protective than those in our Data Processing Agreement, as Article 28(4) requires. Where processing occurs outside the EEA we put a Chapter V mechanism in place and, where the Standard Contractual Clauses are the basis, carry out a transfer impact assessment.
Occasionally we need to replace a provider urgently to maintain security or keep the Service running. In that case we may act with shorter notice and will tell you as soon as reasonably possible afterwards; your right to object still applies.
Contact
Questions, objections, notice subscriptions and data protection queries: hello@loyalmt.com
LoyalMT, Address supplied on request, Malta
Revision history
- 13 November 2026 (v2026.11.1) — First published as a dedicated register. The previous Privacy Policy listed only four providers (Stripe, Supabase, Vercel and “email providers”), which was materially incomplete: Resend, Twilio, Bird, Viva.com, the Google Gemini API, Google Places and Maps, Nominatim, and the Apple and Google wallet platforms were all in use and unlisted. This register adds them, states the processing location and transfer basis for each, separates always-engaged providers from feature-dependent ones, and distinguishes customer-connected integrations from genuine sub-processors.