How your data is protected
Encryption at rest, how credentials are stored, what the AI can and can't read, and honest answers about export and deletion.
Last updated 2026-08-30
Encryption
Connector credentials, two-factor secrets and documents are encrypted at rest with AES-256-GCM. Tampered data fails to decrypt rather than returning something wrong.
Passwords are hashed with scrypt using a unique salt per password and compared in constant time. They are never stored recoverably — which is why a lost password is reset, never retrieved.
Connector credentials
A credential you paste for Stripe, GitHub, Airtable or anything else is encrypted before storage, used server-side only, and never returned to the browser or written to logs. After saving, it is never shown again.
Only workspace admins can set them, and a key can be scoped to a single venture, the workspace, or you personally, with the most specific winning.
Sessions
The session cookie is httpOnly, sameSite lax, and secure in production — it cannot be read by JavaScript. Sessions last 30 days, and the token is rotated when you complete two-factor. You can see and revoke every active session in Settings → Security.
What the AI can read
Advisors and the engine read that one venture's own modules: todos, GTM, metrics, OKRs, notes, documents and prior board analysis.
Documents marked sensitive are excluded from AI context. That exclusion is enforced in the database query, not requested in a prompt, and a sensitive document also cannot be published to a venture's public help pages.
Access between ventures and workspaces
Access is checked per venture on every request. A venture you have no access to returns "not found" rather than "forbidden" — deliberately, so the API cannot be used to discover what exists.
Two honest limitations
We would rather tell you these than have you discover them at the wrong moment:
- There is no one-click data export in the app today. What you own outright is your GitHub repo, your domain and your published site. If you need your kitty data extracted, email info@foundergem.com and we will do it by hand.
- Closing your account disables it rather than erasing it. See closing your account for exactly what that means and how to request real deletion.
Audit trail
Sensitive actions — invites, role changes, two-factor changes, sign-ins and failures, password resets, account closure — are written to an audit log. That log is currently readable by the instance operator rather than exposed to you in-app. Ask us and we will tell you what it holds about your account.
Full detail lives in the Privacy Policy and Terms.
Frequently asked
- Can I export all my data?
- Not with a button today — that does not exist and we would rather say so. Email info@foundergem.com and we will export it for you.
- Does the AI read my private documents?
- It reads the venture's documents except those marked sensitive, which are filtered out at the database query. Mark anything confidential as sensitive.
- Where are my connector API keys stored?
- Encrypted at rest with AES-256-GCM, used server-side only, never returned to the browser or logged, and never displayed again after you save them.
Related articles
- Turn on two-factor authenticationSet up TOTP in about a minute, save your ten recovery codes — and understand why saving them matters more here than elsewhere.
- Close your accountWhat closing does (and honestly does not do), what happens to your ventures and Treats, and how to ask for real deletion.
- Connect Stripe, GitHub, Airtable and the restWhat each connector unlocks, how credentials are stored and scoped, and the honest limits of what each one can do today.
Still stuck?
Email info@foundergem.com with your account email and what you were trying to do. A human replies, usually within one business day.
Browse all articles