Vendor reviewEverything a security review asks for, in two files.
An architecture and security whitepaper and a pre-filled security questionnaire, written from the service as it runs today. Each answer points to the document or the source behind it, and anything we cannot show is marked as not claimed.
Version of November 8, 2026Both files are in English.
The two files
Use them as they are, or copy the answers into your own vendor-review template.
Architecture and security whitepaper
How a request travels from your system through our front door to the regional service and its database, how receipts are signed with Trustvice's own KMS keys and kept in a write-once copy, where data lives, who can access what, and how we handle incidents, vulnerabilities and recovery. An appendix lists the evidence for every statement.
trustvice-security-whitepaper.md · Markdown, EnglishDownload .mdPre-filled security questionnaire
79 questions in the style of the common lightweight questionnaires, grouped by domain, each with an answer, a short explanation and a link to the evidence.
trustvice-security-questionnaire.csv · CSV, EnglishDownload .csvThe whitepaper and the questionnaire are available in English only. Where they differ from a legal document, the legal document governs.
What the whitepaper covers
It describes the service as built, not a roadmap. Where a protection is partial, it says so.
- Data flow: website, API front door, the seven regional services and their databases, the MCP server and webhooks
- Who holds the Ed25519 signing keys (Trustvice, in AWS KMS), how their public halves are published, and what happens when KMS is unavailable
- Data regions and residency: what is regional, what is served from the US, and why calls never fall back to another region
- Sub-processors and how changes are announced
- Encryption in transit and at rest, at the provider and in the application
- Access control: API keys, scopes and roles, OAuth for MCP, sign-in and sessions, and access by our own staff
- Logging and the security audit log
- Availability, the status page, incident handling and breach notification
- Vulnerability disclosure and response targets
- Backup and recovery
- What we do not claim
- An appendix that ties every statement to the document and the source file behind it
How to read the answers
The answer column uses four values. They stay in English in the file, so they sort and filter the same way for everyone.
- Yes
- In place today, as described in the detail column and the linked document.
- Partial
- In place with a stated limit, or for some plans only. The detail column says which.
- No
- Not part of the service today.
- Not claimed
- We make no claim about this.
The documents that bind these answers
The pack summarises. These documents are the binding text.
Data Processing Addendum
Processor terms, security measures, breach notice within 72 hours, audits and international transfers.
Read the DPA →Sub-processors
Each provider that processes personal data, what it does and where, with 30 days' notice of changes.
See the list →Security model
The threat model: what a receipt proves, what you trust us for, and the stated limits.
Read the security model →Trust center
Signing, residency, availability, compliance posture and every legal document with its date.
Open the trust center →Responsible disclosure
How to report a vulnerability, safe harbor and our response targets.
Read the policy →Data regions
The seven regions and what crosses regions.
See the regions →
Questions the pack does not answer
Send us your own questionnaire and we answer it in writing within 30 days, as the DPA sets out. Enterprise buyers can also go through the architecture with us.
