The whole page in five lines
In short
- Hyyryn sets no cookies. Our website and our platform send none.1
- Your browser keeps a few things for us, on this device. The item that keeps you signed in, and some things you did here, such as a company you looked up. Only the sign-in item is ever sent back to us, with your requests, so we know it is you.
- Stripe sets two cookies on the payment step, to stop fraud. Stripe holds the money; that is the only page where it runs.2
- Cloudflare, which carries the site, may set one if it needs to tell a person from automated traffic.3
- None of it is for advertising or analytics, and nothing follows you to other sites.
The sign-in item is needed to use your account, so the law does not ask for your consent to it. Everything else only changes how the site looks and works for you. You can clear it with the button on this page, or in your browser, and the site still works.
Every cookie anyone sets while you use Hyyryn
Cookies
A cookie is a small file a website asks your browser to keep and send back to it. Hyyryn asks for none. These are set by the companies we work with, on the pages named.
__stripe_midStripe, on hyyryn.comOn the payment step1 year2To recognise the device across payments, so Stripe can stop fraud.
__stripe_sidStripe, on hyyryn.comOn the payment step30 minutesThe same, for one visit.
mStripe, on m.stripe.comOn the payment stepUp to 400 daysStripe’s own fraud checks, on its own address.
__cf_bmCloudflare, on hyyryn.comOnly when Cloudflare’s checks for automated traffic are on30 minutes3To tell people from automated traffic. It holds no name and no account.
cf_clearanceCloudflare, on hyyryn.comOnly if you are asked to pass a checkAs long as the check lastsTo remember that you passed it.
Stripe explains its fraud checks in its own words and its cookie policy; Cloudflare lists its cookies here.
Four kinds, every name listed
Your browser’s storage
Your browser keeps two stores for each website: one that lasts until it is cleared, and one for the open tab only. This is everything Hyyryn keeps in them. Every name begins with hyyryn or hy, so you can find them in your browser’s tools.4
AKeeping you signed inUntil you sign out
hyyryn_token- The key to your account. Sent to our platform with each of your requests, so we know it is you. Until you sign out.
hyyryn_user- Your name and the kind of account, so a page can draw before it hears from us. Until you sign out.
hyyryn_known- The email you last signed in with on this device, to welcome you back. Until cleared.
hyyryn_admin_token,hyyryn_admin_name- Hyyryn staff only, on the staff pages: their key, and the name they put on a decision. Until they sign out, or it is cleared.
BWhat you did here, kept for youUntil cleared
hyyryn.jobs,hyyryn.quotes,hyyryn.me,hyyryn.services- A copy of your jobs, quotes, profile and listings as last loaded, so pages open quickly. The real ones are on your account.
hyyryn.saved- Services and jobs you saved on this device. Signed in as a tradesperson, your saved jobs are kept on your account instead, and any saved here move there.
hyyryn_pins- Messages you pinned.
hyyryn.records.recent- Companies you looked up on Hyyryn Records, newest first.
hyyryn.watch,hyyryn.watch.*- The companies you watch on Hyyryn Records, and whether you watch each one, so the button shows the right state.
hyyryn.has-org- Whether to show the organisation menu.
hyyryn.start.hidden.*,hyyryn.trustnotice.shut- A setup list you hid, a notice you closed.
hyyryn.rail.pinned- Whether you pinned a dashboard’s side panel open, on a wide screen.
hyyrynDoor- Which part of Hyyryn you came in by: hiring, or Records.
hyyryn.db.v1,hyyryn.migrated.seededflag.v1- Examples shown before your account has anything of its own, and a note that old examples were cleared.
CNot showing you the same thing twiceUntil cleared, or the visit ends
hyyryn.tour.seen.*- A page’s tour you have seen or turned down.
hyyryn.guide.min.*,hyyryn.guide.done.*,hyyryn.setup.done.*- For a tradesperson: that the setup guide was folded or finished, and that the moment your setup was complete has been shown, so each shows once.
hyyryn.pad.agreed.v1- That you went through the homepage’s receipt.
hyyryn.plans.nudge.v1- When you last saw the note about plans, so it stays away for 30 days.
hyyrynSplashSeen,hyyrynSplashShown,hyyrynDoorSent- That the opening has played this visit. For the open tab only.
DThis tab onlyGone when the tab closes
hyTurn,hy-nav-dir,hy-last-page- Which way to turn the page when you go back and forward.
hyyryn.help.role- Whether Help is showing a homeowner’s answers or a tradesperson’s.
hyyryn.plans.sale- Which plans are on sale, kept for 10 minutes so each page does not ask again.
hyyryn.mvp- Which parts of Hyyryn are open yet, kept for half an hour so each page does not ask again.
hyyryn.notes-read- Notices you opened in this tab, so they stay read while our platform saves it.
hyyryn.google.cfg,hyyryn.google.step- Whether Continue with Google is on, and where you were in it.
hyCapToken,hyCapDevice- On the phone camera page: the one-time link that lets this phone send photographs to a job.
hyyryn.demo- On our preview site only: show examples.
Who else your browser talks to, and when
Other services your browser contacts
Loading a page from another service sends it your internet address, as any website receives it. These are all of them; no other site is contacted.4
- Cloudflare carries every page and every request to our platform.Every page
- Stripe: js.stripe.com, m.stripe.com and m.stripe.network.The payment step
- Google: accounts.google.com, once Continue with Google is switched on.The sign-in pages
- OpenFreeMap: the map pictures on pages that show where trades work. It sets no cookies.Pages with a map
- Hyyryn’s own: platform.hyyryn.com and records.hyyryn.com.As needed
Our typefaces and pictures come from hyyryn.com itself, so loading a page tells no one else you are reading it.
Not now, and not quietly later
What we never do
- Advertising cookies, or anything that follows you to other sites.
- Analytics cookies, tracking pixels or session recording.
- Sharing what you browse with advertisers, or selling it to anyone.
- Adding any of these without first changing this page and asking you.
If your browser sends a Global Privacy Control or Do Not Track signal, there is nothing for it to switch off: we track nothing.
Yours to remove
Clearing and blocking
On this page: the button under On this device, now clears everything Hyyryn keeps in this browser, and Stripe’s two cookies on our address.
In your browser: clear this site’s data, or block cookies or storage, in its settings: Chrome, Firefox, Safari, Edge.
What happens if you block them
- Kind A blockedYou cannot stay signed inEvery page asks who you are again.
- Stripe’s blockedA payment may need an extra checkOr Stripe may refuse it, as it would anywhere.
- Kinds B to D clearedThe site still worksThe introductions show again, and pages open a little slower the first time.
The particulars
Changes, and who we are
When what the site keeps changes, this page changes with it, and the date below says when. The privacy notice, section 8, says the same in short.
- The company
- HypeBox Ltd, trading as Hyyryn
- Registered
- England and Wales, company 16355767
- About your data
- support@hyyryn.com
- This page
- Last updated 21 October 2026
How we know
- On 13 October 2026 we asked hyyryn.com, our preview site and our platform for their pages and read every reply’s headers: none set a cookie, and nothing in the site’s own code writes one. ↩
- The same day we loaded the payment step in a browser and read the cookies it was left with:
__stripe_midfor 525,600 minutes (a year),__stripe_sidfor 30, and Stripe’smon its own address. Stripe describes the checks behind them in its fraud detection guide. ↩ - From Cloudflare’s list of its cookies, which says
__cf_bmends after 30 minutes without activity and holds no user ID. On 13 October Cloudflare set none on an ordinary visit. ↩ - We walked every page of the site signed out, as a homeowner and as a tradesperson, read what each left in the browser and noted every other address it contacted. A test now compares the names in section 3 with the site’s code, so a new one cannot be added without this page. On 21 October 2026 we found that it had missed names the code holds in a variable: ten were kept that this list did not name. They are named above, and the test now reads those too. ↩