Privacy.

Qloo scores the roster and the pitched works. Crossfeed sends it only public names and Qloo’s own IDs:

• the names of shows and works to look up: the roster’s shows, the launch or its comps, the past guests’ works, and each pitched book, film, TV show, or podcast;
• Qloo’s IDs for those shows and works, to rank them, compare their tags, and check demographics.

Never a pitch’s text, a guest’s name, an email address, or a sender’s details. A pitch with no public work is set aside, and a work title that holds an email address, or the guest’s or sender’s name, isn’t sent. Requests carry Crossfeed’s key and nothing about you. A network that adds its own Qloo key sends its requests with that key instead, to the Qloo host it chose. Qloo’s terms let it improve its service from the anonymized lists of entities sent to its recommendation endpoint.

Claude Haiku 5.5, through Anthropic’s API, runs the agent, the topic ranking, the pitch reader, and the pitch ranking. It gets:

• the launch’s name or its comps, the roster’s show names and descriptions, and what Qloo returned for them;
• the answers you give the agent, and the slot values Crossfeed works out from your downloads and CPM;
• for the inbox, each pitch as you load it, its sender and subject included, and the past guests you name;
• for each pitch run’s pitch ranking, each pitch’s subject and up to the first 600 characters of its text, never its sender, with the show’s name and the past guests’ works, and nothing from Qloo.

The sample inbox is made up. Real pitches would send their text and senders to Anthropic, so load only pitches you’re allowed to share.

• In your browser: one cookie, __Host-crossfeed_member, which holds your session’s token and is sent only to Crossfeed, over HTTPS. It’s HttpOnly and lasts 30 days, renewed while you use Crossfeed, or a day for a guest. There are no analytics, ads, or third-party scripts.

• With an account: your name; your passkeys’ public keys, each with the browser it was added from; and only hashes of your session and recovery code. The networks you create or join, with your role in each and when you joined and last opened it.

  Invite links are kept only as hashes, with who made each, who used it, and when, and are deleted once they expire, seven days after they’re made. A network’s API keys are kept only as hashes, with each key’s name and first characters, who made it, when, and the last minute it was used.

  Each network’s roster, CPM, and inbox are kept in its own storage, with the member who approved each reply, and each of its launches in storage of its own: its runs, a copy of the roster and CPM each run ranked, with their Qloo records, the name of the member or API key that started each run, and of the member who approved each insertion order, and when. Only the network’s members and its API keys can open them.

  A network’s own Qloo key, if an owner adds one, is kept encrypted in the network’s own Qloo storage, with the host it’s for and its last four characters, the only part of it anyone is shown. That storage also caches the answers to the network’s Qloo calls and counts them, apart from every other network’s.

  Signing in as a guest asks for nothing. Every guest is signed in as one account they all share, Guest, which has no passkey or recovery code; Crossfeed keeps a hash of each guest’s session, for a day, and the time of each guest sign-in, with nothing else, to count them. Everything guests make, in the guest network and in the networks guests create, such as rosters, launches, runs, inboxes, approvals, API keys, and invite links, is seen and changed by everyone who signs in as a guest, and stays until one of them deletes or replaces it, or until it’s cleared, every day at 12:00 UTC.

• Uploads: a file you upload is read in your browser, or by Crossfeed when a program sends it to the API. A roster file’s text is sent and imported like pasted names; of pitch emails, only each one’s sender, subject, and text are sent, never its attachments or other headers. The files themselves aren’t kept.

• Shared by every network: Qloo’s responses with the requests they answered, cached with no expiry in one cache that every network without its own Qloo key shares. A call another network made first is answered from it, and its evidence says the cache was hit, so a hit can show that another network looked up the same name; nothing else of theirs is shown, and the cache is never published.

  Also shared: the sample launch’s stored run, which the guest network’s replays when Qloo can’t be called; the guest network’s sample launches, runs Crossfeed captured once and loads each day; and each network’s counts for the day against the limits in the beta terms.

• In the logs: one line per Qloo call and per model call, with its timing and counts, and one per run. They hold no roster, pitch, or address.

Crossfeed never stores your IP address or writes it to its own logs. When the page connects to its agent, the address is hashed with a secret salt, and the hash stays with the connection. The day’s counts are kept under a hash of that hash and the UTC day, and earlier days’ counts are deleted. Sign-in requests are counted for a minute under the salted hash. Guest sign-ins are counted for everyone together, with no address. Cloudflare, which runs Crossfeed, also records each request the Worker serves in its own logs.

Earlier days’ counts are deleted; cached Qloo responses are kept, and never published. The standalone demo, retired on 28 October 2026, kept each visitor’s session in storage of its own: no browser can reach those sessions now, but their storage stays.

Leaving a network, or being removed from it, deletes your membership at once, and your open pages of it close. Crossfeed keeps only a note that you were in it, so deleting your account later forgets your name there too. What you added to the network stays with the network.

Deleting a launch, which any of the network’s members can do, wipes its storage: its runs, insertion orders, the roster copies, and their Qloo records. Removing a network’s own Qloo key, which only an owner can do, wipes its Qloo storage at once: the key, its cached answers, and its counts. Deleting a network, which only an owner can do, deletes its memberships, invite links, and API keys at once, then wipes its own storage, each of its launches’, and its Qloo storage. A wipe that fails is tried again by the next hourly cleanup, which also deletes expired sessions, sign-in challenges, and invite links.

Deleting your account, on your account page, deletes your account with its name, passkeys, recovery code, sessions, and memberships at once. What you did in a network stays with it, but not your name: the launches of the networks you’re in, or were in before, say “Former member” on the runs you started and the orders you approved, and the replies you approved no longer say who did. The API keys and invite links you made are revoked at once too, as they are when an owner leaves a network, is removed, or is made a member. A network that can’t be reached at once forgets your name at the next hourly cleanup. It’s refused while you’re a network’s only owner.

“Sign out everywhere” deletes every session of yours.

Every day at 12:00 UTC the guest network is cleared, and so is what guests made beyond it: the networks only the guest account owns are deleted, and wiped as a deleted network is, the guest account leaves the networks it shares with members who have accounts, and the API keys and invite links it made are deleted. The guest accounts of their own that guest sign-ins made before go at the first of these clearings, with the networks only they own and the API keys and invite links they made.

Crossfeed runs on Cloudflare Workers, which hosts the app and its storage. Cloudflare, Qloo, and Anthropic handle what reaches them under their own policies: Cloudflare’s, Qloo’s, and Anthropic’s.