Security at Superdriv
Pre-launch documentation · Last updated September 9, 2026
Workspace isolation
Workspace membership, account assignments and credential scope are checked on the server. PostgreSQL row-level security restricts user reads. Sensitive tables cannot be mutated directly by browser roles.
Protected credentials
Provider tokens use versioned AES-256-GCM encryption with record-bound authenticated data. Access and invitation tokens have 256 bits of randomness and are stored as hashes.
Human control
Sensitive operations become immutable drafts. Approvals bind the payload and expire within 30 minutes. Execution rechecks access, account state, guardrails and connection version. Concurrent execution is reserved atomically. Unknown provider outcomes are not retried automatically.
Operations
No third-party analytics runs on authentication invitations. Production operators must also disable or redact URL query and invitation path logging at the hosting layer. Backups, key rotation, monitoring and incident procedures are documented.
Verification status
This is an implementation description, not a certification. External provider approvals and live advertising verification remain prerequisites to enabling production writes.