Cookie notice

A cookie is a small file a website asks your browser to keep and hand back on the next request. Local storage does a similar job but stays in the browser and is never sent to the server. Both are covered here because from your side the question is the same: what is on my device, and why.

Some of it is necessary — without it you could not stay signed in and the site could not remember that you asked for high contrast. Anything not necessary needs your consent, and this site sets none of that kind.

Stating the absences is more useful than listing the presences, so:

• No analytics. There is no Google Analytics, no tag manager, no product analytics tool and no session-recording script.
• No advertising or retargeting. No advertising pixels, no conversion tags, no audience lists. We do not follow you to another site.
• No selling or sharing of anything stored on your device.
• No cookie wall. Nothing here is worth interrupting you for, so we do not.

If analytics are ever added, this clause changes before the script does.

Two lists. The first is set for everyone; the second only appears if you use the feature that creates it.

Over HTTPS the browser is asked to handle these more strictly, and the names gain a prefix to say so — you will see __Secure-authjs.session-token and __Host-authjs.csrf-token. Same cookies, tighter rules. All of them are set to be unreadable by JavaScript.

This site embeds Google’s page-translation widget so the content can be read in another language. That embed loads a script from translate.google.com, which means Google receives the request — including your IP address — whether or not you translate anything.

If you choose a language, Google sets its own preference cookie so the choice sticks. What Google does with data it receives is governed by Google’s privacy policy, not ours.

Whether to keep this embed at all is under review.

The typefaces are served from Google’s font hosts. Google receives the request and your IP address in order to return the font file, but no cookie is set for it and nothing is stored on your device beyond the browser’s normal file cache.

Portal cookies are only created once you sign in. If you never sign in, they are never set.

If you sign in with a Google account you are sent to Google to authenticate, and Google sets its own cookies on its own domain as part of that. We receive your name, email address and profile picture back — never your password.

Signing out clears the session cookie. What the portal records about you and your hardware is covered in the privacy notice.

• Site preferences. Clearing this site’s data in your browser removes the preference entry, and the site falls back to your operating system’s light or dark setting. Nothing breaks.
• Portal sign-in. Blocking or clearing these will sign you out. The portal cannot work without them.
• Everything at once. Every major browser lets you view, block and delete cookies and site data per site, usually under privacy or site settings. Private or incognito windows discard the lot when you close them.
• Do not track and global privacy signals. There is nothing here for them to switch off, so they change nothing on this site.

When this notice is issued it will carry a version and a date. It should be re-checked whenever a third-party script, embed or measurement tool is added to the site — the inventory above is only worth reading if it is true.

Questions about any of it: Info@amperearc.com.