SOC 2 Type II
Audit underway; report available under NDA on completion. Controls are operating now — the certificate is catching up to the practice.
This page is written for the person doing the diligence — your controller, your IT reviewer, your bank's questionnaire. No marketing claims: what Vernier can touch, what it can't, what it stores, and who supplies the data. If a question isn't answered here, ask us and we'll answer it in writing.
PUBLIC DATA IN · EVIDENCE OUT · NOTHING ELSE CONNECTED
Vernier never collects, stores, or requests private keys, seed phrases, or wallet connections. You register addresses — public strings anyone can see — and nothing more.
Vernier is not a wallet, exchange, or money transmitter. It cannot hold, route, or touch funds. There is no balance with us, and no transaction we could initiate, delay, or block.
Vernier holds no signing capability of any kind. Every integration reads public data. If our entire system were compromised, the blast radius would be a reading — never your money.
Everything Vernier keeps, why it keeps it, and how it's protected. Nothing is stored that isn't listed here.
Most software lets you overwrite yesterday. Evidence can't work that way. Every entry in your Vernier record is written once, dated, and kept — corrections are filed beside the original as addenda, never over it. That's what makes the record worth showing to a bank, an auditor, or a court: it can prove it hasn't been rewritten. And the year-end binder goes further — every record folds into one re-verifiable hash, so if anything underneath were altered, verification would say so, and name the record that moved.
EACH ENTRY SEALS THE ONE BEFORE · CORRECTIONS ARE ADDENDA · EXPORTS CARRY THE WHOLE CHAIN
Vernier compiles findings from independent providers — the same categories of source used across the financial industry. Here's what each category receives from us: an address, and nothing else. Never your name, your business, or why you asked.
Audit underway; report available under NDA on completion. Controls are operating now — the certificate is catching up to the practice.
AES-256 at rest, TLS 1.2+ in transit. Provider API keys held server-side only — never in the browser, never in exports.
Role-based access, org isolation, least-privilege internally. Production access is logged and reviewed.
Data resides in US regions. EU expansion is a deliberate future decision with GDPR designed in — not a default.
A current list of every sub-processor and data supplier, with what each receives, is maintained on the sub-processors page.
Found something? security@vernier.finance. We acknowledge within 48 hours, and we don't pursue good-faith researchers.
Plain English above; specifics below. Written to answer a vendor questionnaire before it's sent — and where a claim can't be verified from outside yet, it says so.
Security questionnaires, architecture walk-throughs, vendor reviews — this is the part of the job we don't mind. Answers in writing, from the people who built it, in whichever language your reviewer prefers.
security@vernier.finance