Privacy and security, written the way it actually works
What Inflect stores, when an AI provider is involved, what leaves the practice, and what happens to your data if you stop working with us. No lawyer-blurred “industry-standard” language.
Short answers, up front
AI providers only see the data needed to draft the section you're asking for — trial-balance subsets, variance context, board preferences. Not cap tables, not investor lists, not employee PII. Every prompt is logged and attributable, and the list of what goes out is inspectable per client.
No. The delivery state machine blocks export from in-review. Portal links need explicit CFO send. Packages with unresolved anomalies don't generate. We won't ship autonomous AI output, at any price.
You get an export of every artifact — packages, memos, metric definitions, the decision ledger, source uploads. Marlow's stored context for your engagement is deleted within 30 days of your written request. No orphaned signals carried into other practices.
What Inflect stores · what you control
What we store
- Uploaded source files (trial balance, billing, budgets)
- Normalised working files and account mappings
- Client context: board preferences, metric definitions, narrative style
- Every generated package, memo, and commentary draft
- The decision ledger: confirmed decisions, rationale, revisit triggers
- Correction logs — so Marlow gets sharper, not noisier
- Portal delivery metadata and signed access tokens
What you control
- Whether AI drafting is enabled at all for a given client
- Which context is included for each engagement
- Which CFO edits become reusable signals — scope-tag per client, or promote firm-wide
- Whether a package is finalised
- Whether a package is delivered, and to whom
- Data-isolation level between engagements (full sharing → lessons only → fully isolated)
- Export and deletion on request, no retention holdouts
What's hardened, what's on the roadmap
Inflect is in design-partner mode. We tell you what's production-ready and what's not — because a buyer who gets surprised by this in month three is a buyer we've failed.
| Area | What ships today | On the roadmap |
|---|---|---|
| Authentication | Email/password with session auth. Sign-out revokes the session immediately. | SSO / SAML and MFA for firm-level rollouts. |
| Storage | Managed Postgres with daily backups; client uploads on an encrypted volume. | Per-client encryption key; regional data residency on request. |
| Secrets | Environment variables through a managed secrets store; never exposed in the UI. | Audit log for secret rotations. |
| AI provider data flow | Only the section-scoped context goes out. Every prompt is logged and attributable. No AI provider is allowed to train on your data. | On-prem / VPC-hosted inference for enterprise buyers. |
| Client delivery | Signed portal links with explicit expiry. Every delivery carries a CFO review mark. PDFs are watermarked with the practice and the review date. | Audit-log export per engagement. |
| Deletion | Full engagement-level export on request. Context deletion within 30 days of a written request. | Self-service deletion from the engagement settings page. |
Privacy is an operating belief, not a checkbox
The CFO owns the judgment. No package leaves the practice without a CFO review mark. Privacy controls exist because someone specific is accountable — we name them in every delivery.
Every financial claim should be traceable. Every number has a lineage. Every narrative paragraph has an author and a review mark. Every signal has a source. If a claim can't be traced, it doesn't make the package — that's also a privacy posture, not just a quality one.
AI should surface uncertainty, not hide it. We'd rather tell you “this metric can't be computed because the COGS mapping is incomplete” than print a confident-looking 0.0%. Uncertainty in the open is a privacy feature, because it doesn't paper over gaps you can't inspect.
Questions this page doesn't answer
Email security@inflect.finance. We reply to every one, and we'll tell you if we can't do the thing you're asking for — instead of burying it in an “industry-standard” statement.