Security model
What we sign, what we store, and who to tell if something looks wrong.
Signing & verification
Every notary receipt is signed with Ed25519 and hash-chained to the receipt before it — tampering with any past receipt breaks every signature after it, not just the one record. The signing key never leaves the process that holds it; the public key is served openly at /notary/health so anyone can independently verify a receipt without trusting us to grade our own work. The full receipt chain re-verifies itself, fresh, on every load of /notary/verify-live — nothing cached, nothing pre-computed for display.
Data handling
We operate our own infrastructure directly rather than routing customer data through third-party SaaS. Business email runs on Google Workspace. What we collect and why is covered in full in our Privacy Policy — in short: only the fields you send us to complete a request (an entity name to screen, a track record to grade), and payment metadata required to settle an x402 charge. We do not sell data.
Operational resilience
Public-facing services run under process supervision that automatically restarts a crashed or killed process — a dead service comes back on its own, typically within a minute, without a human paging in. We do not publish exact infrastructure topology (hosting provider, network layout, internal ports) here, in line with normal practice for not publishing a target map; what we do publish is behavior you can verify yourself at /status.
When a verdict is wrong
A signed receipt is not a claim that we can never be wrong — it's a claim that you can check our work against the named source. If a verdict doesn't hold up against the source it cites, you can file a dispute against it; the resolver is re-run independently and, if it overturns, the filer is owed a payout from an on-chain correctness bond. Full accountability model at /governance.
Report a security issue
Found a real vulnerability — a way to forge a signature, bypass payment verification, or access data that isn't yours? Email info@stillosdigitalholdings.com with details and, if possible, steps to reproduce. We don't yet run a formal bug bounty program; we do respond to and fix real reports.