Cookie Policy
Nothing non-essential runs on this site until you say yes. There are now two things we ask about, and they are two separate questions because they do two separate jobs: analytics, which counts visits, and our sign-up form. You can say yes to one and no to the other. There is no advertising anywhere on this site and we do not sell or share anything about you.
What changed on 10 August 2026
We added Google Analytics. Version 2.1 of this page promised that if we ever added something with a genuinely different purpose, analytics being the example we gave, we would split the question rather than bundle it into the existing one. We have. Everyone who answered the old single question is being asked again, because agreeing to one thing is not agreeing to a larger thing.
What we store in your browser
| Name | Type | Purpose | Expires |
|---|---|---|---|
maritsa.consent |
Local storage, first party. Not a cookie, and never sent to us or anyone else. | Remembers your answers to the questions below, so we do not ask again on every page. It records what you chose for each category, when you chose it, and which services the question covered. It is only written once you have answered. | Until you clear your browser data or change your answer |
maritsa.notify |
Local storage, first party. Not a cookie, and never sent to us or anyone else. | Remembers that you have already been shown, or already used, the sign-up invitation, so you are not asked a second time. | Until you clear your browser data |
_ga |
Cookie, set by Google Analytics. Only ever present if you agreed to Analytics. | Gives your browser a random identifier so repeat visits are counted as one person rather than several. It is not tied to your name or email, and it is not used for advertising. | Two years, set by Google |
_ga_1KJG1JKJX5 |
Cookie, set by Google Analytics. Only ever present if you agreed to Analytics. | Holds the state of your current visit for this site specifically. The letters and numbers after the underscore identify our own Analytics property, nothing about you. | Two years, set by Google |
__kla_id |
Cookie, set by Klaviyo's code. Only ever present if you agreed to the sign-up form. | Identifies your browser to Klaviyo, so that a sign-up can be matched to the visit it came from. It does not follow you to other websites. | Two years, set by Klaviyo |
__kl_key |
Local storage, written by Klaviyo's code. Only if you agreed to the sign-up form. | Holds the key Klaviyo uses to tie your browser to its own record of the visit. | Until you withdraw or clear your browser data |
klaviyoOnsite |
Local storage, written by Klaviyo's code. Only if you agreed to the sign-up form. | Remembers which of our forms you have already been shown, so you are not asked the same thing on every page. | Until you withdraw or clear your browser data |
$referrer, $last_referrer |
Local storage, written by Klaviyo's code. Only if you agreed to the sign-up form. | Record which page or site you arrived from, so a sign-up can be credited to the right source. | Until you withdraw or clear your browser data |
datadome |
Cookie, set by our hosting provider's bot protection. Present for everyone. | Tells automated traffic apart from real people, so the site is not overwhelmed by scanners. It is not used to profile you, and nothing about it reaches our mailing list or our analytics. This is a security measure and is treated as strictly necessary under regulation 6(4), so we do not ask permission for it. It is listed here because you are entitled to know it exists. | Set by the provider, typically about a year |
That is the complete list as observed on this site, checked in a browser rather than taken from a vendor's documentation. Everything in it except maritsa.consent, maritsa.notify and datadome is removed if you withdraw. Those first two only ever record your own choices; the third is a security measure we do not control. If the list ever grows, this page is updated and everyone is asked the question again.
Removed since version 3.0. Our hosting provider's performance monitoring was writing a key called ddSession to your browser without asking. We enabled it by accident on 10 August 2026 while switching on a separate, cookie-free traffic count, spotted it the same morning, and turned the feature off. Nothing on this site writes that key any more. If your browser still holds one from before, it is inert and nothing reads it; clearing your browser data removes it.
The maritsa.consent and maritsa.notify records are strictly necessary under regulation 6(4) of the Privacy and Electronic Communications Regulations, because their only function is to carry out a preference you expressed yourself. They do not need your consent and they do not identify you.
The two services we ask about
| Service | What it does | What it means for you |
|---|---|---|
| Google Analytics 4 Analytics |
Counts visits and shows us which pages are actually read, so we can tell whether any of this is working. | Its code is loaded from Google's servers, so Google receives your IP address when it loads. Google shortens IP addresses on collection and we cannot see the full one. We have deliberately turned off Google Signals, ad personalisation and all three advertising consent signals on this property, so the data is not used to build an advertising profile of you or to follow you around other sites. We have also switched on Google's own filter that strips out anything resembling an email address before it is recorded. None of this happens unless you agree. |
| Klaviyo Sign-up form |
Displays the styled form inviting you to join our mailing list, and remembers whether you have already used or dismissed it. | Its code is loaded from Klaviyo's servers, so Klaviyo receives your IP address when it loads. It sets the cookie and storage keys described above. None of this happens unless you agree. |
Saying no to the sign-up form does not stop you signing up. If you decline, or if something blocks Klaviyo's code, we show you a plain form of our own instead. It loads nothing from anyone else, sets no cookie and stores nothing. It only sends your details when you fill it in and press the button.
How the question works
On your first visit you are asked, before anything non-essential loads:
- Reject All is one click, in the same place, the same size and the same styling as Accept All. It is listed first.
- Two separate boxes, one per purpose, so you can allow the count without allowing the form or the other way round. Use Choose what to allow to see them, then Save my choices to record a mixture.
- Nothing is pre-ticked. Both boxes start empty and stay empty unless you tick them.
- There is no wall you have to get past, and no way to make the question go away by ignoring it. Pressing Escape or clicking elsewhere does nothing — silence is not consent.
- If you reject, nothing non-essential loads, and we do not ask you again unless what we are asking about changes.
- If what we ask about ever grows, everyone is asked again.
What we do not use
- No advertising or social media tracking. No Meta pixel, no Google Ads tag, no TikTok or LinkedIn tracking, and no remarketing. Our Analytics property is configured so that its data cannot be used for advertising.
- No marketing text messages. Giving us a phone number does not sign you up to anything.
- No selling or sharing. We do not sell your details and we do not pass them to anyone for their own marketing.
- No third-party content beyond the two services named above. Our type, images and films are served from our own domain. Web fonts were previously loaded from Google's servers, which sent every visitor's IP address to Google; we moved them onto our own site on 4 August 2026 so that no longer happens.
- No session cookies from us. There are no accounts and no basket on this site, so there is nothing to keep a session for.
Hosting
This site is hosted by Netlify. It keeps server access logs, which include your IP address, for a short period in order to serve the site, count traffic and protect it from abuse. That traffic count is done from those logs rather than from anything placed on your device, which is why it needs no permission and appears nowhere in the table above. Netlify's bot protection sets the datadome cookie described above. Our hosting is covered in section 3 of our Privacy Notice.
The trade enquiry and sign-up forms
The trade enquiry form, the launch notification field on our home page, the sign-up invitation and the plain form on our join page all send what you type directly to our systems when you press the button. They place no cookie and store nothing in your browser, so they are not covered by the question above. What we do with those details is set out in our Privacy Notice.
Changing your mind
You can review or change your answers at any time using the link, which appears in the footer of every page. Withdrawing is as easy as agreeing, which is what UK GDPR Art. 7(3) requires.
Two honest details about how that works. Opening the panel clears your stored answers before it asks again, so if you open it and navigate away without choosing, you will be asked once more on your next visit. And if you withdraw after previously agreeing, we delete the stored data and stop loading the service — but code already running in that page view stops fully on your next page load rather than the same instant.
You can also block or delete cookies and local storage in your browser settings. Doing that will not break this site, because nothing here depends on them.
Questions
Email sales@bigk.co.uk. If you are not satisfied with our answer you can complain to the Information Commissioner's Office at ico.org.uk/make-a-complaint.
Maritsa · Privacy Notice · Prize Draw Terms ·
Imported and distributed by Big K Products UK Ltd, London N17 9QU. Produced and bottled by K. Maritsa Estates Ltd, Kampia, Cyprus.