Security
What we hold. What we cannot see.
OC Vault encrypts every item in your browser. So a new device can unlock, your vault key is also stored with us, sealed under your passphrase and your recovery code — ciphertext we cannot open. A compromise of orangecheck exposes encrypted blobs, not your secrets; a weak passphrase you chose yourself is the one thing an attacker holding them could try to guess offline.
On this page+
What we hold
- Your orangecheck account id (a random did:oc), which your vault is filed under
- Your vault key, sealed under your passphrase and under your recovery code — ciphertext we cannot open without one of them
- When you link a device, your vault key sealed to that device’s key, which only that device can open, and the public key and name of each device you link
- For paid tiers: the BTCPay invoice id, sats paid, tier, and entitlement expiry
- An opaque, double-encrypted blob per item — your synced vault, as ciphertext
- One row per item, carrying its opaque id and a last-updated timestamp — so we can see how many items you store and when each last changed. The count enforces the per-account item ceiling; the timestamp tells a second device what to re-sync
- When you share an item once: its ciphertext and which account sent it, until the link is used up or expires
- When you email a team invite from here: the invite link passes through our server and our email provider (Resend) to be sent, and is not logged. It carries the team key only sealed under a one-time code your browser shows you and never sends; you give the code to the invitee yourself
- For teams: which accounts are members, and pending invites, with the address an emailed one went to
- Request metadata (IP, timestamps) for rate limiting — counters expire with their window, and request logs stay only in our hosting provider's own short retention
What we cannot see
- The contents of any vault item
- The names, titles, or types of your items
- Your vault passphrase or recovery code — neither is ever sent to us
No one can recover it for you.
The encryption design that prevents orangecheck from reading your data also prevents orangecheck from recovering it. If you lose your vault key and all recovery factors, your data is permanently unrecoverable. Keep your own backups of anything critical.
How to report
Please don’t open a public issue for anything exploitable. Until a fix ships, that puts everyone using it at risk.
Email security@ochk.io, or open a private security advisory on the most relevant orangecheck (opens in a new tab) repository.
What happens next
- A reply. We aim to reply to every report within 30 days. We can’t promise a time to a fix yet.
- Disclosure once the fix ships. We publish an advisory and credit you, unless you prefer not to be named.
- Bounty: there is no paid bounty programme yet. We are grateful for responsible disclosure.
The security model in full, with what vault does and does not protect against, is in the docs (opens in a new tab).