Candi1 — Privacy

QUANTVESTRIX, INC. · last updated 2026-10-28 · HTTPS only

Candi1 is built so that activity is publicly verifiable while personal information is not public. This page states, plainly, what is visible, to whom, and why.

What anyone can see

Every settled Candi1 transaction has a ByteID that is publicly visible on our scanner (candi1scan.us) and on the public chain. A ByteID shows that a settlement happened and lets it be verified — the provenance travels inside the identifier, with the payload, not as a pointer to a private database.

What requires a membership

Party details, counterparties, exact amounts and the UETR/reference behind a ByteID are only visible to a holder of a valid membership credential, supplied as X-QVTX-Membership. Membership is a ByteID pair (a public sense identifier and a private shadow key); only the sense is stored, and the server re-derives the pair. Without it, the scanner returns the ByteID and that a settlement occurred — never the PII.

What we do not do

Standard built-in

Candi1's records are structured for ISO 20022 and mapped to an open-API connection specification, so the same transaction can be read by a counterparty's compliant systems while the public surface still exposes only the ByteID.

This is a plain-language privacy statement for the Candi1 surfaces. It is not legal advice and does not create a contract. Questions: candi1.us.