Updated Mar 30, 2026
The site keeps analytics to a minimum. Standard route views, outbound link clicks, and contact submissions may be recorded to understand whether the surface is working as intended.
Contact form submissions include the fields entered into the form, a timestamp, and limited request metadata needed for validation, spam protection, and routing.
Messages sent through Contact are validated server-side, checked against a rate limit, and written to a protected submission log. If a forwarding webhook is configured, the same record may also be sent to that endpoint for response handling.
Messages that fail validation or trigger the honeypot field may be discarded without response.
The site is designed to avoid excessive tracking. No advertising network, heatmap layer, or third-party surveillance script is loaded by default.
If analytics is enabled later, it will remain limited to route-level measurement and essential product decisions.
Proof, Select updates, and Signal notes keep timestamps so content remains readable in context. Contact submissions may be retained only as long as needed to answer the route or maintain a clear record of the exchange.
Legal retention may extend this period when required.
Select and other external routes may lead to third-party sites. Once a user leaves this domain, the privacy rules of that external destination apply.