What changed, 8 October to 20 November 2026. We corrected this policy where it did not say what is kept or who sees it. Newest first; the changelog (opens in a new tab) lists every change.
- 20 November. Page views are counted only by our own cookieless analytics at insights.ochk.io; no third-party analytics service counts them.
- 31 October. An emailed team invite keeps the invitee's address on the invite and shows it to the team's managers, the email goes through our email provider (Resend), and its link carries the team key only sealed under a one-time code.
- 29 October. The browser extension is described. Deleting your account removes the sealed vault key and the rest of your vault data, keeps payment records under a keyed id, and is refused while you own a team that still has other members.
- 8 October. Your vault is filed under your did:oc, and the vault key is stored on our server, sealed under your passphrase and your recovery code.
§ 01Our principles
Zero-knowledge by design
OC Vault is designed so that OrangeCheck cannot read your data. Encryption and decryption happen in your browser. What OrangeCheck stores is an opaque, double-encrypted blob with no readable item names, types, or contents.
§ 02Information we collect
- Account id. The opaque did:oc of the OrangeCheck account you sign in with; your vault is filed under it
- Sealed vault key. Your vault key, encrypted under your passphrase and under your recovery code, so a new device can unlock; OrangeCheck cannot open it without one of them
- Team email (optional). If you choose to show teammates an email address in a team vault, that address
- Emailed team invite. If a team manager emails you an invite: your email address, which is kept on the invite and shown to the team's managers, and sent with the invite link through our email provider (Resend). The link carries the team key only sealed under a one-time code the manager gives you themselves; OrangeCheck never sees the code or the key. The invite is deleted when a manager revokes it, with the team, or when the account that sent or claimed it is deleted
- Payment records. For paid tiers: the BTCPay invoice id, sats paid, tier, and entitlement expiry. No card number, no billing address
- Encrypted blobs. Opaque ciphertext filed under your account id — OrangeCheck cannot decrypt it
- Per-item metadata. One row per stored item, carrying its opaque envelope id and a last-updated timestamp. That means we CAN see how many items you store and when each last changed — the count is what enforces the per-account item ceiling in the service limits, and the timestamp is what lets a second device know which items to re-sync. We cannot see what any item is: not its contents, not its name, not its type. This entry previously appeared on the "what we cannot see" list, which was wrong.
- Access tokens. For developer / CLI / CI access: an SHA-256 hash of each token, an optional label, the granted scope (read or read-write), creation / last-used / optional expiry timestamps. We never store the token itself — only its hash.
- Technical data. IP address and request metadata, for security and rate limiting
§ 03What we cannot see
- The contents of any vault item
- The names, titles, or types of your items
- Your vault key in usable form, your passphrase, or your recovery code — we hold the key only sealed under them
- Your access tokens (only the SHA-256 hash is stored)
§ 04Vault surfaces (web, extension, CLI, SDK)
Same vault, same zero-knowledge guarantee
The same encrypted vault is reachable from the web app, the browser extension, and the CLI and SDK. The zero-knowledge guarantee — that OrangeCheck only ever holds ciphertext — applies to all of them.
Browser extension (not in a store yet)
The OC Vault browser extension is built for Chrome and Firefox but is not yet in either browser's store; its source is public at github.com/orangecheck/oc-vault-extension (opens in a new tab), and you can build and load it yourself. It fetches the same encrypted blobs the web app does, may cache them as ciphertext in extension storage, and decrypts in its service worker only after you unlock it. The vault key lives in memory and a RAM-only storage.session slot and is never written to disk in the clear; if you turn on passkey unlock, it is also stored sealed to your passkey. The content script that offers autofill receives only one entry's username and password at fill time; it never receives the vault key or the entry index. The extension talks only to vault.ochk.io, and to ochk.io for sign-in: no analytics, no telemetry, no remote code.
Developer platform — access tokens, CLI, SDK, GitHub Action
For headless access (oc-vault CLI, the @orangecheck/vault-core SDK, CI / GitHub Actions), you may mint access tokens at vault.ochk.io/vault/developer (opens in a new tab). A token authorizes transport only — it lets the caller fetch your encrypted blobs and the passphrase-wrapped escrow, and (for tokens minted with a write scope) write new ciphertext. A token carries no key material: a leaked token yields only ciphertext, the same thing the server already holds. The passphrase still performs decryption in your local process and is never transmitted. We store only the SHA-256 hash of each token; tokens can be revoked at any time from the same page.
§ 05Cookies & analytics
No cookies of vault.ochk.io's own. The family sign-in cookie oc_session (set by ochk.io: HttpOnly; Secure; SameSite=None; Domain=.ochk.io; 30 days) and the appearance cookies oc_theme, oc_skin, oc_motion and oc_logo (your logo choice, set only when you open a page with ?logo= in its address) apply here. Your vault data lives in your browser's IndexedDB, under your account. Page views are counted only by our own first-party, cookieless analytics at insights.ochk.io, which is sent the page's origin and path and nothing more of its address. No third-party analytics service counts them, and there are no advertising or tracking cookies.
§ 06Data retention
- Encrypted blobs. Kept while your account is active; you can delete the whole cloud copy at any time from settings
- Sealed vault key. Kept so a new device can unlock; deleting the cloud copy does not remove it, and deleting your account does
- Payment records. Retained as required for accounting and entitlement verification; when your account is deleted they stay under a keyed id, not your account id
- Deleting your account. Removes your encrypted blobs, devices and grants, sealed vault key, access tokens, one-time shares, the teams you own alone, and your seats and invites in other teams. It is refused while you own a team that still has other members
- Request logs. Held by our hosting provider (Vercel) for its own short retention window; rate-limit counters keyed by IP expire with their window
§ 07Data security
Client-side AES-256-GCM encryption, HTTPS in transit, and a server that only ever holds ciphertext. No method of storage is perfectly secure — we use reasonable measures but do not warrant security; see the Terms of Service. Because of the encryption design, a compromise of OrangeCheck infrastructure exposes ciphertext, not your secrets.
§ 08Your rights
Access · correction · deletion
- Access & portability. Request a copy of your personal information in a machine-readable format
- Correction. Request correction of inaccurate or incomplete information
- Deletion. Request deletion of personal information we hold (data published to public networks cannot be deleted by us — see retention)
- Objection. Object to or restrict processing in certain circumstances
- Withdraw consent. Withdraw consent where consent is the legal basis for processing
To exercise any right, email contact@ochk.io. We respond within 30 days.
§ 09International transfers
OrangeCheck is operated from the United States. If you access OC Vault from elsewhere, your information may be transferred to, stored, and processed in the US or other countries where our service providers operate. For users in the EEA, UK, or Switzerland, we rely on appropriate safeguards for international transfers.
§ 10Regional rights
CCPA · GDPR · UK · other
California (CCPA / CPRA)
- Right to know the categories of personal information collected
- Right to delete and to correct your personal information
- Right to opt out of sale or sharing — we do not sell or share personal information
- Right to limit use of sensitive personal information — we do not collect sensitive PI as defined by the CPRA
- Right to non-discrimination for exercising your rights
Europe (GDPR) & United Kingdom (UK GDPR)
- Legal basis. Consent, contract performance, legitimate interests (security, abuse prevention, service improvement), and legal obligations
- Your rights. Access, rectification, erasure, restriction, portability, objection, and withdrawal of consent
- Supervisory authority. Right to lodge a complaint with your local EU/EEA data-protection authority, or the UK ICO
- EU/UK representative. If and when required, we will designate an Article 27 representative and publish the details here
Other jurisdictions
If you reside in a jurisdiction with a comprehensive privacy law — including Brazil (LGPD), Canada (PIPEDA / Law 25), Australia, Japan (APPI), South Korea (PIPA), Switzerland (FADP), or any U.S. state privacy law — you have the equivalent rights of access, correction, deletion, portability, and objection. Email contact@ochk.io and we will honour applicable rights under the law of your residence.
§ 11Children's privacy
OC Vault is not intended for children under 13 (or the applicable age of digital consent in your jurisdiction). We do not knowingly collect personal information from children. If you believe we have, email contact@ochk.io immediately and we will delete it.
§ 12Changes to this policy
- We will update the "last updated" date above
- For material changes, we will provide prominent notice on the website
- Continued use after changes constitutes acceptance
In short. End-to-end encrypted; orangecheck stores ciphertext only and cannot read your vault contents.