VOX ORDO · SECURITY — THE WHITEPAPER, READABLE
Security whitepaper
The full architecture, stated plainly enough to attack. Threat model first, trust boundaries drawn honestly, and a standing invitation to break it — because a security page that can't be tested is marketing.
01 / THREAT MODEL — WHO WE DEFEND AGAINST, STATED
in scopeus (the vendor) · a stolen laptop · a malicious partner · a compromised model provider
out of scopean attacker with your unlocked machine AND your passkey — we say so instead of pretending
"us" is first in the in-scope list on purpose — BYOK, local storage, and signed ledgers exist so you don't have to trust InSync
A THREAT MODEL THAT DOESN'T LIST THE VENDOR IS AN AD — THIS ONE STARTS THERE
02 / TRUST BOUNDARIES — THE ONE DIAGRAM
YOUR MACHINE · YOU TRUST IT
keys · memory · dictations · recordings · runner · ledger
→
CROSSES THE LINE · MINIMIZED
model calls (your key) · relay handshakes · grant tokens · usage counts
→
NEVER CROSSES · BY DESIGN
raw audio · transcripts · file contents · your keys · the memory graph
green/amber/red is the same risk grammar as the product — the whitepaper speaks the UI's language
ONE DIAGRAM, THREE COLUMNS — IF A DATA FLOW ISN'T ON IT, IT DOESN'T EXIST
03 / THE CRYPTO — NAMED PRIMITIVES, NO ADJECTIVES
signingEd25519 via platform passkeys · ledger entries chain SHA-256
at restXChaCha20-Poly1305, keys in the OS keychain · zero vendor escrow
in transitTLS 1.3 + pinned relay certs · E2E for summon and fleet pairing
share linkscapability URLs, 128-bit, revocable · passphrase adds scrypt
no "military-grade", no "bank-level" — primitive names and parameters, so experts can object
ADJECTIVES ARE WHERE SECURITY PAGES LIE — THIS TABLE HAS NONE
04 / DISCLOSURE — BREAK IT, GET PAID, GET NAMED
❯ curl voxordo.sh/.well-known/security.txt
Contact: security@voxordo.sh · PGP inline
Bounty: $500–$25,000 · scope: everything on this page
Safe harbor: yes, in writing · disclosure: 90 days, yours to publish
the bounty scope IS the whitepaper — if we described it, you may attack it
researchers publish after 90 days whether we like it or not; that's the deal
the hall of fame names every finder and links their writeups
05 / INCIDENT LOG — OURS, PUBLIC, UNDELETED
2026-04-18relay cert rotation gap, 41 min — summon links failed closedPOSTMORTEM ↗
2026-02-03bounty #7: share-link enumeration hardened (reporter credited)POSTMORTEM ↗
every security event, however small, gets a dated postmortem — the empty months are the credential
06 / AUDITS — THIRD PARTIES, PUBLISHED RAW
2026-05runner + ledger pentest · 2 medium, 5 low · all fixed, diffs linkedFULL PDF ↗
2026-03crypto design review of the signing chain · 1 advisory, adoptedFULL PDF ↗
the unredacted report ships, findings and all — an audit you can't read is a logo, not evidence · auditors are named and rotate yearly
MEDIUMS AND LOWS PRINTED WITH THE FIXES — THE FINDINGS TABLE IS THE TRUST, NOT THE COVER PAGE
07 / SUPPLY CHAIN — THE BINARY YOU RUN IS THE CODE WE SHOWED
❯ aria verify-build
› binary sha matches release 3357c8e · sigstore ✓
› reproducible: builds bit-identical from source
› sbom: 41 deps, 0 known CVEs · list attached
✓ the runner you're running is the runner we published
one command answers "is my binary tampered?" — locally, not by asking us
reproducible builds + signed releases + published SBOM per version
the update channel is just this check, automated before every install
08 / WHAT WE HOLD — THE WHOLE TABLE
account emailbilling + break-glass alerts · deleted 30 days after you leave
usage countstokens per key, for the bill · never the content
relay metadataconnection times for summon/pairing · 7-day rotation
nothing elseno audio, no transcripts, no files, no keys, no memory — we cannot produce what we do not have
four rows is the entire data inventory · subprocessors: one payment provider, one relay host — named, with contracts linked
THE SHORTEST TABLE IN THE INDUSTRY, ON PURPOSE — SUBPOENA-PROOF BY ARCHITECTURE, NOT BY POLICY
09 / TRANSPARENCY — REQUESTS, COUNTED AND DATED
H1 2026 · TRANSPARENCY REPORT
canary updated on the 1st, signed with the release key — if a date is ever missed, assume the worst and check the ledger
"0 content produced" is an architecture fact, not a legal victory
the canary is a signed monthly artifact on the verify page
member notice unless legally gagged — and the gag itself gets counted
SECURITY RULES: THE VENDOR IS IN THE THREAT MODEL · PRIMITIVES, NOT ADJECTIVES · FAIL CLOSED · PAY AND NAME THE BREAKERS · PUBLISH THE BAD DAYS · HOLD NOTHING WORTH TAKING — 9 SURFACES