What DevSync can access—and what it cannot do.
This page describes implemented controls. DevSync does not currently claim SOC 2 certification or an external penetration-test attestation.
Database access
Guided setup accepts PostgreSQL connections only after verifying that the role has no table, schema, or database-create write privileges. Scans inspect schema metadata.
Repository access
The GitHub App requests read-only Contents permission. You select the installation and repositories. DevSync creates short-lived installation tokens when a scan needs access.
Credentials
Database connection strings are encrypted with AES-256-GCM before storage. Browser responses expose only a masked preview. Production requires a deployment-specific encryption key.
Change boundaries
Scanning and plan generation do not execute SQL. Approval freezes a plan version but does not execute it. Migration execution and rollback use separate authenticated endpoints and explicit confirmation.
Tenant access
Row Level Security and server-side ownership or team-membership checks protect project, scan, plan, and team records.
Retention and deletion
Project records and reports remain while the project is active. Remove a project or request account deletion to remove application records, subject to limited security and legal retention.
AI data handling
Deterministic scanning and plan generation do not require an AI provider. AI enrichment is optional; when invoked, relevant schema findings and plan context may be sent to the configured provider.