Cookie Policy
Last updated: 13 November 2026
This page explains what LoyalMT stores on your device. The short version: we use cookies that are strictly necessary to keep you signed in and to make the site work, and the analytics we use does not set cookies or store an identifier on your device. That is why you are not shown a cookie banner.
1. Why there is no cookie banner here
Under the ePrivacy rules — Article 5(3) of Directive 2002/58/EC, implemented in Malta by the Processing of Personal Data (Electronic Communications Sector) Regulations (S.L. 586.01) — consent is needed before storing information on your device or accessing information already stored there, unless doing so is strictly necessary to provide a service you have asked for.
Everything we store on your device falls into that strictly necessary category. We do not run advertising pixels, tag managers, cross-site trackers, remarketing scripts or social media trackers, and our analytics does not write anything to your device. There is nothing for you to consent to, so we do not interrupt you with a banner asking for consent we do not need.
If that ever changes, the banner comes first
If we ever add anything non-essential that stores or reads information on your device, we will implement a proper consent mechanism — with a genuine reject option, no pre-ticked boxes, and the ability to change your mind — before switching it on, and we will update this page. We would rather commit to that in writing than leave it to good intentions.
2. What a cookie is, and what else counts
A cookie is a small text file a site stores in your browser. The same rules, and this page, also cover the other ways information can be kept on or read from your device: local storage and session storage (similar to cookies but with no expiry rules), and service worker and cache storage (used to make a site load faster or work offline).
Where this page says “cookie”, treat it as covering all of those.
3. Cookies and storage we use
Strictly necessary — set by us
| What it does | Type | How long it lasts |
|---|---|---|
| Keeps you signed in to your account and carries your session between pages, so you do not have to log in again on every click | Authentication cookie (set by our database and authentication provider, Supabase) | Until you sign out, or until the session expires |
| Protects forms and account actions against cross-site request forgery | Security token | The browsing session |
| Remembers an in-progress basket, order or booking so you do not lose it if the page reloads | Local or session storage | Until the order or booking is completed or abandoned |
| Remembers your language or display preference where you have set one | Local storage | Until you clear your browser storage |
| Allows the site to be installed and to load reliably on a phone, including on a slow connection in a venue | Service worker and cache storage | Until updated or cleared |
| Stores the push notification subscription your browser issues, if you have agreed to notifications | Browser push subscription | Until you turn notifications off |
These cannot be switched off through a consent control, because the site cannot do what you asked it to do without them. You can still block or clear them in your browser settings — see Section 6 — but signing in, ordering and booking will stop working.
Analytics — no cookies, no device identifier
We use Vercel Web Analytics, provided by our hosting provider Vercel, to count page views and see which pages are used. We use it because it is designed to be privacy-preserving:
- it does not set cookies;
- it does not store an identifier on your device;
- it does not follow you across other websites;
- it does not build a profile of you;
- it reports in aggregate — page, referrer, approximate country, device type and browser — not as a record about an identified person.
Your IP address is processed transiently in order to derive the approximate country and then to count the visit; it is not retained as part of the analytics record. We rely on our legitimate interest in understanding and improving our own website (Article 6(1)(f)), and because nothing is stored on your device, the ePrivacy consent requirement is not engaged.
A correction to what we used to say
An earlier version of our Privacy Policy said “analytics, if used, are anonymised”. That was vague about a product that was in fact in use throughout, and it named no provider. This page names it, and the Privacy Policy now discloses it properly.
4. Third-party cookies you may encounter
Some cookies in your browser come from providers whose components appear within our pages, and are set on their own domains rather than ours. We do not control them, and they are governed by the provider’s own policy.
| Provider | When it appears | Purpose |
|---|---|---|
| Stripe | On any page with a Stripe payment field, and during Stripe Checkout | Fraud prevention and payment security. Stripe sets these on its own domain inside its payment fields. They are necessary to take a payment safely and to meet card-scheme requirements. |
| Viva.com | During a Viva.com payment or redirect | Payment session and fraud prevention, set by Viva on its own domain. |
| Google Maps | On a page with an embedded map, if your business has enabled one | Map rendering and Google’s own abuse prevention. Where a map is embedded, Google may set cookies when the map loads. |
| Apple / Google Wallet | When you add a loyalty card to your phone wallet | Handled by the wallet app and the operating system, not by a web page. Governed by Apple’s or Google’s own privacy policy once the pass is added. |
None of these is an advertising or cross-site tracking cookie as far as our use of them goes. If you would rather not encounter the payment ones, you can pay in person instead of online.
5. What we do not use
- No advertising or remarketing cookies, and no ad network tags.
- No Google Analytics, no Google Tag Manager, no Meta or TikTok pixel.
- No cross-site or cross-device tracking, and no data brokers or audience platforms.
- No fingerprinting to identify your device.
- No location storage. We never store your location in a cookie or anywhere else — see Section 9 of the Privacy Policy.
We have never sold or shared data from this site for anyone else’s advertising purposes, and we do not intend to.
6. How to control cookies and storage
You can see, block and delete cookies and site storage in your browser’s settings. The relevant sections are normally:
- Safari (iPhone and iPad): Settings › Apps › Safari › Advanced › Website Data. Desktop: Safari › Settings › Privacy.
- Chrome: Settings › Privacy and security › Third-party cookies, and › Delete browsing data.
- Firefox: Settings › Privacy & Security › Cookies and Site Data.
- Edge: Settings › Cookies and site permissions.
Blocking the strictly necessary cookies will stop you signing in, ordering or booking. Most browsers also offer a private or incognito mode that clears storage when you close it, and a “Do Not Track” or global privacy control setting — we do not run the kind of tracking those signals are aimed at, so there is nothing for them to switch off here.
Push notifications and wallet passes
Push notifications are controlled separately from cookies, in your browser or phone settings for the site. Wallet passes are controlled in the Apple Wallet or Google Wallet app, where you can delete a pass or turn off its notifications at any time.
7. If you run a business on LoyalMT
Your customers reach your menus, cards, booking pages and order pages through our infrastructure, so what is described above is what happens on those pages. If you embed a LoyalMT page or link in your own website, or add your own analytics, advertising or chat scripts to your site, those are your responsibility — including getting consent for them where ePrivacy requires it, and having a cookie policy of your own.
Please do not inject third-party tracking into LoyalMT-hosted pages. Section 19 of the Terms of Service and the Acceptable Use Policy cover this.
8. Changes and contact
We will update this page if what we store on your device changes, and the date at the top will change with it. Material changes are recorded in the revision history below.
Questions: hello@loyalmt.com
LoyalMT, Address supplied on request, Malta
You can complain to the Information and Data Protection Commissioner (IDPC) in Malta, which also supervises the ePrivacy rules, at idpc.org.mt.
Revision history
- 13 November 2026 — First published. Previously there was no cookie policy at all, and the Privacy Policy’s only statement on the subject was that “analytics, if used, are anonymised” — which did not name Vercel Web Analytics, then already in use, and did not explain the ePrivacy position. This page names every category of storage, explains why no consent banner is required, discloses third-party payment and map cookies, and commits to building a consent mechanism before anything non-essential is ever added.