What leaves your machine, and what never does

Updated August 14, 2026

The short version: your quote and policy documents never leave your machine, full stop. Your Vault, your saved proposals, and your brand settings do leave your machine, but only to your own workspace's server, never to a third party. There is exactly one kind of data that reaches an outside service at all, and it is described in full below.

#PDFs are parsed in your browser, with no network call

When you drop a carrier quote or a current policy on the New proposal page, or a document on the Vault page, the parsing happens entirely inside your browser. The engine that reads the PDF is bundled with the app itself, not fetched from anywhere, and runs against the raw file the moment you drop it. There is no upload, no request to a parsing service, no server round trip. See How ProClose reads a PDF for how the parser itself works.

That is true whether the parse succeeds or not. If a PDF cannot be read deterministically, the app falls back to the sample flow locally. The file itself is never sent anywhere to try harder. See When a PDF does not parse.

#The Vault, your proposals, and your brand reach your own server, and nowhere else

Everything in your Vault (appetite guide, fee schedule, coverage standards, vendors, and any document you drop in to update it), every proposal you save, and your Brand settings are written to your own workspace's server, so they survive a reload and follow you to a different device. That server is yours, run by whoever set up your ProClose install. It is never a third party, nothing on it is used for training, and the app never sends it anywhere else. See Where your data lives for exactly what is stored and where.

A document you drop on the Vault page to feed it new rows is still parsed locally first, the same as a quote PDF below; only the resulting appetite rows, fee lines, standards, and vendors, the structured data, get saved to your server once you confirm the merge.

#The deck renders locally

Building a proposal, editing it on the canvas or in the outline editor, and presenting it, all of that is your browser assembling and rendering the slides from data that is already on your machine. Nothing about building or viewing a deck sends its contents anywhere.

Exporting is the same story. Printing to PDF, downloading HTML or Markdown, or using Copy for AI all produce their output locally, from what is already in your browser. See Print or save as PDF and Export HTML, Markdown, and Copy for AI. Clicking Save to add a proposal to your Proposals list is different from all of that: it is a deliberate write to your workspace's server, covered above, not a local-only render.

#The one path to a third party: analyzing a call

This is the only data that reaches a service outside your own infrastructure, and it happens only when you deliberately pull and analyze a recorded call.

Here is the exact path:

1. You pick a call in the call picker. The recording is retrieved from your RingCentral account by your own server, not your browser.
2. Your server sends the call audio to a transcription service to get a transcript.
3. Your server sends that transcript to an insight model to extract structured fields (prospect name, summary, coverage needs, objections, sentiment, next step, key quotes, and so on).
4. The transcript and the resulting insights come back through your server to your browser, and your server also writes them to its own disk cache so that specific recording is never transcribed or analyzed a second time.

Two things are worth being precise about:

• Your browser never talks to the transcription service or the insight model directly. Both calls are made server-side. Your credentials for either service are never sent to a browser.
• This only happens for a call you choose to analyze. Nothing about your documents, your Vault, or a proposal you are building is sent to the transcription or insight service. What reaches that outside service is scoped to call audio and the transcript derived from it, nothing else.

For what gets cached, how the 25MB recording limit works, and what happens on a retry, see Call analysis: caching, limits, and privacy.

#The full picture

Nothing else ever reaches a third party.

#Related articles

• Where your data lives
• The Security page
• How ProClose reads a PDF
• Call analysis: caching, limits, and privacy