Technical whitepaper
Version 0.2, 11 November 2026. Not yet externally reviewed; the document says so on its first page.
Read the whitepaper → What the server holds in the clear (section 7) Subprocessors and platform AI models
A short summary. The technical whitepaper states the mechanism, what we hold in the clear, and what the design does not protect against.
Version 0.2, 11 November 2026. Not yet externally reviewed; the document says so on its first page.
Read the whitepaper → What the server holds in the clear (section 7) Subprocessors and platform AI models
Vulnerability Disclosure Policy
We welcome good-faith security research. If you find a vulnerability in a Trausto system, please report it privately first so we can investigate and fix it before public disclosure.
Reporting
Email vulnerability reports to security@trausto.com. Include the affected system, a clear description, reproduction steps, and proof-of-concept material where appropriate. For sensitive disclosures, contact us for a public key before sending details.
Machine-readable per RFC 9116: /.well-known/security.txt
We do not currently run a paid bug bounty programme. With consent, we are happy to acknowledge researchers who report valid issues responsibly.
Acknowledgement
5 business days
We confirm receipt and let you know that the report is being reviewed.
Initial triage
14 days
We provide an initial severity assessment and coordinate remediation privately.
We aim to resolve critical vulnerabilities within 30 days and high-severity findings within 90 days. When public disclosure is appropriate, we coordinate timing with the reporter where possible.
RiskZone GmbH will not pursue civil or criminal action against researchers who act in good faith and follow this policy.
Intentional data theft, service disruption, social engineering, physical attacks, and DoS/DDoS testing are not covered by this safe harbor.
Security questions or disclosures?
Our security mailbox is reviewed by the responsible team.