Trust & data use
What ValuationMCP stores, and what stays with you.
A plain-language summary of commitments the Privacy Policy, the Terms and the product already make. Where this page and the Privacy Policy differ, the Privacy Policy governs.
Read the Privacy Policy →Stays on your side
Platform credentials
Your assistant connects to your platforms through their own MCP servers or APIs using credentials you control. ValuationMCP cannot see and does not store those credentials.
Records, files and exports
Only the specific figures your assistant sends reach the database. Statements, transaction histories, CRM exports, position-level data, payroll files and similar source material stay on your side.
Client information
No client names, no account numbers, no positions. ValuationMCP has no field for client-identifying data. Client households are held as a count, never a roster.
What you type
The one thing that could carry client information in is text you type yourself. Do not place client names, account numbers, Social Security numbers, contact details or other nonpublic personal information in notes, source details, deal-room memos, data-request notes or any other input.
What ValuationMCP stores
Practice inputs
The firm name, any notes, and the financial and operating figures sent: revenue, EBITDA, EBOC, AUM, client households, cash flow and rates, and any supplied multiples.
Quality scores, not raw metrics
Raw quality metrics are converted to the six 0–100 scores the engine consumes using fixed published anchors; the scores are stored and the raw values dropped.
Provenance
Which platform or system supplied each input, so each valuation is traceable.
Valuation outputs and deal rooms
Per-method values, the blend, the quality multiplier, confidence and the headline. For shared rooms: the parties, seats, the figures the host chose to share, and memos whose figures are engine-copied facts only.
Who can see what
Your records are yours
Practice records, valuation outputs, deal rooms and data-request submissions are scoped to the account that created them, enforced per user at the database level.
The host decides what crosses
In a deal room, the host chooses what the other side sees; the range and data coverage always travel with shared figures. A buy-side walk-away ceiling is never shareable.
NDA before figures move
A data request opens a shared room where the NDA step comes first, unless the receiving firm waives it. Nothing is sent until the account holder reviews and approves it.
Network sharing needs consent
A network sees a member's practice only after that member's explicit consent, and sees saved outputs, not raw inputs.
Agents prepare, people approve
An assistant may prepare a submission or a request; a person approves each step.
No standing connections
Every pull is a one-time request in a conversation you can see; nothing keeps a standing key to your CRM or ledger.
How data is used
ValuationMCP does not sell, license or share identifiable practice records, valuation outputs, deal-room content or data-request submissions with third parties. Aggregate statistics are computed only after stripping firm-identifying fields, and any benchmark dataset is derived from de-identified aggregates.
Advertising measurement: the Google Ads click identifier from the link you arrived on may be shared, with the fact and value of a paid subscription, with Google to measure advertising. Your name, email and practice figures are never sent. Global Privacy Control and Do Not Track are honored, and you can stop advertising measurement from the Privacy Policy.
Advertising measurement in the Privacy Policy →Keeping and deleting data
Records are retained while your account is active so you can compare past work. Archiving a run or a room hides it without deleting it.
From your workspace you can delete individual valuations, all valuations for a practice, or the practice record itself. If you delete your account, your records are removed within a commercially reasonable period, except where data must be retained for legal or security purposes.
Security
Encrypted transport, authenticated MCP sessions, per-user row-level access control and role-based access in the application. What a deal-room guest may see is decided server-side by the host's share choices, not by the page they open.
Figures you can check
Every figure comes from a deterministic engine, not generated text, and each saved run records the engine and index versions that produced it.
Read the methodology →