FundOps — how your fund’s data is handled
We publish exactly what is true today and what is on the roadmap. Ask us anything; you’ll get the same candour.
| Control | Status | Detail |
|---|---|---|
| Custody / movement of funds | NEVER | The product has no custody, no payment rails, no bank connections. Wires move through your bank exactly as today; FundOps runs the paperwork and the record. |
| Deterministic figures | YES | All money math (allocations, capital accounts, performance multiples) is computed by an integer engine, unit-tested, exact to the minor unit. The AI never computes or invents a number; missing data renders as an explicit [MISSING] flag. |
| Human approval on every send | YES | No notice, letter or reminder reaches an LP without explicit operator approval. Approvals are recorded with actor and timestamp. |
| Append-only audit trail | YES | Every action (human / agent / system) is written to an append-only log, exportable as a CSV audit pack. The production database schema enforces immutability with a trigger. |
| Bank data minimisation | YES | Full account numbers are never stored. Wire confirmations record masked references only (e.g. •••• 4417). |
| Control | Status | Detail |
|---|---|---|
| Encryption in transit | YES | All traffic over TLS (HTTPS). |
| Data residency | YES | Deployed per client in a UK/EU region of your choice (e.g. London). Single-tenant: your instance and data are isolated from any other client. |
| Encryption at rest (document vault) | ROADMAP | In active development. Until it ships, pilots run without sensitive identity documents (no passports/IDs in the vault) — operational data and masked references only. We will tell you exactly when this lands. |
| SSO / SAML | ROADMAP | Planned alongside role-based access (admin / viewer roles are modelled in the production schema). |
| SOC 2 | NOT YET | We do not claim SOC 2. If certification becomes a requirement for you, we’ll discuss timeline honestly. |
| Control | Status | Detail |
|---|---|---|
| Model provider | YES | Anthropic API only. Anthropic does not train models on API customer data. |
| What the AI sees | SCOPED | Task-scoped context only (e.g. one LP’s call data to draft one notice) — not your whole database. Extraction suggestions carry confidence scores and require human confirmation before anything is written. |
| What the AI can do | DRAFT ONLY | Drafts prose and suggests extracted fields. It cannot send, approve, move data between LPs, or compute figures. |
Pilot data policy (honest line): during the design-partner phase, upload operational documents (LPAs, subscription docs with data you’re comfortable with) but hold identity documents until at-rest encryption ships. Bank references are masked by design from day one.
What we do not claim
Stated plainly, so you don’t have to ask.
No SOC 2
We do not claim SOC 2. If certification becomes a requirement for you, we’ll discuss timeline honestly.
No third-party penetration test
We have not commissioned an independent penetration test of FundOps.
No encryption at rest for the vault — yet
It is on the roadmap, not shipped. Until it is, pilots run without identity documents in the vault.
No SSO / SAML — yet
Planned alongside role-based access. It is not available today.
This page mirrors our security datasheet, v1.0. FundOps is software for fund administrators and fund managers; it is not a fund administrator.