Who receives something, and who receives nothing.

Who receives something

1. Cloudflare

   Terminates TLS and carries every request to our servers through a tunnel. Also sends the emails SalesWolf sends you — sign-in codes and workspace invitations — and delivers what you send through the /contact form to our own inbox. On /contact, runs Turnstile, the check that tells a person from a bot.

   Receives

   All traffic in transit, which is everything you send or receive — including the text you paste and your session cookie. For email, your email address and the content of those messages; for the /contact form, the name, email address, request type and message you send. For Turnstile, the address your browser connects from, a fingerprint of its secure connection, its User-Agent header, and our site key and the page it runs on.

   Route

   Directly, in front of every request; from our servers whenever an email is sent or a Turnstile check is confirmed; and from your browser, which loads Turnstile from Cloudflare's servers when you open /contact. Turnstile sets no cookie.

2. OpenRouter

   Routes our model requests to the provider that serves them. Based in the United States.

   Receives

   The material you ask us to work on — the text of a call, email or document you pasted, the facts already on the deal, and the messages you write to the assistant.

   Route

   Directly, from our servers, whenever a request needs a model.

3. Google

   Serves the language model that reads your material and drafts from it.

   Receives

   The same material, as forwarded by OpenRouter.

   Route

   Through OpenRouter — we hold no direct relationship.

4. Voyage AI (MongoDB)

   Serves the embedding model that lets us find the passages related to a question.

   Receives

   Short passages of your material, converted to numbers for search.

   Route

   Through OpenRouter — we hold no direct relationship.

5. Paddle

   Sells paid seats as Merchant of Record: it is the seller on your invoice, takes the payment and collects the tax. The seller is Paddle.com Inc. for buyers in the United States, Paddle.com (Canada) Ltd for buyers in Canada, and Paddle.com Market Limited, based in the United Kingdom, for buyers everywhere else. It holds your payment details as a controller in its own right, under its own privacy notice.

   Receives

   What you enter at checkout — your name, email address, billing address and payment details — and which workspace the seats are for, and how many. On /pricing, and on the app's Billing page when the workspace owner opens it to subscribe, the address your browser connects from, which Paddle uses to work out your country, and the two plan prices it is asked to show in your currency. Never your deal material.

   Route

   Directly, from your browser: when you open /pricing, when the workspace owner opens the app's Billing page to subscribe (both load Paddle's script from Paddle's servers), and when you buy or manage seats. Those servers may set a Cloudflare bot-protection cookie (__cf_bm) on paddle.com; nothing is set on our domain. Paddle's script tries to add Paddle's own analytics snippet (Paddle Retain), and the security policy of the site and of the app blocks it. From our servers: the owner's email address to prefill checkout, and the subscription's references when the owner changes the seat count, opens Paddle's customer portal or reads the billing history, and when we check a subscription against Paddle's record.

Who receives nothing

The functions a service like this one usually buys from somebody, and what we do instead.

1. Website analytics

   There is none. This site runs no tracker, sets no cookie on its own domain and keeps no record of your visit — so there is nothing to send anyone, self-hosted or otherwise. On /pricing, Paddle's script tries to add Paddle's own analytics snippet (Paddle Retain); the site's security policy blocks it, so it never runs, and the app's policy blocks it the same way on its Billing page. On /contact, Cloudflare Turnstile checks the form for spam and sets no cookie.

2. Databases and backups

   MongoDB runs as a container on infrastructure we operate. No managed database provider holds a copy.

3. Error tracking and monitoring

   Our logs stay in our own database. No monitoring vendor receives them.