Deal-data commitments PE firms actually scrutinize.

Every target list, every written summary, and every input you provide through the criteria intake is owned by your fund end to end. DealForge holds a non-exclusive license to process those inputs solely to deliver the contracted service — nothing in this license allows us to redistribute, sublicense, or train models on the data we will monetize.

On contract termination we return or hard-delete every artifact at your direction within 30 days. Encrypted backups are purged on the same 30-day cycle, and we provide deletion logs on request so your ops team can confirm the tapes are gone.

Only employees on a strict need-to-know basis — the analyst assigned to your account, and the small delivery-ops team that runs quality checks on the named analysts deliverable. Nothing from your flow is ever shared with another client, used to train models we will monetize, or surfaced to peers at industry events.

We sign a mutual NDA before any data exchange, and we will countersign yours. The signed NDA names every DealForge employee with read access to your account and is renewed at each renewal cycle.

Every UI and API call to DealForge is over TLS 1.2 or higher — no plaintext fallback, no exception for internal tooling. Stored data is encrypted at rest with AES-256 on managed Postgres volumes; backups inherit the same envelope.

We never run credentialed scraping of authenticated third-party systems under your credentials. Every input data source is either read-only public (secretary-of-state filings, public company registries, open LinkedIn profiles, public news feeds) or a licensed feed delivered under our vendor agreement. You never hand us a username and password for a target site.

Every third party that touches your data through DealForge, and what crosses each boundary:

The DealForge admin dashboard at /admin is gated to a single role-checked Postgres user, seeded at deploy time from the NOTIFICATION_EMAIL environment variable. No engineer or vendor has standing database access to client flows — admin reads go through the audited UI.

Admin reviews of a delivery are logged in leads/analytics rows so the client can request the access log on demand. Impersonation of another fund’s flow is permitted only with a written client-side request and is logged with the requester, the window, and the touched rows.

DealForge is in a paid closed beta with roughly 20 funds. The controls we already ship are below. We will not misrepresent readiness — the items in the “not yet” column are real gaps, on a real roadmap, with a release we will name in writing before the next cohort meeting.