Scan database fields for PII in dry-run mode first, then optionally transform writable string fields when your deployment explicitly enables database scanning.
POST /v1/scan/database
Disabled unless explicitly enabled by the deployment owner.
The engine defaults to dry_run=True so discovery can be reviewed before writes are allowed.
The public API route is disabled unless ALLOW_DATABASE_SCANNING is enabled on the deployment.
Callers can scope scans to selected tables rather than scanning the whole database.
Write-mode updates require tables with primary keys; tables without them are reported as skipped.
The API caps requested row limits and the engine supports configurable limits for controlled scans.
Database connection URLs are secrets and should be supplied only server-to-server, never from public browser code.