> ## Documentation Index
> Fetch the complete documentation index at: https://docs.notifique.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Security and verification

> Control who uses chat: anonymous, form, OTP code, or site login.

You choose whether you need to know **who** is chatting.

## Identification modes

| Mode             | What happens                          |
| ---------------- | ------------------------------------- |
| Open (anonymous) | Click and chat, no form               |
| Optional         | Asks for name and email, but can skip |
| Required         | Must fill in to chat                  |

### Form fields

| Option | Fields               |
| ------ | -------------------- |
| Email  | Name + email         |
| Phone  | Name + phone         |
| Both   | Name + email + phone |

<Tip>
  To capture leads without blocking people in a hurry: **Optional** + **Email**.
</Tip>

Data becomes a **contact** in the CRM (creates or updates).

## Confirmation code (OTP)

Like proving you own the email or phone:

1. Fill in the form.
2. Receive a **6-digit** code.
3. Type it in chat.
4. Then chat freely.

### Channels

| Channel  | Requirement           |
| -------- | --------------------- |
| Email    | Verified email domain |
| SMS      | Automatic             |
| WhatsApp | Active instance       |

With multiple channels active, the code may go through **all**. The visitor confirms with whichever arrives first.

<Warning>
  Each OTP **uses credits** (real delivery). For many cases, required mode **without** OTP is enough.
</Warning>

* Valid for **10 minutes**
* Max **4 requests per minute** per person

## Automatic verification (site with login)

If the visitor **is already logged in**, your site can confirm identity and skip form and OTP.

1. Generate the **verification secret** in the dashboard.
2. On your site **server**, sign the data and send it to the widget.

<Info>
  Technical option: usually needs a developer. Without login on the site, use the normal form.
</Info>

The secret shows **once** when generated. Lost it? Generate a new one.

## Automatic protections

### Domains

Chat only runs on authorized sites. Code copied to another domain does not work.

### Message limits

| Protection       | What it does                     |
| ---------------- | -------------------------------- |
| Per conversation | Up to 50 messages (configurable) |
| Between messages | 1 s wait (configurable)          |
| Per minute       | Max 60/min per visitor           |

### Credits

Each AI reply **uses credits**. Abuse drains balance and chat stops. This protects against unexpected cost.

## Which mode to choose?

| Situation                       | Recommended mode       |
| ------------------------------- | ---------------------- |
| Online store (browsing visitor) | Open or optional       |
| Site with logged-in area        | Automatic verification |
| Post-sale support               | Required + OTP         |
| Lead landing page               | Optional + email       |
| Company blog                    | Open                   |

## Next steps

* [For developers](/en/ai-web-widget/api): OTP and session in custom integration
* [Tips](/en/ai-web-widget/boas-praticas)
* [AI chat on your site](/en/ai-web-widget/index)