decoyrail

Privacy

Nothing flows to us.

Decoyrail exists to control what leaves your machine, so it holds itself to the strictest version of that rule. The binary sends us nothing: no telemetry, no crash reports, no usage analytics, no update checks, no account, no phone-home. There is no server of ours for it to call.

What the binary does with your data

Everything Decoyrail knows lives in local files you can open yourself: the encrypted vault, the policy, the audit log, and the spend meter, all under ~/.decoyrail. The audit log records what your agents did; it never leaves your machine unless you ship it somewhere yourself. Nothing Decoyrail writes is readable by us, sent to us, or held anywhere but your disk.

The only network connections the proxy makes are the ones your agent asked for and your policy allowed. Decoyrail originates no traffic of its own.

When you buy a license

Checkout runs through Lemon Squeezy, the merchant of record. They process the payment under their privacy policy; your card details never reach us. What we learn from an order is your email address and which tier you bought, and we keep that to issue and renew your license. Buying by email works the same way and teaches us the same two things. We do not share it, sell it, or use it for anything else. The license file you get back is verified offline: installing it tells us nothing, and no license state ever touches your traffic.

This website

The site is static pages. We run no analytics and set no cookies. It is served by Cloudflare Pages, so Cloudflare's edge handles the requests the way any host does. The docs pages load one diagram library from cdn.jsdelivr.net; that request goes to that CDN like any script fetch. Nothing on the site reports back to us.

Questions

Ask anything about this policy at [email protected]. To report a vulnerability, use the security policy instead. If this page ever changes, the change lands in the public repo first, where you can read the diff.

Last updated 2026-07-29.