Who runs this

Secrets management shouldn't require trusting the operator. Every hosted secrets manager asks you to believe a promise: "we won't look." Pock is built so the promise is unnecessary. Encryption happens on your device, we only ever store opaque ciphertext, and the parts of the system you do have to rely on (key distribution and the code we serve) are published to public, append-only logs where cheating leaves permanent evidence.

The motto across our security page is "verify, don't trust": the goal is that cheating leaves evidence, whether the cheater is an attacker or us.

These are properties of the architecture, not policies we could quietly change. Each is covered in depth on the security page.

• Zero-knowledge, end-to-end encryption. Your vault and shares are encrypted on your device before anything reaches us. We store ciphertext we cannot read, and if you lose your keys we cannot recover your data. That is deliberate.
• Key transparency. Public keys are recorded in an append-only Merkle log with signed tree heads. Clients verify inclusion and consistency proofs, so a swapped key is detectable, including one swapped by us.
• Post-quantum cryptography. Key exchange uses X-Wing, a hybrid of X25519 and ML-KEM-768, with ChaCha20-Poly1305 for payloads, so ciphertext harvested today can't be decrypted by a future quantum computer.
• Verifiable releases. Every release publishes its file hashes to the same append-only transparency log. Anyone can re-hash what we serve and check it against a logged release, so shipping a backdoor would leave permanent public evidence.

Anything the architecture can't guarantee, we document plainly on the privacy page: what metadata we hold, for how long, and who our subprocessors are.

Pock is built and run by an independent developer who stays out of the story on purpose. That choice doubles as a test of the product's central claim: if you have to know who we are to feel safe, the cryptography isn't doing its job.

Every promise on this page is checkable without trusting a name. The key log and release log are public and append-only. The encryption runs in your browser, where you can watch it. A server breach, a rogue operator, and a hijacked deploy all leave the same thing behind: ciphertext.

There are no investors and no growth targets that depend on your data. If that ever changes, the architecture is what keeps us honest.

Questions, security reports, or just checking we answer our email: hello@pock.sh. We read everything.

More of the paper trail: security, privacy, terms of service, and status.