Relay privacy policy

Last updated 8 November 2026

Who this covers

This policy is from Chris Brendan (“I”, “me”), who makes Relay. It covers the Relay app for Mac, the Relay iPhone app and this website.

What stays on your Mac

Relay keeps what it knows on your Mac:

• Your board, cards, comments, attachments, canvases, routines, Claude's memory and each card's workspace, in ~/Library/Application Support/Kanban. The browser profiles Claude uses, with the sites you sign in to in them, are kept there too.
• A transcript of each card's work with Claude, including what its tools returned, in ~/.claude/projects. Claude Code writes these, and Relay uses them to pick a card's conversation back up.
• Relay's settings, and which version of the terms you accepted and when, in the app's preferences.
• In your Mac's Keychain: your Claude sign-in (Claude Code's own), the keys for pairing your iPhones, and your TypeSafe key if you added one.

I don't have a copy of any of this, and Relay doesn't send it to me. Apart from your beta sign-in, below, Relay has no account with me, and it has no analytics, tracking or crash reporting of its own.

Your beta sign-in

Relay is in a closed beta, so you sign in with an email address I've approved. When you request access on this site, or sign in to Relay, I store in Supabase, a database service from Supabase, Inc., in its Mumbai, India region:

• your email address;
• whether it's approved;
• when you requested access, when you were approved, and when Relay was last seen signed in;
• the version of Relay you last signed in or checked in with;
• when your last sign-in code was sent;
• for each Mac you're signed in on: a scrambled copy (a hash) of its sign-in token, the device id Relay sends, its version of Relay, when it signed in and was last seen, and when its sign-in was revoked, if it was.

Supabase Auth, part of the same service, also keeps a user record for your email and a record of its sign-in sessions, which are ended as soon as your code is checked. Every few hours Relay checks that your sign-in still works, sending your Mac's sign-in token, its device id and Relay's version through this site to Supabase. If your access is switched off, or your version of Relay is too old, the check locks Relay until it's sorted out.

To stop abuse, such as someone guessing sign-in codes or flooding the request form, the site also keeps counters in Supabase of recent requests, sign-in emails and code guesses. Each entry holds the email address or IP address it counts, or both, and the time. Entries are deleted after two days.

Sign-in codes are emailed by Supabase Auth through Resend, an email delivery service from Resend, Inc., from hello@letsrelay.app. Resend handles them under its own policies. When I approve you, I email you myself. Everyone at a few email domains I've chosen is approved without asking. For them, the record above is created the first time they sign in successfully, under their address without any +tag.

I keep this record while you're in the beta. To have it deleted, email me. Deleting it also deletes your Supabase Auth user and the sign-in record for each of your Macs, so Relay is signed out on its next check. The abuse counters above expire on their own within two days.

Claude and Anthropic

Relay runs Claude through Anthropic's Claude Agent SDK, signed in with your own Claude account. When Claude works on a card, what it needs goes to Anthropic: the card and its thread, your instructions, and whatever Claude reads to do the task, such as files and images you attach, files on your Mac, web pages and connector results. The copy of Claude Code that Relay bundles can also send usage and error data to Anthropic and its service providers. Relay doesn't turn this off.

Anthropic handles all of this under its terms and privacy policy for your account, not this one. I don't see it.

Websites, apps and connectors Claude uses

On your instructions, Claude can search the web, open websites in its own Chrome profile using the sign-ins you gave it, use apps and files on your Mac, and use connectors: the ones on your claude.ai account, and any server you add yourself.

Relay also makes some requests by itself:

• Before showing you a link or image Claude cites, Relay opens it to check it works.
• Routines Claude sets up on a card run on a schedule without you. Their checks can fetch web pages, open pages in Claude's browser with your sign-ins there, and run programs from the skills you've switched on, which may contact outside services.
• When you open a canvas, Relay loads its pictures straight from the sites they're on, which shows those sites your IP address.

Each of those sites and services receives what's sent to it, and handles it under its own policies.

Update checks

Relay checks for updates when it opens and every 5 minutes after that, using Sparkle. Each check downloads the update feed from Cloudflare R2, a storage service from Cloudflare, Inc., and an update downloads from there too. Like any web request, a check reveals your IP address and basic details such as the app's version. Relay doesn't send anything else with it: Sparkle's optional system profile is switched off.

The iPhone app (optional)

Using Relay on your iPhone is off until you switch it on in Settings → iPhone. While it's on, your Mac connects to a relay server, and so do the iPhones you pair, so a phone can reach your Mac from anywhere. I run that server on Cloudflare Workers, or you can enter the address of your own.

What your Mac and phones send each other, including the board and what Claude says, is encrypted end to end, so the server can't read it. To do its job, the server stores:

• a random id for your Mac's room, and the public keys of your Mac and paired phones;
• an entry for each paired phone, named just “iPhone”, never the phone's real name;
• each phone's push notification token;
• the latest encrypted copy of your board, so a phone can catch up;
• encrypted messages from your phones waiting for your Mac, until your Mac has them, or for at most 30 days.

While iPhone access is on, your Mac keeps the encrypted copy of your board up to date on the server, whether or not a phone is paired. The server also knows which devices are connected right now, but doesn't store that.

Notifications go through Apple's Push Notification service. The text Claude wrote is encrypted inside each notification and only your phone decrypts it, so Apple and the server see only a generic “Claude has an update”. Cloudflare sees connection details such as IP addresses, as for any web service.

The server has Cloudflare's Workers Logs switched on. They record every request to it, including its address, which contains your room's id, and the server's own messages, which can include a phone's device id when a notification fails. Cloudflare keeps these logs for a limited time under its own policies.

Apart from waiting messages, nothing on the server expires by itself:

• Removing a phone while your Mac is connected takes it off the server's list and deletes its token and waiting messages.
• Unpair All, which Settings shows once a phone is paired, deletes everything the server holds for your room while your Mac is connected. Relay then starts a new room, and while iPhone access stays on, it uploads your encrypted board to that room too.
• Switching iPhone access off stops new uploads, but deletes nothing already on the server.

To have the server's copy removed completely, switch iPhone access off and email me your room id. It's the room value in ~/Library/Application Support/Kanban/remote/remote.json.

Jev by TypeSafe (optional)

If you add your own TypeSafe API key in Settings, Relay uses TypeSafe's Jev to tell whether a message you wrote without @claude is meant for Claude. For each such message it sends TypeSafe the message, the card's title, group and column, and up to 10 earlier messages on the card. Without a key, nothing goes to TypeSafe. TypeSafe handles this under its own terms.

This website

This site is hosted by Vercel. It runs no analytics or tracking scripts and sets no cookies. Like any host, Vercel processes your IP address and browser details to serve the site and protect it from abuse.

The Download button sends you to the newest version on Cloudflare R2. If you request access, the site sends the email you enter, and counts the request against your IP address, in Supabase, as described under “Your beta sign-in”.

When you contact me

If you email me, for example with feedback or a bug report, I keep your email and what you send so I can reply and improve Relay. I don't sell it or share it, except where the law requires.

Your choices

Your data is on your devices, so you can see, export or delete it there. To remove all of it, in this order:

1. Email me to delete your beta sign-in record, described above.
2. In Relay's Settings, remove your TypeSafe key, and press Unpair All under iPhone if it's there. Then switch iPhone access off.
3. If you've ever switched iPhone access on, note your room id, the room value in ~/Library/Application Support/Kanban/remote/remote.json, and email it to me so I can delete the server's copy.
4. Quit Relay, and delete the app and ~/Library/Application Support/Kanban.
5. Delete the card transcripts in ~/.claude/projects. Their folders are named after each card's workspace inside the folder above. Other Claude Code projects keep theirs there too, so delete only Relay's.
6. Delete Relay's preferences, which include the terms you accepted: defaults delete local.kanban in Terminal.
7. In Keychain Access, delete the items named “Kanban iPhone keys” (service local.kanban.remote). Your Claude sign-in belongs to Claude Code; sign out there if you want it gone.
8. Delete the Relay app on your iPhone, which removes its copy of your board and cards. Its pairing is kept in the iPhone's Keychain and can outlast a reinstall, but stops working once the phone is unpaired.

For what Anthropic holds, use your Claude account's privacy settings. You can also ask me what I hold about you, or ask me to delete it, by email.

Children

Relay isn't meant for children, and needs a Claude account, which Anthropic only gives adults.

Changes

If Relay starts handling data differently, I'll update this page and its date first, and tell testers about any big change.

Contact

Questions or requests about privacy: hello@letsrelay.app.