Security

Last updated: to be set on publication.

An overview of how Fundgrow protects your data. This describes our practices at a high level and is not a warranty.

Tenant isolation

Each workspace’s private data (contacts’ workflow, notes, engagements, emails, mailbox connections) is isolated at the database layer by row-level security keyed to the tenant, so one workspace can never read or write another’s data. The shared investor universe is read-only to tenants.

Encryption

Data is encrypted in transit (TLS) and at rest by our infrastructure providers. Connected mailbox OAuth tokens are additionally encrypted with AES-256-GCM using a dedicated key before storage.

Authentication & access control

Sign-up requires email verification; sign-in supports password and magic link, with rate limiting on authentication and signup. Access within a workspace is role-based (admin / editor / viewer), and internal service credentials follow least-privilege.

Infrastructure

Fundgrow runs on managed, SOC-audited platforms (Vercel and Supabase) with no self-hosted servers. Database schema changes are version-controlled and replay-tested before release.

Monitoring & backups

We monitor uptime and runtime errors and alert on anomalies. The database is backed up daily by our provider; recovery procedures are documented and periodically tested.

Subprocessors & disclosure

We use vetted subprocessors (see Subprocessors). If you believe you’ve found a vulnerability, please report it to security@fundgrow.ai — we investigate all good-faith reports and will not pursue researchers who act responsibly.