Verso / Trust
Trust · security · discretion

Discretion, engineered.

The trade moves exceptional works on trust. Buyers, sellers, prices and locations are protected for good reason — most platforms treat that as a gap to tolerate; Verso treats it as a control to build. What follows is the design; the evidence arrives with the production build.

Discretion by design

Confidentiality enforced in the architecture.

Not left to good behaviour.

Need-to-know

Role and relation scoped

A registrar, a client and a shipping agent each see their slice of a record. There is no universal "view all".

Price on request

Default-private

Values and terms are withheld unless deliberately disclosed — per recipient, per record, with intent.

No cross-tenant compiling

Your book is yours

One firm's counterparties, collection and pricing are never pooled, profiled or resold. Verso builds no market-wide dossier from your data.

Owner-controlled disclosure

Explicit, reversible, logged

Consignors and collectors control what is shown, to whom, and for how long — a trail, never a side-effect of a default.

Crypto-shredding

Personal data in an append-only log

Shredded by key destruction, not deletion — the log stays whole, the person is gone.

Governance classes

Reversible · needs-signature · never-automatic

Every command carries exactly one. The test is not "can we undo it" but "who outside this company learns something when it runs".

Controls

Evidence, not promises.

The six controls the production build is specified against. None is evidenced yet, and this page will say so until it is.

Encryption

In transit and at rest

Every connection and every stored record, keyed per tenant — the same keys crypto-shredding destroys.

Identity

SSO · MFA · least privilege

Identity comes from your tenant's provider. Every seat holds the least it needs, and a seat is a role, not a person.

Residency

EU / UK data residency

Your book stays in the region you choose. No copy leaves it for analytics, training or support.

Assurance

SOC 2 Type II

The control set the build is written to. Audited after the production build, not before — and not claimed until then.

Monitoring

Detection and response

Every command is logged with its governance class; unusual ones are surfaced to a person, not silenced.

Trade compliance

AML · sanctions · CITES in the workflow

Checks sit on the act — the sale, the export, the loan — so the record shows they ran, not that they were meant to.

Status. Specified, not yet evidenced. The controls report is published with the production build and linked from this line.

Ask for the controls report when it exists.

Request the report