Cookie policy.
Last updated 6 October 2026
This site, run by iMint Ltd trading as ReMint, sets one cookie of its own, and only after you have answered the banner. We do keep a small amount of other information in your browser, which the rules treat in the same breath as cookies, so this page is about that too. The banner asks two separate questions, one about advertising cookies and one about analytics cookies, and this page lists what you would be saying yes to in each case. What we do with personal data is in the privacy policy.
Cookies
One from us, and none from anybody else unless you say yes on the banner. There are two things to say yes or no to, and they are asked separately because they are different things: advertising cookies, listed further down, and analytics cookies, which are Google Analytics and are described in their own section below. You can accept one and refuse the other.
The one cookie we set ourselves is rm_consent, which records your two answers so we do not ask again. It holds a yes or a no for each of them, the date, and a number saying which questions we had put to you at the time, so that a question you were never asked is never read as a no. Nothing else. It lasts a year, it is only set once you have answered, and it is strictly necessary in the legal sense, because without it we could not remember that you said no.
What we keep in your browser
The law here is about storing anything on your device rather than about cookies specifically, so these are listed for the same reason a cookie would be.
- A sign in session, only if you sign in. Customers and our own team get the same one: it is how the next page knows it is still you. It goes when you sign out.
- Which phone the calculator opened on, so the page does not change underneath you while you are reading it. It lasts until you close the tab.
- Your last quote: the phone, its size and its grade, so the homepage can offer it back at that day’s price when you return. Nothing about you, and no price is kept. It goes when you close it with the cross, when you place an order, or after thirty days.
- How you found us: one word such as google, instagram or direct, taken from the link you arrived on. It is recorded once and kept, so an order placed days later still tells us which channel brought you. It is not your name, your email or anything that identifies you.
- The advert you arrived on, if you arrived on one: the reference the platform puts in the link it sends you here with, and, where that platform’s own cookies exist, what they hold. It is kept so that an order placed days later can still be matched to the advert that brought you. This one is written whichever way you answer the banner, because it is read off the link rather than set by anybody, but it only ever leaves us if you said yes to advertising cookies. Say no and nothing about you goes to any platform, whatever is sitting here.
- Whether you have already seen the opening animation, so you are not shown it twice.
How we count visits ourselves
This part uses no cookies and happens whichever way you answer the banner. We count page views and a few actions, such as opening the calculator. Each browsing session is given a random number that is thrown away when you close the tab, is never written into your account or your order, and is never linked to your name or your email. Nothing in that counting follows you from one visit to the next, apart from the two things in the list above: the one word for how you found us, and, if you arrived on an advert, its click reference. Your answers on the cookie banner are counted the same way, as a yes or a no with no name attached, so we can see how many people accept and how many decline. Google Analytics, below, is a separate thing and we ask before any of it happens.
Analytics cookies, only if you say yes
Say yes to analytics on the banner and we load Google Analytics, which sets two cookies: _ga, and one whose name begins _ga_ followed by the identifier of our Analytics property. They hold a random number for your browser and nothing about you, and they last two years, which is Google’s own default lifetime and one we have not changed. That is what makes three pages read one after another count as one visit rather than three, and what lets us see that somebody who came back a week later is the same browser rather than a new one. We use that to see which pages work, which ones lose people, and whether a change made things better. Google processes it for us and the data reaches Google’s servers.
Say no, or never answer, and neither of those two cookies is set. One honest detail, because a neater sentence here would be the wrong one: if you said yes to advertising but no to analytics, Google’s tag is on the page for the advertising, and it still counts your page view, but with analytics switched off at the tag it sets no analytics cookie and cannot recognise your browser next time. Say no to both and the tag is not on the page at all.
Advertising cookies, only if you say yes
When we run adverts, the platforms we advertise on want to know that a visit, a quote or an order came from one of their adverts, and they do that by setting cookies from a small piece of their code on our pages. We do not load any of that code until you have said yes to advertising on the banner. Say no, or never answer, and none of it loads. Say yes to analytics but no to advertising and none of these platforms is given anything either: no advertising cookie is set, and nothing about you is reported to any of them. Google is the one to be exact about, because its analytics and its advertising are a single tag. On an analytics yes that tag is in the page with its advertising side switched off inside it, so it sets the two analytics cookies described above, sets no advertising cookie, and tells Google nothing about any advert.
The table below says who could learn you had been here, what that company does with it, and how long that lasts. It covers every platform the site is able to load, switched on today or not, because a yes you give now still counts on the day one of them is switched on. Lifetimes are as each platform documents them today and are theirs to change. The cookie names themselves are in small print under each one, for anybody who wants to go and look for them. The last column is live, read from our own settings as you look at the page, and the platforms that are switched off, which set nothing at all, are folded behind a single line you can open.
| Platform | What it is for | Lasts | Now |
|---|---|---|---|
| Meta (Facebook and Instagram) | Lets Meta know that your visit came from one of our Facebook or Instagram adverts, and count a quote or an order against it. Cookies: _fbp (90 days), _fbc (90 days) | Up to 90 days | checking |
| Google Ads | The same for adverts on Google and YouTube: it ties your visit to the advert you clicked. Cookies: _gcl_au (90 days), _gcl_aw (90 days) | Up to 90 days | checking |
| Google Tag Manager | A container our marketing agency loads the others through. It sets nothing itself, and whatever is put inside it can, so it sits behind the same yes. | Nothing of its own | checking |
| TikTok | Ties your visit to a TikTok advert, and counts a quote or an order against it. Cookies: _ttp (13 months) | 13 months | checking |
| Microsoft Clarity | Records how pages are used (scrolls, taps, where people get stuck) so we can fix them. Analytics, not advertising. Cookies: _clck (1 year), _clsk (1 day), CLID (1 year) | Up to 13 months | checking |
| Microsoft Advertising | Ties your visit to an advert on Bing, or elsewhere in the Microsoft network. Cookies: _uetsid (1 day), _uetvid (13 months), MUID (13 months) | Up to 13 months | checking |
| Ties your visit to a LinkedIn advert, and lets LinkedIn recognise the same browser when it comes back. Cookies: li_sugr (90 days), bcookie (1 year), lidc (1 day), li_fat_id (30 days), UserMatchHistory (30 days), AnalyticsSyncHistory (30 days), li_gc (6 months) | Up to a year | checking | |
| X | Ties your visit to an advert on X, and lets X recognise the same browser when it comes back. Cookies: muc_ads (2 years), _twclid (30 days), personalization_id (2 years) | Up to 2 years | checking |
| Klaviyo | The email platform our marketing runs on. Its script draws the sign up forms on the site and recognises the same browser when it comes back, so an email you get from us can be tied to what you looked at. Only ever emails people who ticked marketing. Cookies: __kla_id (2 years) | Up to 2 years | checking |
Checking which of these is switched on.
What we tell them after you order, only if you said yes
If you said yes to advertising cookies and then sold us a phone, we may tell the platform whose advert brought you here that the order was placed, that the phone arrived, and that you were paid. Meta gets those stages with your email address in a scrambled form (a hash) that it can only match against an account it already holds, along with the identifiers its own cookies set and your IP address and browser details as they were when you placed the order, which we keep with the order for no more than 30 days. Google gets the click identifier from the advert and the stage, and, when you place the order, your email address in the same scrambled form, so it can match the order to the advert that brought you. The point is so the adverts learn which people actually post a phone, rather than which people fill in a form. No amount is ever attached to a quote, on any platform: the only place a figure can appear is on an order you have actually placed, and then it is what we agreed to pay you. Said no, or never answered, and none of this happens, whatever you go on to do.
You can change either answer any time from Cookie choices in the footer of any page, or with the same link just below. The banner and the link appear whenever we are asking, which can be before any platform is switched on: an early yes simply means the platforms load the day one is. Nothing here is sold, and the site, your quote and your order emails all work the same whichever way you answer.