How your data is handled

The demo runs on a bundled sample dataset: 12 fictionalized deals with invented account names. Nothing about you is collected when you explore it. If you generate an executive summary in demo mode, that sample dataset is processed server-side to produce the narrative. Sample data only, never yours.

The upload never leaves your machine. Your file is read and parsed by JavaScript running in your browser, scored there, and held in memory only:

• No server receives the file. There is no upload endpoint, no storage bucket, no database.
• Executive summaries for uploaded pipelines are generated in your browser as well.
• Nothing persists. Refresh or close the tab and the data is gone.
• No third party (including any AI model) ever sees your uploaded data.

Practical tip: when you export from your CRM, leave out personal contact fields (emails, phone numbers). Deal name, ACV, stage, close date, rep name, and hygiene fields are all the scoring needs.

The site uses Vercel Analytics for anonymous page views and button clicks (for example, how many people click "Book a Working Session"). No pipeline data, file contents, or personal identifiers are attached to those events.

If we work together on a Pipeline Health Audit, your CSV export is handled under the same principle: it stays under your control or mine, never on Pipewright servers.

• You send data via an access-controlled shared link (Google Drive, Dropbox) that you can revoke, or an auto-expiring transfer service. Not email attachments.
• Analysis runs locally on my machine. Your data is never uploaded to any Pipewright infrastructure.
• After the readout is delivered, your file is deleted from my machine. The only artifact that remains is the output we walked through together, which you have a copy of. Written confirmation of deletion is available on request.

If anything here is unclear, or your security team wants specifics before an engagement, book a working session and ask directly.