Cookie policy

RelayLink sets two cookies, both of them needed for the pages that set them to work, and neither of them for tracking. This page says what each is, how long it lasts, and why there is no banner asking you to accept them. Last updated 5 September 2026.

What a cookie is

A cookie is a small piece of text a website asks your browser to keep and send back on later requests to the same site. It is how a site remembers that you signed in a moment ago. Some sites also use cookies to follow you across pages and across other sites; RelayLink does not.

The cookies we set

Name	What it does	Set when	Lasts
`relaylink-signin`	Records that this browser proved, by an emailed code, that it can read the address on an account. It is what lets you open your inbox, your contacts and your settings without a code on every page.	You sign in on the account portal or the consent screen.	Until you close the browser, or eight hours after you last used the portal, whichever comes first. Signing out ends it at once.
`.AspNetCore.Antiforgery.`…	Pairs with a hidden field in each form we serve, so that a submission we receive can be checked to have come from the page we sent and not from another site pretending to be you.	You open a page with a form on it: the sign-in page, the consent screen, or any page of the account portal.	Until you close the browser.

Both are first-party, sent only to relaylink.ai, marked so that scripts cannot read them, and sent only over HTTPS outside a developer's own machine. Neither holds your address, your name or anything about what you have read; the sign-in cookie holds an encrypted reference that only this service can decode.

Where we set none

The public pages — the landing page, the guides, the documentation, this page and every other policy — set no cookie at all. Neither does the page a briefing link opens, nor the reply form on it. Tests in our code hold that line. The founding list form on the landing page deliberately carries no antiforgery cookie: an anonymous form has no identity to protect, and a cookie on that page would make a shareable page per-visitor.

No third-party cookies, and nothing like them

There are no analytics cookies, no advertising cookies, no social media buttons, no embedded fonts or scripts from another domain, and no tracking pixels in our emails. Every stylesheet, font and script the site uses is served from relaylink.ai. Browser storage other than cookies is not used. We also turn off the click and open tracking our email provider offers, so no link in a RelayLink email passes through a tracker.

Laws that require consent for cookies — the EU's ePrivacy rules and the national laws that implement them — exempt a cookie that is strictly necessary to provide a service the person asked for. Both of ours are: one keeps you signed in after you asked to be, and the other protects the form you are about to submit. There is nothing optional to consent to, so there is nothing to ask. If we ever add a cookie that is not strictly necessary we will ask first, and this page will change.

How to control them

Your browser lets you view, block and delete cookies for any site. Blocking ours stops the account portal and the consent screen from working, because a form submission or a signed-in page cannot be verified without them; everything public keeps working. Signing out, or closing the browser, removes the sign-in cookie. Your browser's “Do Not Track” setting and the Global Privacy Control signal change nothing here, because there is no tracking for them to turn off.

Contact