GDPR and Screen Sharing: Keeping Personal Data Off the Screen
Screen sharing a CRM, dashboard or inbox can put personal data — names, emails, IDs, IP addresses and location — in front of people who don't need it, and into retained recordings. Here's how data minimisation applies and how to keep personal data off the screen. Not legal advice.
Personal data under GDPR — a customer's name, email, IP address, order or account ID — routinely sits in the CRM, dashboard or inbox you're about to present. The practical way to stay on the right side of data minimisation is to keep that data off the screen: share a single window, blur the personal data you don't need to show, and control whether the session is recorded and how long any recording is kept. An unnecessary on-screen disclosure — especially to people in another organisation on the call — is exactly the kind of processing the principles are meant to curb.
What counts as personal data on your screen
GDPR defines personal data broadly: anything relating to an identified or identifiable person. In Salesforce, HubSpot, a support inbox, an analytics dashboard or a spreadsheet of users, that includes:
- Direct identifiers — names, email addresses, phone numbers and postal addresses.
- Account and reference IDs — customer, order, ticket and user IDs that map back to a person.
- Online identifiers — IP addresses, device IDs and cookie identifiers, e.g. in an analytics or logs view.
- Location and behaviour — city or region columns, session recordings, purchase history and other profile data.
- Special-category data — health, religion, ethnicity or similar, which carries stricter handling and should almost never be casually on screen.
- Other people's data in the margins — a contact list, an inbox preview or a notification naming customers unrelated to what you're demoing.
Which GDPR principles apply to a live share
Three principles do most of the work here. Data minimisation says process only the personal data you actually need — showing a whole customer table when you're demoing one workflow is more than necessary. Purpose limitation means data collected for one purpose (say, fulfilling orders) shouldn't be casually repurposed as demo material for an audience with no need to see it. And for recordings, storage limitation matters: a screen recording full of personal data is itself a new record that must be kept only as long as needed, then deleted. Keeping data off the screen in the first place is the cleanest way to honour all three.
Common risks and how to reduce them
| Risk | Practical mitigation |
|---|---|
| Whole screen shared, exposing other apps and tabs | Share a single window only; close or blur background tabs holding customer data. |
| A CRM list or table showing many customers at once | Blur the columns and rows you're not discussing; reveal only the one record in scope. |
| Inbox, chat or notification previews naming customers | Turn on Do Not Disturb; box-blur the message pane; keep a panic blur ready. |
| Analytics or logs showing emails, user IDs or IP addresses | Blur the identifier columns; present aggregates rather than row-level personal data where possible. |
| Cross-org demo to people with no need to see real data | Use a demo or sandbox account with fake data, or blur real personal data before presenting. |
| A retained recording containing personal data | Decide up front whether to record; if you do, limit retention and delete when no longer needed. |
- 1
Share one window
Present only the app you're demoing so your inbox, chat and other tabs with personal data stay out of frame.
- 2
Blur personal data in the page
With BlurFirst, box-blur list views and identifier columns, then element-blur individual names, emails or IDs. The blur is rendered into the page as real pixels, so it survives Zoom, Google Meet, Microsoft Teams, Loom and any recording.
- 3
Scan for common identifiers
Click Scan to auto-detect and blur emails, phone numbers and card numbers locally in one pass — a quick data-minimisation sweep before you present. It matches patterns, not free-text names, so check the ones it can't detect.
- 4
Reveal only what's needed
Leave visible just the record or metric relevant to the call; keep everything else frosted. Start blurring with Ctrl/⌘ ⇧ Y and panic-blur with Ctrl/⌘ ⇧ H.
- 5
Control the recording
Decide whether to record at all; if you do, review it for stray personal data and keep it only as long as you need it.
A checklist before you share your screen
- Prefer a demo or sandbox account with synthetic data for anything customer-facing.
- Share a single window, not the whole screen.
- Turn on Do Not Disturb so notifications naming customers don't appear.
- Blur identifier columns, lists and previews, and run Scan for emails, phones and card numbers.
- Reveal only the record or metric in scope — data minimisation in practice.
- Decide whether to record; if you do, review it, set a retention limit, then delete when done.