Greymatter.ioGreymatter.io
Start for Free
Greymatter.ioGreymatter.io Why Greymatter.io?
Pricing Start for Free
Use Case • Sensitive Data Detection

Your data moves all day. Now you can see where.

Personal data, sensitive markings, health records, and shipment details move between your apps, vendors, and AI tools. Greymatter reads that traffic and highlights findings as it moves.

Built for regulated data
Four kinds of regulated data, in one pass
Identity numbers, card and bank numbers, health codes, shipment details, and sensitive markings.
See What It Detects →
Mapped to ISO 27001, PCI DSS, GDPR, and HIPAA
The Stoplight shows where sensitive data detection is on, service by service, for each framework.
See Stoplight Measurement →
GigaOm Radar Leader and Outperformer, 4+ years
Ranked at the top of the market by independent analysts.
Explore Mesh →
Real-world problems

Sensitive data leaves your apps. Most teams never see it.

Most data loss tools watch files and email, not the messages your apps and AI tools send each other. When a support chatbot sends a client's account numbers to an outside AI company, nothing flags it. The first anyone hears of it is a breach report.

Your current toolsChecks who sent it and where it is going. Never opens it.
CHECKING LABEL
Sent bySupport chatbot
Going toAn outside AI company
InsideNever opened
VerdictNothing flagged. Request sent.Three leaks left with no record.
GreymatterOpens the message, finds the sensitive data, and records who sent it.
WAITING
Sent bySupport chatbot, for J●●●●● R●●●●●
Going toAn outside AI company
InsideAccount numbersSensitive markingsInfrastructure details
VerdictInspecting…Saved to the forensic record · 9:14:07
One week, start to finish

Follow sensitive data through one week at a hospital.

Ana Ruiz leads privacy for a regional hospital system. Pick a day on her calendar to see what moved, what Greymatter recorded, and what she did next.

Privacy officeWEEK 11 · REGIONAL HOSPITAL SYSTEM
FLAGGEDDELIVERED
MON909:14 Chatbot prompt Card numberHealth data TUE1011:40 Chatbot answer Home address WED1102:00 Nightly sync Patient recordsDiagnosis codes THU1207:30 Vendor reminders Diagnosis codesSocial Security numbers FRI1315:00 Weekly privacy review 3 apps found
MONDAY · 09:14 · CHATBOT PROMPT

The card number and diagnosis code get flagged, with the agent's name on them.

What happened

A support agent pastes a patient's details into the chatbot. Greymatter reads the prompt on its way to the outside AI model.

Draft a reply for this client. Include their card number and a diagnosis code.
What Greymatter recorded
Card numberRecorded. Request delivered.
PERSONAL DATA
Health dataRecorded. Request delivered.
HEALTH DATA
Ana keeps the chatbot running and corrects one agent, instead of banning AI across the hospital.
Explore AI Guardrails & DLP →Sample data. Values masked.
Day to day

What changes for your team.

One tenant policy entry turns detection on for every app it selects, including apps added later. Your apps do not change.

NO DOWNTIME
Work never stops
Detection records and alerts. A false alarm cannot lock anyone out of the system they need. Explore AI Guardrails & DLP →
LESS NOISE
Alerts worth reading
Card and bank account numbers must pass their check-digit test. Common shapes, such as email and street addresses, need a label or context before they count. Your team acts on alerts instead of muting them. Explore AI Guardrails & DLP →
LOWER COST
No new tool to run
Detection is part of the Greymatter platform, with the same policy, record, and Console. There is no separate agent to deploy, connect, or staff. Explore the Platform Overview →
LESS RISK
Evidence you control
You decide what each finding keeps. Turn message bodies off, and a finding keeps only a short piece of the matched text. Credentials in headers and URLs are written as [REDACTED]. Explore Forensic Auditing →
See it on your own traffic

See what sensitive data leaves your apps today.

Start free on the systems you already run. Turn on detection and read the first findings, with nothing blocked.

Start for Free Meet Our Security Experts Browse How to Buy →
Download the Guardrails and DLP white paper
Keep digging

Additional resources

Platform AI Guardrails Learn More → Platform Forensic Auditing Learn More → One-pager Greymatter for Every Role Read the One-Pager →
Swipe for more
Asked and answered

Sensitive data detection FAQs

Greymatter sensitive data detection finds confidential information while it moves between apps, APIs, and AI agents. It spots four kinds: personal data, health data, logistics details, and sensitive markings. The record names the sender, the destination, and the time. Detection is built into the platform, with no code changes.

Greymatter reads the traffic between apps, APIs, and AI agents, including prompts sent to AI chatbots and the answers that come back. Traditional DLP watches files and email at the endpoint. Each finding names the person or app that sent it. Greymatter records and alerts, and never blocks the request. Many teams run both.

Yes. Greymatter Stoplight maps the sensitive data control to requirements in HIPAA, PCI DSS, and GDPR. It shows where detection is on, service by service. It supports your review. It does not certify compliance.

Greymatter keeps a forensic record of findings, with the sender, the destination, and the time. Search it by app or person in the Console's sensitive data view.

Greymatter favors precision over volume. Card and bank account numbers must pass their check-digit test, and common shapes such as email addresses need a label or context. Findings arrive with the app or person who sent them.