Cookies

Cookie policy

RelayLink sets three cookies of its own, each of them needed for the pages that set it to work. On the public pages, Google Analytics can set two more, but only if you allow it. This page says what each is, what it holds, how long it lasts, and how to change your choice. Last updated 20 October 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 other sites; RelayLink does not, and the analytics cookies below are used only to count visits to this site.

The cookies we set

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. On the public pages, your answer to the analytics question below is kept in your browser’s local storage as rl-analytics-consent, so we do not ask again on every page. It holds “granted” or “denied” and nothing else, and it is not sent anywhere.

Google Analytics, only if you allow it

The public pages — the landing page, the guides, the documentation, this page and every other policy — use Google Analytics to count visits: which pages are read, how people arrived, roughly where they are and what device they use. The first time you visit, a bar at the foot of the page asks whether to allow it, and both choices are one tap.

Until you allow it, and if you decline, Google Analytics sets no cookie. The page still sends Google a cookieless signal that a page was viewed, with no identifier that links one visit to the next, which Google uses to estimate totals. Google’s advertising features are switched off, and nothing is shared for advertising. Google Analytics never loads on your account pages, the sign-in and consent screens, or the page a briefing link opens, so it never sees correspondence. Its terms and Google’s own privacy policy govern what Google does with what it receives; it is listed with our other subprocessors.

Where we set none

The page a briefing link opens, and the reply form on it, set no cookie and load nothing from Google. Our server sets no cookie on any public page: the analytics cookies above are set in your browser by Google’s script, only after you allow them. 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 advertising, and nothing in our emails

There are no advertising cookies, no social media buttons and no tracking pixels in our emails. Apart from Google Analytics on the public pages, 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.

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. Those are never part of the question. The analytics cookies are not strictly necessary, so they wait for your answer.

How to control them

Choose Cookie settings at the foot of any public page to change your analytics answer at any time; choosing Decline also removes the analytics cookies already set. 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.

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.