Security & data

Read-only isn't a promise. It's the architecture.

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.

The short version: public data in, evidence out, nothing else connected.
PUBLIC LEDGER SCREENING REPORTS PRICE DATA Vernier READ-ONLY INSTRUMENT THE RECORD EVIDENCE OUT — YOURS TO EXPORT YOUR KEYS YOUR FUNDS YOUR WALLET No path exists. No keys held. No wallet connections. No custody. No way to move money — not for you, not for us, not for anyone.

PUBLIC DATA IN · EVIDENCE OUT · NOTHING ELSE CONNECTED

The boundary, in plain terms

What Vernier cannot do — by design, not policy.

NO KEYS · EVER

Nothing to steal.

Vernier never collects, stores, or requests private keys, seed phrases, or wallet connections. You register addresses — public strings anyone can see — and nothing more.

NO CUSTODY · NO MOVEMENT

Nothing to freeze.

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.

NO WRITE PATH

Nothing to hijack.

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.

What we store

The data register.

Everything Vernier keeps, why it keeps it, and how it's protected. Nothing is stored that isn't listed here.

DATA REGISTER · CURRENTUS-HOSTED · ENCRYPTED
Wallet addresses you registerPublic identifiers, visible to anyone on the blockchain already. Never linked by us to personal identity.AES-256 AT REST · TLS 1.2+
Screening findingsWhat each data provider reported, when, about which address — stored with its source, verbatim.APPEND-ONLY STORE
Memos & statementsThe documents generated from findings. Versioned, dated, exportable by you at any time.RETAINED UNTIL YOU LEAVE
Decisions your team logsWho accepted, declined, or escalated — name, timestamp, optional note. Your governance trail.ORG-SCOPED ACCESS
Your own wallet addressesThe addresses you register as yours — for Inbound Watch and the close. Read-only, public identifiers; never keys, never custody.READ-ONLY · NO KEYS
Payments, invoices & bookingsDetected transfers, invoice matches, and the balanced entries you approve — the close's working record.APPEND-ONLY STORE
Directory listings & confirmationsAddresses you publish (control-proved) and confirmations you opt in. Third-party confirmations surface only as an aggregate above a privacy threshold — never who confirmed.OPT-IN · K-ANONYMIZED
Account & billing basicsEmail, organization, plan. Payment handled by Stripe — card numbers never touch our systems.VIA STRIPE
The append-only ledger

A record you can't quietly edit.
Neither can we.

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.

EM-2041 JUL 14 · SEALED EM-2042 JUL 15 · SEALED EM-2043 JUL 16 · SEALED EM-2044 JUL 16 · SEALED ADDENDUM A FILED BESIDE · NEVER OVER

EACH ENTRY SEALS THE ONE BEFORE · CORRECTIONS ARE ADDENDA · EXPORTS CARRY THE WHOLE CHAIN

Who supplies the data

The watchdogs, on the record.

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.

DATA SUPPLIERS · BY CATEGORYTHEY RECEIVE: THE ADDRESS ONLY
Sanctions screeningChecks against government designation lists (e.g. OFAC SDN).FINDING CITED IN EVERY MEMO
Fund-flow tracingWhere money moved from and to, across the public ledger.FINDING CITED IN EVERY MEMO
Identity & labelsPublic attributions — exchange, protocol, known service.FINDING CITED IN EVERY MEMO
Fraud & scam flagsReports of drainer, phishing, and scam-linked activity.FINDING CITED IN EVERY MEMO
Chain data & pricingTransaction history, balances, and USD value at time of transfer.PUBLIC DATA
Posture & practice

The unglamorous parts, stated plainly.

IN PROGRESS

SOC 2 Type II

Audit underway; report available under NDA on completion. Controls are operating now — the certificate is catching up to the practice.

STANDING

Encryption

AES-256 at rest, TLS 1.2+ in transit. Provider API keys held server-side only — never in the browser, never in exports.

STANDING

Access control

Role-based access, org isolation, least-privilege internally. Production access is logged and reviewed.

STANDING

US-hosted

Data resides in US regions. EU expansion is a deliberate future decision with GDPR designed in — not a default.

STANDING

Sub-processors

A current list of every sub-processor and data supplier, with what each receives, is maintained on the sub-processors page.

STANDING

Responsible disclosure

Found something? security@vernier.finance. We acknowledge within 48 hours, and we don't pursue good-faith researchers.

For your security team

You'll forward this page to someone.
This part is for them.

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 FACT SHEET · v1FULL PACKET & PENTEST SUMMARY UNDER NDA
INFRASTRUCTURE & TENANCY
HostingManaged cloud (Postgres + serverless functions), US regions. No self-managed servers; no customer data on employee devices.
Tenancy modelLogical isolation per organization, enforced at the database layer with row-level security — not application code alone.
Outbound integrationsData-provider APIs called server-side only. The payload is the screened address. Provider credentials never reach the client.
Blockchain accessRead-only RPC/data-API access to public chains. Vernier operates no wallet, holds no signing keys, and has no transaction-submission capability anywhere in the stack.
ACCESS & AUTHENTICATION
Customer authEmail + strong password with MFA available; SSO/SAML on Volume plans. Sessions are short-lived and revocable.
Internal accessLeast-privilege, role-scoped, logged. Production data access requires documented cause and is reviewed quarterly.
SecretsProvider and platform keys in a managed secrets store, rotated on schedule and on personnel change. Never in code, logs, or the browser.
DATA LIFECYCLE
EncryptionTLS 1.2+ in transit; AES-256 at rest, including backups.
Backups & recoveryAutomated daily backups with point-in-time recovery; restore procedures tested on schedule.RPO/RTO IN PACKET
Retention & deletionRecords are append-only while your account is active (that's the product). On termination: full export provided, then deletion within 30 days except where law requires longer.
PII footprintDeliberately minimal: user emails and org names. Counterparty data is public-chain data and provider findings — Vernier does not collect identity documents, and screening requests carry no customer identity.
ASSURANCE & RESPONSE
SOC 2 Type IIAudit in progress; report under NDA on completion.DATE IN PACKET
Penetration testingIndependent test at least annually and on major architecture change; summary available under NDA.
Vulnerability managementDependency and infrastructure scanning in CI; severity-based SLAs for remediation.
Incident responseDocumented IR plan; affected customers notified without undue delay and within any contractual/statutory windows.
Sub-processorsNamed list with purpose and region on the sub-processors page — infrastructure, billing, AI synthesis, and each screening-data supplier.
Anything marked "in packet" is stated precisely in the NDA security packet rather than approximated here. If your questionnaire asks something this sheet doesn't answer, send it — completed questionnaires are part of the service, not a favor.
Still diligencing?

Ask us the hard questions.

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