Last updated September 13, 2026
This Privacy Policy explains what information TrustLedger ("TrustLedger," "we," "us") collects when you use our AI code governance platform, how we use it, and the choices you have.
Account information. When you create an account, we collect your name, work email address, and — if you sign in with GitHub — your GitHub username, profile URL, and avatar. If you sign up with email and password, your password is stored by our authentication provider (Supabase Auth) in hashed form; we never see or store it in plain text.
Repository and source code data. Once you install our GitHub, GitLab, or Bitbucket integration, we receive pull request metadata (repository name, branch, commit SHA, author, diff statistics) and the contents of files changed in each pull request, so our scanner can analyse them. Scan results — risk scores, detected AI-generated code, flagged secrets, and vulnerable dependencies — are stored so you can review, attest, and report on them later.
Usage and diagnostic data. We collect product usage analytics (pages visited, features used) and error/crash diagnostics to operate and improve the service.
Payment information. If you subscribe to a paid plan, billing is handled by our payment processor; we do not store your full card number on our own servers.
We use the information above to: operate the scanning, gating, and reporting features of the platform; authenticate you and enforce access controls; send you service notifications and security alerts you've configured (Slack, email, PagerDuty); generate the compliance evidence and audit reports you request; monitor and improve platform reliability and performance; and communicate with you about your account or the service.
Source code you submit for scanning is treated as confidential. It is used solely to provide the service to your organisation — to run our detection engine, generate risk scores, and produce the reports and dashboards you see. We do not use your source code to train third-party AI models, and we do not share it with other customers.
Access to stored code and scan data is scoped per organisation with database-level access controls, so one customer's data is never visible to another. You can configure data retention windows and request deletion of historical scan data at any time (see Section 6).
We rely on the following categories of subprocessors to operate TrustLedger. Each is bound by its own data processing terms:
We retain scan and violation data for as long as your account is active, subject to any retention window you configure in Settings. Attested scans are kept as an immutable audit record and are not deleted, since their purpose is to provide durable proof of review. You can request full deletion of your organisation's account and associated data by contacting us or using the account deletion option in Settings; some records may be retained where we have a legal obligation to do so.
We use encryption in transit (HTTPS/TLS) and at rest, HMAC-signed webhook verification, role-based access control, and an immutable audit log for security-sensitive actions. No method of transmission or storage is 100% secure, and we cannot guarantee absolute security.
Depending on your location, you may have the right to access, correct, export, or delete your personal data, and to object to or restrict certain processing. To exercise these rights, contact us at the email address below. We will respond within the timeframe required by applicable law.
We use a small number of essential cookies to keep you signed in (via Supabase Auth) and, where analytics are enabled, a cookie to distinguish unique visitors. We do not use third-party advertising cookies.
TrustLedger is intended for business use and is not directed at children. We do not knowingly collect personal information from anyone under 16.
We may update this policy from time to time. Material changes will be notified via email or an in-product notice before they take effect.
Questions about this policy or your data can be sent to trustledgerapp.dev@gmail.com.