1. Zero-Retention Execution

Veridence audits target codebases in an isolated, RAM-only sandbox container. We never write code files to persistent disk, and all sandbox instances are immediately destroyed upon audit completion.

2. OAuth & Access Credentials

Authorized tokens for GitHub and Slack are stored securely using cloud KMS encryption. These tokens are only used to fetch codebase files for the duration of requested scans and are never shared.

3. Data Security and Encryption

All communication with Veridence services is encrypted in-transit using TLS 1.3 and at-rest using AES-256. Audit logs and generated PDF/CSV reports are purged automatically after 30 days.

4. Contact Security Operations

For custom escrow setups, private air-gapped instances, or security inquiries, please contact our security team at security@agiphi.com.