Data residency
Launch workspaces use Australian infrastructure: Neon in Sydney and Azure services in Australia East. EU and US mappings are designed but not represented as generally available at launch.
Trust centre
The detail behind our security claims.
A public summary of how Fallow handles tenant data, isolates workspaces and limits internal access. Formal assurance documents will be published here as they become available.
AU
Australia is the launch data region.
1:1Tenant to Key Vault key isolation
15mReport link expiry
30dDefault raw scan retention
Architecture
Controls that are difficult to bypass.
Security-sensitive choices are centralised in the product architecture rather than left to individual routes or support procedures.
Per-tenant encryption
OAuth tokens and raw scan data use envelope encryption with tenant data keys wrapped by a workspace-specific Azure Key Vault key.
Data minimisation
Raw API responses never enter Postgres. Postgres stores derived metrics and tenant-salted hashes where possible.
Operator boundaries
Support and engineering tooling expose workspace metadata only. Fallow has no tenant impersonation mode.
Tamper evidence
Audit events are append-only and linked by a SHA-256 hash chain. Updates and deletes are rejected by database triggers.
Controlled egress
Reports are encrypted at rest and served only through signed, single-file URLs with a 15-minute expiry.
Sub-processors
A short, intentional list.
These providers support Fallow infrastructure and service delivery. Contractual details can be supplied during vendor review.
Microsoft Azure
Compute, queue, encrypted blob storage and Key Vault key management.
Neon
Regional serverless Postgres for application and audit metadata.
Stripe
Subscription billing, checkout and tax processing.
Resend
Transactional service email.
Cloudflare
DNS, CDN and perimeter delivery services.
Find the fallow seats
Need evidence for your vendor review?
Send your security questionnaire or architecture questions directly to the Fallow security contact.