Identity and access
Netlify Identity provides v1 account sessions and confirmed email. Organization roles are enforced by the API. Credential management requires a time-limited TOTP step-up token.
Data isolation and staged migration
Billing, integrations, imports, canonical source data, usage and job records are tenant-scoped behind forced PostgreSQL row-level security. During controlled infrastructure migrations the organization directory is maintained in two managed datastores: every change is mirrored and compared by canonical hash, and authority moves only after sustained clean verification and a tested rollback path. Generic ingestion keys encode only an opaque tenant locator and are persisted as hashes.
Credentials
Provider credentials are encrypted with AES-256-GCM, bound to the organization and provider using authenticated additional data, and never returned after storage. Active and secondary master-key IDs support controlled re-encryption.
Execution safety
AI produces explanations, not executable jobs. Live writes stay globally disabled during the insights launch and require certified connectors, deterministic policies, read-back verification and rollback evidence.
Launch posture
These controls describe the staged implementation; they are not a claim that public general availability or the directory cutover has been approved. Launch remains gated by migration evidence, managed backup and restore proof, environment review and signed acceptance.
Report a concern
Email security@foxestechnology.com. Do not send credentials or customer data by email.