Security
For whoever vets a contractor before the deal: how the site and data are protected and what we commit to when handling your access. Each commitment can be written into the contract.

Found a vulnerability — write to us
The machine-readable contact lives at /.well-known/security.txt per RFC 9116. Security reports go to the same address as everything else: hello@dbit.one.
- We reply within 24 hours and confirm receipt.
- We do not pursue researchers acting in good faith: no data exfiltration, no availability damage, no touching other people’s accounts.
- We tell you what was fixed and when. Critical issues come first, the rest in order of priority.
What is visible from outside
Everything below is verifiable without us: securityheaders.com, ssllabs.com or a plain curl. You see the result yourself, as of today rather than as of the day this page was last updated.
Visitor data
The site has no persistent store of personal data — not out of strictness, but by architecture: there is nothing to lose.
- A submitted form is delivered as a message to our working chat and is not saved in any site database.
- The IP address is used only for rate limiting — no more than five submissions per ten minutes — and is held in memory for those ten minutes.
- Analytics does not load until the visitor consents: before that there is not a single third-party script or analytics cookie on the page.
- The form is protected by a hidden honeypot field and server-side validation. There is deliberately no CAPTCHA: it filters out humans as effectively as bots.
Development and deployment
- Every commit passes type checking, linting, a build and a content check before it can reach the server.
- Dependency updates arrive as automated pull requests weekly and go through the same checks.
- A new version is built into a separate directory and swapped in with two renames — the site never serves broken pages mid-build.
- A health check follows every deploy. If the new version does not respond within thirty seconds, the previous one is restored automatically.
Handling your access
These are commitments, not settings: they cannot be verified from outside, but they can be written into the contract — and we agree to that.
- We work under individual accounts with the minimum sufficient rights. We do not create shared “team” passwords.
- Secrets are exchanged through a password manager or your own perimeter, not as a message in a chat.
- When the work ends we ask you to revoke access and confirm that nothing was left behind on our side.
- Production data is not copied onto working machines: debugging runs on anonymised sets.
- The NDA is signed before the first substantive call, not after.
Who to write to
For security questions, a DPA, the subprocessor list or an NDA — hello@dbit.one. The founder answers, not a support desk.