Skip to content
All guides

How To Keep PII Out Of Product Screenshots

Use demo data, hidden-element selectors, AI blur, and version approval to publish screenshots without exposing private data.

Selector hiding is exact but only hides what you point it at. This guide covers a practical workflow for keeping personal data out of docs, support, and marketing screenshots, with AI annotations as an extra layer for data you cannot target by selector.

Step-by-step implementation

  1. 1

    Capture from a demo or seeded account so real customer data is never on screen.

    Step 1
  2. 2

    Add CSS selectors for any remaining sensitive elements (emails, names, API keys) to the screenshot's hide list; they are made invisible before each capture.

    Step 2
  3. 3

    For sensitive data you cannot target by selector, save an AI annotation rule that blurs sensitive data. It runs on every new capture, and the unblurred capture is never served publicly.

    Step 3
  4. 4

    Keep the screenshot private until you have reviewed a capture, then approve that version so later captures wait for review before they are served from the stable URL.

    Step 4
  5. 5

    Embed only approved screenshot URLs in published content.

    Step 5

FAQ

Are hidden elements applied again on recapture?
Yes. Hide selectors are saved with the screenshot and applied on every capture.
Does ScreenshotAgent blur or detect PII automatically?
Selector hiding does not: elements are hidden only when they match the selectors you provide. An AI annotation rule can blur sensitive data that a vision model finds on each capture. It can miss things, so check blurred screenshots before publishing.
Can I review before publishing?
Yes. Approvals and versioning let you control what gets served publicly.

Run this guide in ScreenshotAgent

Start with one project and apply this workflow to keep screenshots accurate with less effort.

Start free trial14-day trial · 5 captures free · No card required