The standard door

State what you need. A person reads it.

Not a chatbot, not a router, not a form that disappears into a queue. One sentence about the outcome you are after, filed to a named human here — and nothing about you is matched, ranked or passed on without somebody on each side agreeing to it.

What the panel does, and what it refuses

It drafts a message in your own mail client. You see the exact bytes before they leave, and you are the one who sends them — which is why it can honestly say it makes no network calls of its own. It stores nothing: the draft dies with the tab. It sets no cookie, loads no third party and carries no pixel. Those are not policy sentences. A test greps the served bundle for fetch, XMLHttpRequest, sendBeacon and every storage API, and the build fails if one of them appears.

A door with nobody behind it refuses to render at all. If the script cannot name an accountable human it shows nothing rather than collecting into a void, which is the only honest behaviour available to an intake surface that has no server yet.

Why every property in the group has the same one

The same dependency-free script runs on each of our properties, and each files to its own named human rather than to a shared inbox. That is deliberate: the queue belongs to the property you arrived at, not to the parent. If you would rather pick a specific door — press, partnership, engineering — /contact/ lays them out. If you do not know which one you want, this page is the one to use.

The widget is the Mesh Concierge, built by Magician, a portfolio company. We run the version they publish, byte for byte, and a test in this repository fails if our copy drifts from theirs.