Data and compliance
Where your data lives, how it's kept, and how to get it out again.
Portfolio data is among the most sensitive material a fund holds. This page covers where it sits, what your obligations look like, and – importantly – how you leave if you ever want to.
Where your data lives
- Region: AWS London (
eu-west-2). Data stays in the UK/EU rather than being replicated to US regions. - Storage: PostgreSQL, with files in object storage in the same region.
- Residency: Because processing and storage are in-region, GDPR transfer questions don't arise the way they do with US-hosted tooling post-Brexit.
For funds subject to DORA, a compliant addendum is available – ask us and we'll send it with the contract paperwork.
Access control
Access inside your workspace is governed by roles. The one worth re-reading if you work with an external administrator is fund admin, which is explicitly walled off from files, investor updates, contacts and audit history – your administrator gets the numbers they need for the books without access to founders' confidential material.
Every API key is scoped to a single workspace, and the MCP server acts as the signed-in user, inheriting their permissions rather than granting blanket access.
Provenance
Fundra is built so that any number can be traced to where it came from:
- Extracted KPIs keep a reference to the exact spreadsheet cell or PDF page and text fragment they were read from.
- Competing values for the same period are kept, not overwritten, so restatements are visible as restatements.
- Ledger figures are derived from recorded transactions, so any position can be rebuilt from its underlying events.
- Changes are recorded in audit history.
- NAV can be split apart and recalculated for any historic period, as we automatically save a snapshot of your portfolio state at quarterly closing.
- LPA compliance is automatically enforced and verified against capital calls, distributions, management fee calculations, etc.
This matters at audit time. "Where did this number come from?" has an answer that takes one click rather than an afternoon.
Getting your data out
Data portability is a design property, not a retention lever:
- Full API access to everything in your workspace, at any time, on every plan – see custom integrations for the fastest way to pull it.
- Exports from any view in the app.
- Continued access for three months after a contract ends, so an export is never a fire drill.
If you're evaluating Fundra, the honest test of any vendor is what leaving looks like. The API is the same one the product runs on – there's no reduced "export tier".