Driver code often handles credentials, tokens, customer identifiers, or other things that shouldn't end up in centralised logging — and most of the time they don't, until somebody accidentally prints one. Data protection would add a set of safeguards that catch that sort of accident before it becomes a problem, and give teams with stricter compliance requirements the controls they need to use Anvil confidently.

At the centre is auto-redaction: common sensitive patterns (API keys, JWTs, credit card numbers, private keys, passwords in URLs, and more) are detected and masked at ingestion, before the data is stored. Because redaction happens up front, the original value is never persisted and there's no way to recover it — which is the point. Alongside redaction, secrets detection alerts your team when something that looked sensitive was intercepted, so you can fix the code path that sent it rather than relying on the safeguard to keep catching it.

Other controls give you coarser-grained protection. An IP allowlist lets you restrict ingestion to known controller or network ranges so unexpected sources can't send data to your project. An audit log records significant organisation actions — logins, member changes, API key creation, integration connections, security setting changes — so you can answer "who did what, and when" after the fact. Enterprise-tier additions include custom redaction patterns, session management, enforced MFA, data export controls, data residency options, and the GDPR/SOC 2 tooling that larger customers need.