AISnapMeal Get Started

Cookies Policy

Last updated: October 21, 2026

trades as AISnapMeal, and in this policy “we”, “our” and “us” mean that company. This page tells you which cookies and similar technologies — your browser’s own storage, for example — we use on aisnapmeal.com and in your AISnapMeal account. It is written to give you the information that the EU ePrivacy Directive (as implemented in ) and the GDPR require us to give.

The short version. On an ordinary visit, the one cookie this site sets of its own is the sign-in cookie of your customer account. When the payment button of our payment provider loads, the provider adds a single cookie. On top of that, a few entries for this site live in your browser’s storage. You will find every one of them listed below. (Apple Pay and the provider’s card-payment partner work inside the payment form and may add cookies of their own there — see section 6.1.)

Table of Contents

  • What is a cookie, and what is browser storage?
  • Why do we use cookies and browser storage?
  • Which kinds of cookies do we use?
  • Which cookies are set, one by one?
  • Does Google set cookies here?
  • Do other companies set cookies here?
  • What else works like a cookie?
  • What does the cookie notice do?
  • How can I control cookies?
  • Where are the settings in my browser?
  • Can I opt out?
  • Do you respond to Do Not Track or Global Privacy Control?
  • What about my phone?
  • What stops working if I block cookies?
  • Will this policy change?
  • How can I reach you?

1. What is a cookie, and what is browser storage?

1.1 A cookie in plain words

A cookie is a small text file. When you visit a website, the site can place one on your device — your computer, smartphone or tablet. From then on, whenever your browser asks that website for something, it sends the cookie back to the site that set it.

1.2 What is browser storage?

Your browser can also hold small pieces of information for a website inside the browser itself. This comes in two kinds. Local storage stays until it is cleared. Session storage is removed when you close the tab.

Unlike a cookie, none of this travels to the website automatically — the site’s own scripts read it. This policy covers cookies and browser storage alike.

1.3 How long does a cookie last?

Some cookies, called session cookies, disappear when you close your browser. The rest stay for a set period, or until you delete them.

Your customer account’s sign-in cookie doesn’t last long. It runs out after 30 minutes without activity, when you sign out, or 12 hours after you signed in — whichever comes first. Of all the cookies a customer comes across on this site, our payment provider’s fraud-prevention cookie lasts longest (section 4).

1.4 Who sets a cookie?

A first-party cookie comes from the website you are on — in this case aisnapmeal.com.

A third-party cookie comes from a different service, on that service’s own domain. On this site, that means our payment provider, inside the payment form it supplies — and, within that form, possibly Apple Pay or the provider’s card-payment partner (section 6.1).

2. Why do we use cookies and browser storage?

2.1 To make the essentials work

  • So you stay signed in to your customer account (a cookie)
  • So payments are taken securely and payment fraud is prevented (our payment provider’s cookie)
  • So your checkout holds together while you pay (session storage)

2.2 To make the site easier to use

  • So the site remembers that you closed the cookie notice (local storage)
  • So a support chat stays open as you go from page to page (session storage)

2.3 To measure visits

  • To recognise returning visits to this site, using a marker that belongs to this site alone (local storage)
  • To count page views, clicks and checkouts, so we can see how people use the site

2.4 To measure our advertising

  • To note the ad or campaign link that brought you here (session storage), so we can tell which of our ads and campaigns bring in visitors and subscriptions

And what we don’t do: no advertising cookies, no remarketing, and no analytics cookies, whether our own or anyone else’s.

3. Which kinds of cookies do we use?

Cookies are usually sorted into the four categories below. This site’s own cookies belong only to the first of them. Our payment provider’s fraud-prevention cookie is explained separately (sections 4.5 and 6.1).

3.1 Do you use strictly necessary cookies?

Yes. They are there because you have asked for something that needs them. The sign-in cookie keeps you signed in to your account, and your account cannot work without it. The test cookie opens the internal test links our team uses.

The legal basis: under the ePrivacy rules, a cookie that is strictly necessary for a service you ask for does not need your consent.

3.2 Do you use performance or analytics cookies?

No, none. We measure visits without cookies, in the way section 7 describes.

3.3 Do you use functionality cookies?

No, none. There are two things we remember for your convenience — that you closed the cookie notice, and a support chat you have open — and both are kept in browser storage instead (section 7).

3.4 Do you use targeting or advertising cookies?

No, none — and no advertising network sets cookies through this site either.

4. Which cookies are set, one by one?

Below is every cookie that we and our payment provider set. Apple Pay and the provider’s card-payment partner may add their own from inside the payment form (section 6.1).

4.1 Strictly necessary cookies, in detail

  • session — set by aisnapmeal.com (first-party). What it does: keeps you signed in to your customer account at aisnapmeal.com/portal. When it is set: when you sign in with a single-use sign-in link. How long it lasts: until you sign out, until 30 minutes pass without activity, or 12 hours after you signed in at the latest — whichever happens first.
  • dr_test — set by aisnapmeal.com (first-party). When it is set: only on the internal test links our team uses to check a landing page, and never on an ordinary visit. How long it lasts: 12 hours.

4.2 Performance and analytics cookies

There aren’t any.

4.3 Functionality cookies

There aren’t any.

4.4 Targeting and advertising cookies

There aren’t any.

4.5 The cookie our payment provider sets

  • vp_visitor — set by our payment provider, on its own domain (third-party). What it does: recognises the browser to prevent fraud, so that the provider can refuse a browser involved in a chargeback, a pre-dispute or a bank’s fraud report at any of the shops it serves. When it is set: whenever the provider’s payment button or payment page loads — on our checkout page once you have ticked its two confirmation boxes, on the page our ads lead to as soon as that page opens, and on the payment-method page of your account. How long it lasts: 400 days from when it is first set.

5. Does Google set cookies here?

No. Google sets no cookie through this site, and nothing we use from Google runs in your browser. In practice that means:

  • No Google Analytics
  • No Google Ads tags and no Google Ads conversion cookies
  • No Google Fonts — we serve our fonts from our own domain
  • No reCAPTCHA
  • No Google Tag Manager

5.1 What happens when I arrive from a Google ad?

Tap or click a Google ad, and the link that brings you here includes Google’s click identifier (gclid, gbraid or wbraid). We store that identifier in the note of how you arrived (section 7) and with your visit, so we can see which ads lead to subscriptions.

Should we connect a Google Ads account to measure conversions, it is our server — not your browser — that sends Google the click identifier, the time and value of the purchase, and a hashed (SHA-256) form of your email address. Our Privacy Policy explains this as well.

6. Do other companies set cookies here?

6.1 When you pay

The one piece of third-party content on this site is our payment provider’s payment form, and it sets the vp_visitor cookie listed in section 4.

Within that form, the provider may load Apple’s Apple Pay script (on browsers that don’t have Apple Pay built in) or the fields of its card-payment partner when you pay by card. Each of those services may set cookies of its own for the payment, and does so under its own policies.

6.2 Social media

None. You won’t find social media buttons, pixels or embedded posts anywhere on this site.

6.3 Analytics and optimisation

None. We don’t use any third-party service for analytics, and none for session recording either.

6.4 Customer support

The support chat belongs to us, and it sets no cookies. What it does keep is one entry in session storage (section 7).

6.5 Security and infrastructure

Neither our hosting nor our content delivery network sets any cookies.

7. What else works like a cookie?

7.1 How do you count visits without cookies?

While you browse, the pages send small requests to our own server. These record page views, clicks and checkout steps, along with the visit marker described below. The requests go to this site only, and never to a third party.

Our emails carry no tracking pixels either, and the links inside them are not tracked.

7.2 What does the site keep in local and session storage?

Here are the entries this site keeps in your browser. The names look random because each one is unique to this site:

  • sq5i48il4zi (local storage) — the visit marker. It is a random identifier that lets this site recognise a returning visit. It travels with this site’s measurement requests, price look-ups, checkout, support chat messages and contact form messages, and with nothing else. Set on your first page view, it stays until you clear it, and each visit record it links is deleted after 18 months.
  • s02k782422q (local storage) — remembers that you chose Accept or Reject on the cookie notice, so the notice stays closed. Set when you click, and kept until you clear it.
  • s0p9spsj148 (session storage) — the note of how you arrived, holding the advertising click identifier and campaign parameters of the link you followed (for example gclid, gbraid, wbraid, fbclid, msclkid or utm_ parameters). Present only when the link carried them, and removed when you close the tab.
  • Checkout entries (session storage) — hold your checkout session together while the payment form loads and while you pay. Removed when you close the tab.
  • A button-test entry (local storage) — records which version of a button you saw, so you keep seeing the same one. Used only on the page our ads lead to, and only while we test the wording of its button. Kept until you clear it.
  • s0z12q8iqs7 (session storage) — the price you were shown, so the checkout charges you that same price. Used only while we test prices, and removed when you close the tab.
  • s588554i24j (session storage) — lets an open support chat carry on when you go to the next page. Set only after you send a chat message, and removed when you close the tab.

7.3 What device details are sent at checkout?

To help prevent payment fraud, the checkout sends our payment system some technical details of your browser and device when you start a payment — for example screen size, time zone, languages, platform and browser version. Those details are stored with the record of your purchase, as our Privacy Policy describes.

7.4 Do you fingerprint my device?

No. We don’t use these details — or any other technique — to recognise you from one website to another.

7.5 What about ETags and caching?

To make pages load faster, our content delivery network relies on standard HTTP cache mechanisms (ETags and cache headers). They play no part in tracking.

8. What does the cookie notice do?

8.1 What the notice tells you

On your first visit, a notice lets you know that we use essential cookies and that we measure visits and ads. It comes with an Accept button, a Reject button and a link to this policy. You won’t see the notice on the page our ads lead to.

8.2 What happens when I click a button?

Your browser stores the choice (the s02k782422q entry in section 7) so that the notice stays closed. That is all it changes.

Either way, on an ordinary visit the site sets no cookie of its own outside your customer account. And the visit measurement and the note of how you arrived, both described in section 7, work in the same way whichever button you choose.

What this means for you: if you want to stop them, you need to block or clear this site’s storage in your browser (section 9).

8.3 How do I change my choice?

Clear this site’s data in your browser, and you will see the notice again the next time you visit.

9. How can I control cookies?

9.1 Your browser’s own settings

All the major browsers give you control over cookies and site storage. Typical settings let you:

  • Block every cookie
  • Block third-party cookies
  • Clear cookies and site data, for a single site or for all of them

9.2 What about private browsing?

If you browse in a private or incognito window, its cookies and site storage are deleted once you close that window.

10. Where are the settings in my browser?

Here is where to find the controls. For the exact steps in your version, see that browser’s own help pages:

  • Using Google Chrome? Head to Settings → Privacy and security
  • Using Mozilla Firefox? Head to Settings → Privacy & Security → Cookies and Site Data
  • Using Safari on a Mac? Head to Safari → Settings → Privacy
  • Using Safari on an iPhone or iPad? Head to the Settings app → Safari (on recent versions, Settings → Apps → Safari)
  • Using Microsoft Edge? Head to Settings → Cookies and site permissions
  • Using Opera? Head to Settings → Privacy & security

11. Can I opt out?

This site has no analytics or advertising cookies, so there are none here to opt out of.

For personalised advertising you see elsewhere, you can make your choices in your Google account’s ad settings, through Your Online Choices (youronlinechoices.com, for the EU), and in the advertising settings of the social networks you use.

12. Do you respond to Do Not Track or Global Privacy Control?

12.1 Do Not Track (DNT)

“Do Not Track” is a setting in your browser that asks websites not to track what you do. No universal standard exists for how a site should respond to it, and this site behaves the same whether or not it receives the signal.

12.2 Global Privacy Control (GPC)

We don’t act on the Global Privacy Control signal either. Bear in mind that this site sets no advertising cookies, and loads no advertising network’s scripts.

13. What about my phone?

13.1 Phone browsers

AISnapMeal works in the browser on your phone. That means this policy, and your browser’s settings, apply on your phone exactly as they do on a computer.

13.2 Do you use advertising identifiers?

No. We don’t use mobile advertising identifiers (such as IDFA or GAID), and we don’t use tracking SDKs.

13.3 How do I limit ads on my phone?

If you want to limit personalised advertising across your phone as a whole, go to Settings → Privacy & Security → Tracking and Apple Advertising on iOS, or to Settings → Google → Ads on Android.

14. What stops working if I block cookies?

14.1 If you block all cookies

  • Signing in to your customer account won’t work
  • The payment form may fail, which means you may not be able to subscribe
  • The rest of the site keeps working as normal

14.2 If you block or clear site storage

  • The site won’t recognise your visits when you come back
  • You see the cookie notice again
  • A support chat you have open starts from scratch on the next page

15. Will this policy change?

15.1 When we update it

This Cookies Policy gets updated when the cookies or storage we use change, when the law changes, or when our own practices change.

15.2 How you will know

Each time we change something, the “Last updated” date at the top of this page changes with it.

15.3 Checking back

It is a good idea to look back at this page now and then.

16. How can I reach you?

Got a question about cookies, browser storage or this policy? Here is how to reach us:

Company Registration Number:

Registered in

Registered Address: ,

Email:

Can I complain to a regulator?

Yes. If you disagree with how we process personal data, you may lodge a complaint with the Data Protection Commission (DPC), which is ’s supervisory authority, or with the data protection authority in the place where you live.

Data Protection Commission ()

21 Fitzwilliam Square South, Dublin 2, D02 RD28,

Website: dataprotection.ie

Effective Date: October 21, 2026

Version: 2.0

© 2026 . All rights reserved.