[Dramatization] A customer support rep
That spreadsheet
had customers' phone numbers in it.
*This story is a dramatization. All people and companies are fictional.
Every week, her job is to have AI summarize trends in customer inquiries. The busier the day, the more the checks get skipped.
That day, too, she attached the spreadsheet as is.
Inside were customers' names, phone numbers, and email addresses. There was no time to look over hundreds of rows.
That's when they found...
Samurai AppThe company had turned on Samurai App's PII detection.
Eight minutes to the deadline.
Fujita chose Send masked.
before sending...!
3 p.m. on the dot. The summary reached the leader.
How did this happen?
Here are 3 reasons
- It checks in the browser before sending
Covers chat attachments, files added to knowledge, and text in the input box. No model is used, and nothing is sent out for the check.
- It finds personal data and secret values
Email addresses, phone numbers, My Number (Japan's individual number), addresses, card numbers, API keys, and more.
- The user decides whether to send
Cancel, Send as is, or Send masked.
Built for company use, so these never bend
- Admins and managers are the ones who flip the switch
- When something is sent despite a finding, only the file name and count go to the audit log (never the values)
- With the browser extension, attachments and pastes on other companies' generative AI sites can also be checked before sending
What happened to Fujita
Send a masked copy, and the analysis carries on as usual.
Team leader: "We no longer have to rely on each person's attention to catch it."