Trunk
Security you can audit.
SAML SSO with SCIM. Every gate cryptographically signed and appended to an immutable log. What follows is what we do, what we don't, and where to send a report.
Data model
Trunk stores three categories of data:
- Product content — your primitives (styles, components, pages), deltas, documentation, flags, comments. Encrypted at rest with AES-256, in transit with TLS 1.3.
- Identity + audit — user records, SSO mappings, gate signatures, activity log. Isolated database, tamper-evident.
- Repo access tokens — GitHub / GitLab / Bitbucket OAuth tokens. Encrypted, rotated on OAuth-refresh, scope-limited to read + PR-write.
We do not store your source-code repository. Trunk raises PRs on your remote; the code lives with your provider.
Access & identity
Audit trail
Every gate signature is cryptographically signed with the signer's SSO identity, timestamped, and appended to an immutable, tamper-evident log. Retention is 30 days on Team, up to 1 year on Enterprise. Export as CSV / JSON via API for regulators.
The log is append-only. Deletions are recorded, never applied. A per-tenant Merkle root lets you verify integrity independently.
Infrastructure
Subprocessors
| Provider | Purpose | Region |
|---|---|---|
| AWS | Primary compute + storage | us-east-1 · eu-west-1 |
| Cloudflare | CDN + DDoS mitigation | Global |
| Stripe | Payment processing | US · EU |
| Vanta | Continuous compliance monitoring | US |
Reporting vulnerabilities
Report security issues to firodiya.ritesh@gmail.com. PGP key: request by email. We acknowledge within 24 hours, triage within 72, and publicly credit reporters (opt-in) in the trust package.
Please do not run scans against production. If you need to test attack scenarios, contact us for a scoped staging environment.