Cookies and browser storage
Last updated: 27 September 2026.
There is no cookie banner on this website. This page explains what we store on your device instead, and why you are not being asked to click past it.
None of it is tracking. Everything on this page is either what keeps you signed in, or the interface remembering how you left it: which sidebar section you opened, how wide you dragged a column, whether you picked the dark theme. Nothing follows you to another website and nothing is used for advertising.
How much you get depends on how far in you are, so this page is in three parts: browsing, signing in, and using the customer portal.
Browsing the website
Name | Kind | What it does | If you clear or block it |
|---|---|---|---|
| Local storage | Your basket, so it survives a reload or a closed tab | The basket empties |
| Local storage | Whether you chose the light or the dark theme | The theme goes back to following your system setting |
| Local storage | Whether the modifications helper panel on the bespoke-order form is open | The panel returns to its default state |
| Local storage | Which corner of the screen you dragged that panel to | The panel returns to its default corner |
| Cookie, one hour | Remembers that this browser verified your email address, so checkout can carry on without asking twice | Checkout asks you to verify your email again |
| Local storage | Sequences you added to an order from one of our tools, so the order form can fill them in. Kept for seven days at most, and emptied when you send the order | The order form starts blank |
| Local storage | Only there if you switched website statistics off, so that your choice holds (see below) | This browser is counted again |
The checkout cookie only exists while you are actually going through checkout, and it goes stale after an hour whatever you do.
Signing in
Name | Kind | What it does | If you clear or block it |
|---|---|---|---|
| Cookie | Keeps you signed in to your account | You are signed out, and sign in again |
| Cookie, five minutes | A one-time puzzle your device answers when you sign in with a passkey, so the answer cannot be replayed by anyone else | Passkey sign-in fails and you use an emailed code instead |
| Cookie, five minutes | The same, at the moment you add a new passkey to your account | You cannot add a passkey until you allow it |
| Local storage | Which way you signed in last, so the page opens on that method instead of guessing | The page opens on the passkey option and waits to be asked |
If the last way you signed in on this browser was a passkey held on this device, the sign-in page offers one straight away rather than waiting to be asked, and login_challenge arrives as the page opens. It holds a single random value, it is tied to nothing but that one attempt, and it is thrown away whether or not you use it. Otherwise nothing is offered until you ask for it, and no challenge is issued: that covers a browser we have not seen you sign in from, one where you last used a password, and one where you last approved from your phone.
In the customer portal
The portal is a working interface rather than a set of web pages, so it remembers your layout the way a desktop application would. All of it is preference, and none of it is used to work out anything about you.
What it keeps falls into three kinds:
- How you like it laid out. Light or dark, which sidebar sections you left open and the order you dragged them into, how wide you dragged a column, and your organisation's name so the sidebar can show it straight away rather than blank-then-filled on every page.
- Where you had got to. Whether the help panel is open and how far through a guide you are, the order of the list you clicked in from so "previous" and "next" work while you are looking at a record, and whether you have already been shown the keyboard-shortcut tip.
- Something in transit. A value you copied with a field's copy button, waiting for you to paste it into another record. A "saved" message waiting to be shown on the other side of the reload that follows a save.
None of that is collected, and none of it is sent to us to look at. The one item that travels with a request is the theme, which rides along as a small cookie so that a page can be drawn in the right colours before it appears instead of flashing white first. The rest stays in the browser: some of it until you clear it, the rest only until you close the tab.
That is the shape of what the portal stores rather than a numbered inventory of it, and it grows as the interface does. A new panel that remembers where you put it is a new entry, and we update this page when one appears. What will not appear is anything that watches you rather than serves you. If we ever need that, you will be asked first.
Website statistics
We count visits to this website so that we can see which pages are useful and how people find us. The counting stores nothing on your device: no cookie, no local storage, nothing that is still there once you close the tab.
For each page you open we record the page, the page you came from, roughly how long you stayed, your browser type and screen size, and the country your connection is in. To find the country, and the organisation whose network you are on, such as a university, we use the network address your browser connects from. We do not keep it whole: the last part is removed as soon as the country is looked up, so what we keep points to a network and not to a device.
None of it is linked to your name, your email or your account, even if you sign in or order later, and it is not shared with anybody. It runs on our own servers. Anything in a page address that could hold what you typed, such as a sequence in a shared calculator link, is removed before it is sent.
If your browser sends Do Not Track or Global Privacy Control, nothing is counted. You can also switch statistics off with Website statistics at the foot of any page. That switch is the one thing we store for statistics, and only once you use it, so that your choice holds.
What we do not store
No advertising cookies. No tracking that follows you to another website. No third-party scripts, fonts, embedded videos or social widgets. On the public site and in the portal alike, everything a page loads comes from us, and nothing is shared with anybody for marketing.
We also run product analytics for our own staff working in the admin system. It does not observe customers in the portal.
This site is served through Cloudflare's network, which sees the IP address and the address of each page requested. Cloudflare's own protection cookies (__cf_bm, _cfuvid) are not in use here. If we ever turn on their bot challenges that will change, and so will this page.
Why there is no banner
The rule is that you must be asked before anything is stored on your device. There is one exception, and it is the whole of our position: storage that is strictly necessary to provide the thing you asked for.
Everything above is. You cannot stay signed in without a sign-in cookie. You cannot finish checkout without proof that you verified your email. A basket that forgets what you put in it is not a basket, and a sidebar that forgets which section you opened is a worse version of the thing you signed in to use. The theme, the column widths and the panel positions exist only because you chose them. None of it tells us who you are anywhere else, and none of it is used for advertising.
Website statistics store nothing on your device at all, so that rule does not reach them. Data protection law does, and the privacy notice explains how we meet it.
So there is nothing to ask you about. A banner here would be theatre, and clicking it would change nothing. If we ever add something that does need your consent, you will be asked before it runs, not after.
Clearing it
Every item above can be removed from your browser's settings, under site data or cookies for this site. Nothing breaks permanently: you sign in again, the basket starts empty, and the rest goes back to its defaults.
Questions
Email privacy@assemblon.co.uk. The privacy notice covers what we do with personal data more generally.