Skip to main content

Demoing with Buyer Data: Preparation and Privacy Checklist

Illustrated presales article cover with a document and play control for demoing with buyer data: preparation and privacy checklist

Using a buyer’s own data in a demo can answer questions that fictional records cannot, but it creates privacy, security, and accuracy obligations. Start with a narrow test purpose and use the least sensitive data that can answer it.

Confirm permission and scope

Ask who owns the data, what may be shared, which environment may process it, who will see the result, and when it must be removed. Follow the organization’s legal and security process. Do not assume that receiving a file by email authorizes uploading it into a demo tool.

If the question can be answered with synthetic data or a buyer-created test record, use that instead. Real data should have a specific reason to be in the demonstration.

Prepare the environment

Check access controls, logging, retention, backups, and screen-sharing behavior. Remove unnecessary fields and identifiers where possible. Have a safe fallback if the data cannot be approved in time. Avoid using a production account as a shortcut because the standard demo tenant lacks configuration.

For example, a buyer may want to verify how a reporting tool groups their departments. They could provide a small approved test hierarchy rather than real employee records and financial results.

Document what the test proves

Record the sample, configuration, date, and result. A successful path with ten records does not establish performance with ten million. Keep the data-handling record separate from a public case study and obtain separate permission before sharing any buyer-specific screenshot or outcome.

The safe sample data guide helps when real buyer data is not necessary.

Check the data path before and after the demo

Before using buyer data, make sure the people responsible for it can answer these questions:

  1. What buyer question requires this data rather than fictional records?
  2. Which fields and people are permitted, and where may the data be stored?
  3. What will appear in screen shares, notifications, logs, and recordings?
  4. Who will remove the data, including any retained copies, and how will completion be confirmed?

If an answer is missing, use a fictional scenario and explain what a later buyer-specific test would require. After the session, follow the agreed removal process and record that it was completed. A reset of the visible demo screen alone is not proof that every copy is gone.

Ready to try our platform?

Get started for free