LEGAL

Privacy

Last updated 16 November 2026

This page covers the caedos.com website, the Caedos Cloud waitlist on caedos.cloud, Caedos Cloud accounts, signing in and connecting an AI assistant on app.caedos.cloud, and the emails a Caedos Cloud workspace sends you. Caedos Cloud itself, the workspaces and what runs in them, will have its own privacy statement before it opens. The Caedos program you run is covered at the end, briefly: it sends us nothing.

Who we are

Ross Walpole, a sole trader in the United Kingdom, runs this website and caedos.cloud, and decides how the data described here is used (the data controller). Write to [email protected] about anything on this page.

What this website collects

  • This site sets no cookies and has no accounts.
  • Like every website, it receives what your browser sends with each request, such as your IP address, browser and the page asked for. Our host uses this to deliver pages and protect the site. We keep no server logs of our own.
  • It runs no analytics.
  • It has no forms.
  • If you email us, we receive what you send and use it to reply.

The Caedos Cloud waitlist

The waitlist on caedos.cloud ↗ asks for your email address and, if you like, what you'd keep running on Caedos Cloud. We store them, with the time you joined, in a database Cloudflare runs for us, and keep nothing else about your visit. We use them only to tell you when Cloud opens, and to learn what people want from it. Like this site, caedos.cloud itself sets no cookies and runs no analytics. Signing in on app.caedos.cloud sets one, below.

Caedos Cloud accounts

For now we make each account ourselves: you can't sign up on your own yet. An account keeps:

  • the email address it was made for, where its sign-in links go;
  • which Caedos Cloud workspace is yours, once you have one;
  • when its address was first shown to be yours, by your using a sign-in link mailed to it;
  • whether you've stopped your workspace's emails, and when;
  • when it was made, and when it last changed.

Signing in

  • Sign-in links: you ask for one at app.caedos.cloud/account. If the address you type has an account, we email it a link that works once, for 15 minutes. If it hasn't, we send nothing and keep nothing about it. Opening the link changes nothing; the button on the page it opens signs you in.
  • Sessions: signing in starts a session that lasts 30 days from then, or until you sign out. Using it doesn't make it last longer.
  • Kept only as hashes: we keep each link and each session only as a hash (SHA-256) of its secret part, never the secret itself. Signing out deletes the session at once. Links and sessions that have ended are deleted at the next 08:00 UTC after they end.
  • Your IP address: we use it only to count sign-in tries, at most five a minute, and don't keep it.
  • One cookie: signing in sets __Host-caedos-session, on app.caedos.cloud only. It holds your session's secret, goes only over HTTPS and can't be read by the page's scripts. It's strictly necessary: it's how you stay signed in, and signing out clears it. Caedos Cloud sets no other cookie of its own.
  • A record of sign-ins: we log each sign-in, refused link and sign-out with its time and your account's ID, never your address.

Connecting an AI assistant

When you add Caedos Cloud to an AI assistant, such as Claude, the assistant sends you to app.caedos.cloud, where you sign in if you aren't already and allow it. If you sign in there, your sign-in link also keeps that page's address, to bring you back to it.

  • A connection keeps: which assistant it is, by the name and identifier it gives us; your account, which allowed it; when you allowed it; when it last got a token; and when it ends.
  • Its tokens, kept only as hashes: as with links and sessions, we keep each of the assistant's tokens only as a hash (SHA-256). An access token works for an hour. The connection lasts 30 days from the last time the assistant got a token, so one you keep using stays connected.
  • Deleted when they end: an assistant's request waits 10 minutes for you to allow it. Requests, connections and tokens are deleted at the next 08:00 UTC after they end, and disconnecting a connection ends it.
  • Disconnecting: signed in at app.caedos.cloud/account, you can see each assistant you've connected and disconnect it. Within a minute it can no longer reach your workspace.
  • A record of connections: we log each time you allow or deny an assistant, each connection made and each one ended, with its time, your account's and workspace's IDs, the assistant's identifier, and who ended it: you, us, or Caedos Cloud itself, which ends a connection if one of its used tokens is sent again, since it may have been copied. The record never holds a token or your address.
  • Your IP address: some assistants register themselves with us each time they connect. We also use IP addresses to count those registrations, at most ten a minute, and don't keep them. For an assistant on your own computer, that's your address.

Emails from your workspace

A Caedos Cloud workspace has an "Email me" channel, which emails your account's address, and no other, once that address has been shown to be yours.

  • What they carry: what your synths send through that channel, which can be anything they read, such as the text of a page one watches; and Caedos Cloud's own notices: a synth waiting for your OK, with a link to that one action, a synth that stopped, a connection that broke, reasoning that stopped, a test you ask for, and a count of emails held back.
  • How they're sent: as plain text from [email protected], through Resend (below), which keeps each message for 30 days. We keep nothing of a message ourselves.
  • What we keep: for each workspace, how many emails it sent and held back in each hour, for two days. We send at most ten an hour and thirty a day; past those, we hold the rest back and send how many instead.
  • Their links, kept only as hashes: a link to a waiting action works once, for 24 hours. Opening it changes nothing; its Allow or Reject button uses it up. Every email also has a link that stops your workspace's emails, which works for 30 days. Opening it changes nothing; its button stops them, and you can start them again at app.caedos.cloud/account. Each link is deleted at the next 08:00 UTC after it ends.
  • A record of them: we log each time a waiting action's link is used, with the synth's and the action's IDs, each time you stop or start the emails, and each email that fails to send, with your workspace's ID. The record never holds what an email said.

Why, and on what basis

  • Delivering and protecting the site: our legitimate interest in running a website that works and stays up.
  • Replying to your email: our legitimate interest in answering you.
  • Telling you when Caedos Cloud is ready: your consent, given when you ask to hear. You can withdraw it at any time by emailing us.
  • Your Caedos Cloud account, signing in, connecting an assistant and your workspace's emails: to carry out our contract with you, or the steps you ask for before one.
  • Counting sign-in tries and registrations, and keeping a record of sign-ins and connections: our legitimate interest in keeping accounts and the service secure.

We don't sell your data, share it for advertising, or use it to make automated decisions about you.

Who processes it

  • Hosting: Cloudflare serves this site and caedos.cloud, so it processes request data such as IP addresses. It also stores the Caedos Cloud waitlist, accounts, sign-in links, sessions, connected assistants, email counts and links, and the record of sign-ins, connections and emails.
  • Mail: Resend (Plus Five Five, Inc., in the United States) sends our sign-in links and your workspace's emails from caedos.com's own domain, from Ireland, and keeps each message, your address and what it says included, for 30 days in the United States.
  • Email: the providers that carry and store our caedos.com mail receive the messages you send us.

Some of them process data outside the UK, including in the United States. Where they do, the transfer relies on safeguards UK data protection law recognises, such as the UK–US data bridge, the international data transfer agreement, or the UK's addendum to the EU's standard contractual clauses.

Downloads come from GitHub, including the ones our install scripts make, and our community is on Discord. Those sites have their own privacy policies, which apply when you use them.

How long we keep it

  • Your emails: until we've dealt with what you wrote about and no longer need them for it, or sooner if you ask.
  • Your address for Caedos Cloud, and anything you told us with it: until we've told you it's ready, or that it won't be built, or you ask us to remove it.
  • Your Caedos Cloud account: until it's closed. Ask us, and we'll close it and delete your address.
  • Sign-in links and sessions: a link for 15 minutes, a session for 30 days or until you sign out. Each is deleted at the next 08:00 UTC after it ends, or at once when you sign out.
  • Connected assistants: 30 days from the last time each got a token, or until it's disconnected. You can disconnect one at app.caedos.cloud/account, or ask us to. Each is deleted, with its tokens, at the next 08:00 UTC after it ends.
  • The record of sign-ins and connections: for as long as we keep the log, after the connections themselves are deleted. It names you only by your account's and workspace's IDs, which lead to no one once your account is closed.
  • Your workspace's emails: we keep none. Each hour's count of sent and held-back emails is deleted at the first 08:00 UTC after it's two days old. A waiting action's link works for 24 hours and a stop link for 30 days, and each is deleted at the next 08:00 UTC after it ends.
  • Mail at Resend: 30 days, under its own policy.
  • Request data: we keep none. Our host keeps it briefly, under its own policy.

Your rights

Under UK data protection law you can ask for a copy of the data we hold about you, and ask us to correct it, delete it, limit how we use it, object to how we use it, or give it to you in a portable form. Email [email protected], and we'll reply within one month.

If you're unhappy with how we've handled your data, you can complain to the Information Commissioner's Office at ico.org.uk ↗. We'd like the chance to put it right first.

The software

Caedos, the program you run, sends us nothing. It has no analytics, no usage reporting and no accounts. What it stores stays in its data folder on your machine. It connects to what you set up: the model provider whose key you add, the sources and destinations your processes name, the MCP servers you connect, and the public MCP registry when you browse it in the control room. See Security.

Changes

When this page changes, the date at the top changes with it.