§ Cookies
Cookie policy
There is no cookie banner on this site because there is nothing here to consent to. This page explains exactly what that means and what the one cookie we do set is for.
The short version
This website sets one cookie, only on the contact page, and only to stop somebody else's site submitting the enquiry form as you. It carries no identifier we can reuse, expires when you close your browser, and goes nowhere near anybody else.
No analytics. No advertising. No social media pixels. No embedded video. No fonts or scripts loaded from another company's servers. Nothing on this site reports your visit to a third party, which is also why the privacy policy can be as short as it is on the subject.
What this site sets
| Name | Purpose | Type and life |
|---|---|---|
| .AspNetCore.Antiforgery.… | Holds an anti-forgery token so the server can tell that the enquiry form was submitted from this site by you, and not forged by another page you happened to have open. Set only when a page with a form is served. |
Strictly necessary. Session cookie — removed when you close the browser.
First party, HttpOnly, SameSite=Strict, and
Secure over HTTPS.
|
We may also, in future, store a preference you have explicitly set — a reduced-motion choice, for example. If we do, it will appear in this table before it appears in your browser.
Why there is no banner
Regulation 6 of the Privacy and Electronic Communications (EC Directive) Regulations 2003 requires consent before storage on your device, with an exception for storage that is strictly necessary to provide a service you have asked for. An anti-forgery token on a form you are submitting is the textbook example of that exception.
Since the only cookie here falls within it, asking you to click a banner would be theatre. If we ever add a cookie that does need consent, you will get a real choice, it will default to off, and refusing will be exactly as easy as accepting.
What we do not use
- No analytics of any kind on this site — no Google Analytics, no self-hosted alternative;
- No advertising or remarketing tags, conversion pixels or identity graphs;
- No social media buttons, feeds or share widgets that phone home;
- No third-party fonts — the site uses the fonts already on your device;
- No CDN for scripts or styles; everything is served from this origin;
- No session recording, heatmaps, chat widgets or A/B testing tools;
- No fingerprinting — we do not profile your device in place of a cookie.
This is enforced technically as well as by policy: the site sends a Content Security Policy that forbids loading scripts, styles, fonts or images from anywhere but this origin, so a tracker could not be added by accident.
Cookies in the products
Footersly and MailAuthInspector are signed-in applications and necessarily set more than this brochure site does — a session cookie, an authentication cookie, an anti-forgery token, and a cookie remembering interface choices such as a collapsed menu. Each product documents its own cookies on its own site, and neither uses advertising cookies.
Controlling cookies yourself
Every major browser lets you see, block and delete cookies, usually under Privacy or Site Settings. Blocking cookies for this site will stop the enquiry form working, since the server cannot then verify the submission; everything else on the site will behave normally. Email hello@trustlayertechnologies.com instead if you would rather not allow it.
Browsers also offer Do Not Track and Global Privacy Control signals. We have nothing to switch off in response to them, which is the outcome they are asking for.
Changes to this policy
If the cookies this site sets change, this page changes first. The date at the top tells you when it was last reviewed.
Questions about this document
Write to privacy@trustlayertechnologies.com for anything about data protection, or hello@trustlayertechnologies.com for everything else. Post reaches us at the registered office: to be confirmed.