Privacy Policy
Last updated 12 July 2026
Relay is a desktop application that operates your web browser on your behalf. To do that it has to see the pages you point it at. This policy explains exactly what leaves your computer, where it goes, and what we keep — in plain terms, because a policy you can’t follow is not consent.
Who we are
Relay is operated by Christopher Inegbedion, a sole trader based in the United Kingdom, who is the data controller for the purposes of the UK GDPR. You can reach us at privacy@relaythis.com.
The most important thing to understand
When Relay runs a task, the contents of the pages it is working on are sent to an AI model provider. That includes screenshots of those pages and the text on them, and it may therefore include anything visible while Relay is working — including personal or confidential information on the page.
This is not incidental; it is how the product works. Relay cannot operate a page it cannot see. If a page contains something you would not want sent to a third-party AI provider, do not run Relay on it.
Page content passes through our server and on to the model provider. We do not store the page content, screenshots, or the text of your tasks. We record only what the call cost — the model used, the number of tokens, and the price — so we can meter usage.
Your contact details
When you finish setting Relay up, you are shown your name, email address and phone number and asked to approve them. Those three details are sent to us and stored against your account, so that we can reach a person rather than an anonymous token — to send you your invite, tell you about a problem, or answer you when you get in touch.
We do not take your address, even though Relay asks you for it. We have no use for it, and data held with no purpose is only a liability. Nothing else from your setup is sent.
What stays on your computer
Everything else Relay knows about you never leaves your machine. It is stored on your own disk (under your Documents folder) and is not uploaded to us:
- your postal address;
- documents you give it, such as a CV;
- your task history, the agent’s memory, and any screenshots it took;
- your Relay account token.
Deleting that folder deletes that data. We have no copy of it. (The page contents of a task are still sent to the model provider while the task runs, as described above, and your name, email and phone number are held against your account as set out just above.)
What we collect
| What | Why | Kept for |
|---|---|---|
| An installation ID — a random identifier for your copy of Relay. It is not derived from your hardware and says nothing about you or your machine. | To attach your account to your installation, apply your usage limit, and let us disable an account if we have to. | As long as your account exists. |
| Setup-session data — a random temporary session identifier, your installation ID, the invite used to approve it, and a one-way hash of a one-time setup secret. | To securely unlock the copy of Relay that opened the setup page without putting its account credential in the browser or URL. | The session expires after 10 minutes. Expired records are removed automatically during later setup activity. |
| Usage records — for each AI call: the model, token counts, and cost. Not the content. | To meter usage against your monthly limit and to keep the service from being abused. | As long as your account exists. |
| Product analytics — events such as “a task started”, “a task failed”, which onboarding step you reached. Never page content, URLs, or task text. | To understand which parts of Relay work and which do not. | 12 months. |
| Crash reports — the type of error and the internal stack trace. Never the error message, which can contain a URL or a file path. | To find and fix bugs. | 12 months. |
| Problem reports — only when you press “Report a problem”: what you wrote, plus a recent extract of Relay’s log. API keys, email addresses and your home folder path are removed before it is sent, and you are told the log is attached before you send it. | To diagnose the problem you reported. | 24 months, or until resolved. |
| Your contact details — the name, email address and phone number you approve when you set Relay up. Not your address. | So we can contact you about your account, send you your invite, and reply to you. | As long as your account exists. |
| Waitlist — your email address, if you give it to us. We also record which form on the page you used, and the campaign or site you arrived from, if any. | To email you an invite, and to know which parts of our own site actually work. | Until you ask us to remove it, or until we stop running a waitlist. |
| Website analytics — on relaythis.com only: that a page was viewed, how far down it was read, and whether a signup form was used. No cookie is set and nothing is stored on your device; the identifier tying one visit’s events together is random, held in memory, and gone when you close the tab. We cannot recognise you on a later visit. | To see where our own site loses people, so we can fix it. | 12 months. |
| Downloads — when the app is downloaded we record the time, the version, the invite code in the link if it was used, and a one-way hash of the IP address. Not the IP itself. | To tell “was never downloaded” apart from “downloaded but the install failed”, which need different fixes. | 12 months. |
| Email we send for you — if you ask Relay to send an email, we record that a message was sent, its subject, and a one-way hash of the recipient. We do not keep the recipient address in readable form or the body of the message. | To stop our sending domain being used for spam, which would break email for every user. | 12 months. |
Who else sees your data
We use a small number of providers. We do not sell your data, and we never will.
| Provider | What they receive |
|---|---|
| OpenRouter, and the AI model provider it routes your request to (for example Google or OpenAI) | The contents of the pages Relay is working on, and your task text. This is the AI model doing the work. |
| Cloudflare | Hosts our server and database. Sees the requests passing through it. |
| PostHog (EU infrastructure) | Product analytics and crash reports. No page content. |
| Resend | Sends email — invites, notifications, and any email you ask Relay to send. |
| Twilio | Only if you turn on SMS or WhatsApp notifications: your phone number and the message. |
Some of these providers operate outside the UK. Where data is transferred abroad, it is done under the safeguards required by UK data protection law, such as the International Data Transfer Agreement or an adequacy decision.
Our lawful bases
- Performance of a contract — running your tasks, and the account, metering, usage limits and contact details needed to provide the service to you and to reach you about it.
- Legitimate interests — product analytics, crash reports, and abuse prevention, so that Relay works and is not used to harm others. You can object to analytics at any time (see below).
- Consent — the waitlist, problem reports, and optional SMS or WhatsApp notifications. You can withdraw consent at any time.
Turning analytics off
Set RELAY_TELEMETRY=0 in Relay’s environment file (~/.relay/.env)
and restart Relay. Nothing further is sent. Relay works exactly the same.
Your rights
Under the UK GDPR you have the right to access the data we hold about you, to have it corrected, to have it deleted, to restrict or object to how we use it, and to receive a copy in a portable form. Email privacy@relaythis.com and we will respond within one month.
Email us from the address you gave Relay and we can find your records. If you never gave us one, tell us your installation ID (Settings → About) instead.
If you think we have handled your data badly, you can complain to the Information Commissioner’s Office at ico.org.uk. We would rather you told us first, and gave us the chance to fix it.
Children
Relay is not intended for anyone under 18, and we do not knowingly collect their data.
Changes
If we change this policy in a way that materially affects you, we will tell you in the app before the change takes effect — not only by quietly updating this page.