Security & Trust
Built for how funds
actually handle deal data.
Portfolio deal data is material non-public information. OperatorBoard is architected from the ground up to keep it isolated, access-controlled, and auditable — without trading convenience for security.
What's true today
Six guarantees, in production now.
These are architectural facts about how OperatorBoard works today — not aspirational claims.
Per-fund data isolation
Every fund's workspace is row-level-security scoped at the Postgres level via Supabase RLS. One firm's deal data is structurally unreachable by any other fund — not just by policy, but by database enforcement.
We never train on your data
AI features call hosted models (Claude via OpenRouter) as a stateless per-request API. Your deal memos, thesis lines, and actuals are never retained by the model provider and are never used to train any AI model.
Role-based access control
Board, operator, and portfolio-owner roles each receive a scoped view. Board members see the rollup. Portfolio operators see their companies. Admins manage the workspace. No role can elevate its own permissions.
Versioned audit trail
Every thesis sign-off and monthly-report approval is timestamped and attributed to the user who took the action. The record is immutable: who approved what, and when.
Encryption in transit and at rest
All data travels over TLS 1.3. Data at rest is encrypted by Supabase's managed Postgres layer (AES-256). No plaintext data ever touches disk.
Google OAuth authentication
Logins are handled by Google OAuth — no password hashes stored in the application database. Accounts are tied to your corporate Google Workspace identity.
AI architecture
Your thesis is not a training dataset.
When OperatorBoard drafts a board deck or summarises a variance, it makes a stateless API call to a hosted language model. The request is answered and discarded. No deal content, no portco names, no financial lines are retained in the model provider's systems.
This is a deliberate architectural choice, not a setting you have to configure. The model gets only what it needs to answer the current request — nothing is persisted on the other side of that API call.
On the roadmap
Coming for enterprise funds.
These capabilities are committed on the roadmap and are not live today. We will not claim otherwise.
Roadmap
Enterprise SSO / SAML
Okta, Azure AD, and any SAML 2.0 provider — so your IT team controls provisioning and deprovisioning.
Roadmap
Configurable data retention
Set workspace-level retention windows so data is automatically purged when your policy requires it.
Roadmap
Exportable audit logs
Machine-readable export of all sign-offs, approvals, and user actions for your own compliance archive.
What we are not (yet) certified for
OperatorBoard is not currently SOC 2 Type II certified, ISO 27001 certified, or FedRAMP authorized. If those certifications are required for your fund's vendor policy, contact us — we will tell you exactly where we are in the process and whether the timeline fits your diligence window.
We believe the architectural guarantees above are more meaningful for a fund-stage deployment than checkbox certifications applied to a general-purpose SaaS product. We will pursue them as the right stage arrives.
Ready to carry the thesis to exit?
14-day free trial. Full platform. No card required.