Privacy

Updated 4 September 2026

This policy covers this website, every *.moxlade.com corpus and the MCP services reached through them. It is written to be read, not to be scrolled past.

These websites

We measure which pages are read, using PostHog in its cookieless mode: the page loads a script from PostHog and reports the page you are on, the page you came from, the size of your window and the kind of device. It stores nothing in your browser — no cookie, no local storage, no session storage. The visit is counted against a rotating hash PostHog derives on its own servers, so you are not recognisable to us on a later visit and we cannot follow you across days. We do not use it to record your screen. If you block it, the pages work exactly the same. There is no consent banner because nothing is stored to consent to.

A corpus subdomain does set cookies, and they are not analytics. Our authentication provider, Clerk, sets them on every page there so a browser that is already signed in stays signed in; they are what makes the service work rather than something we chose to learn about you, and they go when you sign out. This site, at the apex, sets none. Fonts are served from our own origin on both.

The server keeps ordinary access logs (IP address, user agent, path, time) for security and capacity, rotated on the usual schedule.

Getting a token

Today a token is issued by email: you write to us, we create it against an account we make for you, and we keep your email address so the token can be revoked and so we can tell you about changes to the service. When self-serve sign-in is enabled, sign-in is handled by our authentication provider, Clerk, which stores your email address and the session in your browser; we receive your account id and email.

Using the service

Every tool call is logged against your token: which tool, the workspace it named if any, a hash of the arguments (not the arguments), how long it took, and whether it succeeded or why not. This is what enforces the caps, tells us what is being used, and lets us find a runaway agent. Argument values themselves are not stored.

If you have a workspace, its files and its captured outcomes belong to that workspace and are visible only to its members. They are never used to answer another tenant’s questions.

Paying

Payments, when open, are taken by Stripe on Stripe’s pages. We receive the payment reference, the amount and the email you gave Stripe, and we never see a card number.

The corpora

The data a service answers from is compiled from publicly visible postings and public professional profiles. It is third-party data about businesses and professionals, held to answer questions in aggregate or about a specific posting a user is already working on. If you are the subject of a public profile or posting and want it removed, write to us with its URL. We remove it and say when it is done.

Where it is stored

On a dedicated server in Germany. Stripe and Clerk process their parts on their own infrastructure, in part in the United States.

How long

Account and token records: until you ask us to delete them or the service closes. Call logs: as long as they are useful for caps and capacity, then deleted in bulk. Access logs: on rotation.

Your rights

Ask for a copy of what we hold about you, ask us to correct it, or ask us to delete it. One email is enough; no reason required. If you are in the EU or UK you may also complain to your national data protection authority.

Changes

The date at the top is the current version. A material change reaches token holders by email before it takes effect.

Contact

[email protected] — Moxlade.