Read-only by design
Fallow requests minimum read scopes. It never deprovisions users or changes permissions in MVP.
Security
Fallow is designed to minimise what it collects, isolate every workspace and prevent support or engineering operators from reading tenant user data.
Fallow requests minimum read scopes. It never deprovisions users or changes permissions in MVP.
Raw scan data stays in encrypted regional blob storage and never enters Postgres.
Every request is authenticated, workspace-scoped and protected by central plan gates.
Support and engineering tooling expose metadata only—never your customer user data.
Data path
Sensitive source data is envelope-encrypted before storage. Postgres receives derived metrics and tenant-salted PII hashes—not raw API responses.
Controls
Fallow does not rely on a privacy policy alone. Its architecture removes common paths to accidental customer-data exposure. Security controls described here include target architecture and are not all generally available yet.
Regional database, encrypted storage and key management are launch requirements. The replacement infrastructure must be verified before hosted access resumes.
The target architecture uses a separate workspace key to wrap short-lived data encryption keys. Replacement key management is being validated.
Every report link is scoped to one file and one user, then expires after 15 minutes.
Append-only audit events form a SHA-256 hash chain; updates and deletes are rejected.
Logging and error reporting scrub credentials, tokens and customer PII before events leave the process.
Find the fallow seats
Join the private preview. The security controls described on this site include target architecture and are not all generally available yet.