Sensitive data detection

Find the details that are easy to miss before you share

PrivacyShot combines page-aware field rules with local text patterns to surface likely sensitive information in the current web page. You stay in control of every final cover.

PrivacyShot popup showing local screenshot protection
Detection starts only after you request a capture.

Local signals

Useful coverage without a cloud scan

PrivacyShot marks suspected content with local rules. It does not claim that a pattern match is a complete privacy audit.

01

Sensitive fields

Password, token, API key, verification-code, payment-card, identity-number, and other semantic field labels.

02

Common text patterns

Mainland China mobile numbers, common email formats, identity-number candidates, bank-card candidates, and IPv4 addresses.

03

Your own rules

Add custom keywords or CSS selectors for internal project names, account labels, or business-specific fields. They remain local.

Human review stays in the loop

Detection is a checklist, not a promise

A page can contain context that no simple rule understands. PrivacyShot makes the likely areas visible so you can check the rest yourself.

  1. Look for names, customer records, and internal URLs
  2. Check the browser address bar and visible notifications
  3. Inspect the final image after all covers are applied
  4. Use an opaque cover for high-sensitivity values
PrivacyShot editor for reviewing suspected sensitive areas
Delete a false positive or add a missing cover.

Keep sensitive page data out of the next ticket

Capture locally, review the result, and share only the evidence that helps someone act.

Download PrivacyShot