Cookies
Cookie policy
RelayLink sets three cookies, each of them needed for the pages that set it to work, and none of them for tracking. This page says what each is, what it holds, how long it lasts, and why there is no banner asking you to accept them. Last updated 19 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 step that asks for your code, the consent screen, or any page of the account portal. | Until you close the browser. |
relaylink-notice |
Carries a one-line confirmation of what you just did in your account — “Sent to Priya”, “Key revoked” — to the page you land on next, which shows it once and deletes it. | You submit a form in your account. | Until the next page reads it, and two minutes at most. |
All three 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. The sign-in cookie holds your address and a session marker, encrypted so that only this service can read them. The antiforgery cookie holds a random value and nothing about you. The notice cookie holds the confirmation sentence itself, which can name the person you acted on, unencrypted, for the two minutes at most that it lives.
Browser storage
Where the assistant built into your account pages is available, those pages keep two things in your browser’s session storage: whether the assistant’s panel is open, and a message you have typed to it but not sent, so moving between pages does not lose it. The browser discards both when the tab closes, and neither is sent anywhere. Nothing else on the site uses browser storage.
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 sign-up 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. We have not enabled the click and open tracking our email provider offers, and our emails load no images, so no link in a RelayLink email passes through a tracker.
Why there is no banner
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. All three of ours are: one keeps you signed in after you asked to be, one protects the form you are about to submit, and one tells you that what you just asked for was done. The session storage holds only what you typed or opened yourself, for as long as the tab is open. 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, and closing the tab clears the session storage. 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
Questions about cookies or anything else in the privacy policy go to hello@relaylink.ai — the only channel we take them on. PillarStack LLC is in Richmond, Virginia, United States. The whole set of policies is listed at relaylink.ai/legal.