It spots personal data and internal keywords before they go to an AI. On a hit your organization decides: send with a mask, send with a warning, or stop the send. The setting applies to everyone and individuals cannot turn it off.
It scans what is about to be sent for built-in kinds and your organization's own rules.
Mask, warn, or stop the send, as chosen for each kind and each rule.
With the mask action, the text goes to the AI with placeholders. With warn and send, the value goes as it is. With stop, nothing is sent.
If the reply contains a placeholder, it is turned back into the real value only when shown on screen.
Chosen for each built-in kind and each custom rule.
The value is replaced with a placeholder such as "Email_1" before sending. If the reply contains the placeholder, the screen shows the original value again.
The send is not stopped, but the person is told that an organization rule was hit. This action does not mask the value.
Nothing goes to the AI. The screen says the message was not sent because of an organization rule, and no PFC is used.
On Enterprise you can switch the items other than the current message on or off. By default all are on. Some paths check only the current message, and some check everything regardless of the switches. The contents of images, audio and video are not checked on any path.
Always on and cannot be switched off.
Content from earlier turns is checked too.
Text that can be read from attached documents is checked. Text inside an image you attach is not.
Content pulled from knowledge before it is passed to an AI is checked.
Text fetched from a URL is checked.
The instruction text for generating images and similar is checked.
Email addresses, phone numbers, postal codes, Japanese My Number, credit card numbers, bank account numbers, addresses (in the form of a Japanese prefecture through a street number), API keys and US Social Security numbers (SSN). On Enterprise you choose, for each kind, whether it is detected and which action applies.
Add words that only your company uses, such as project names or client names. Keywords (several words, with optional fuzzy matching) and regular expressions are supported. Each rule has its own action, and you can name the placeholder (for example "Client"). Each organization can have up to 20 regular-expression rules.
If someone sends "Write a reply about Mr. Tanaka (tanaka@example.com / 090-1234-5678)", the email address and phone number are replaced and the AI receives "...Mr. Tanaka (<Email_1> / <Phone_1>)...". If the reply contains a placeholder, the screen shows the original value again.
Personal names such as "Mr. Tanaka" are not found out of the box. Cover names and internal terms with your own rules.
| 項目 | Business | Business+ | Enterprise |
|---|---|---|---|
| Mask before sending, restore in the reply | Yes | Yes | Yes |
| Per-kind on/off and action | — | — | Yes |
| Switching what is covered (history, attachments and so on) | — | — | Yes |
| Your own rules | — | — | Yes |
| Standard auto-mask that individuals cannot turn off | Yes | Yes | Yes |
Only the kind and number of hits, the action (mask, warn, stop) and the rule ID are recorded. The matched values themselves, the rule contents and the conversation text are not.
It is under Settings and is shown only to organization admins.
For each kind, such as email addresses, switch it on or off and choose mask, warn or stop.
Add your own terms as keywords or regular expressions and choose an action.
From a member account, send a phrase that should hit. A stop rule shows that the message was not sent because of an organization rule.
Questions? Contact us.
Enterprise is available online: choose your seats and shared PFC, then pay by card.
Go to the sign-up page