Moderation, GDPR and limits
Blocked words, AI moderation, GDPR consent and rate limiting for the Aimogen Pro chatbot, and how to configure them before going public.
A public chatbot is an input field connected to a paid API. These settings are what stand between it and misuse.
AI Chatbot › Moderation and AI Chatbot › Limitations
Input filtering#
| Setting | What it does |
|---|---|
Blocked Words From Chat Input | Messages containing these are rejected before any API call |
Enable User Message Moderation | Runs input through a moderation model first |
AI Moderation Model | Which model performs it |
Flagged Text Message | What the visitor sees when a message is flagged |
Blocked words cost nothing and are checked locally. AI moderation is more capable but adds a request and some latency to every message.
For most sites, a blocked-word list plus a well-written Bot Context is enough. Enable AI moderation when the audience is large or the topic is sensitive.
Rate limiting#
| Setting | What it does |
|---|---|
Limit User Messages - Max Requests / Time Window | For example 10 messages per 60 seconds |
Error Message When User Exceeded The Limit | What the visitor sees |
Total Token Cap Per Day For Users | A daily token ceiling. Also restricts guests |
Single Message Max Input Length (Characters) | Longest message accepted |
Disable Sending Of Empty Chat Messages | Rejects empty submissions |
Rate limiting is not the same as usage limits. Rate limiting caps the speed; usage limits cap the total. Configure both.
GDPR consent#
| Setting | What it does |
|---|---|
Require GDPR Consent Before Users Can Access The Chatbot | Shows a consent gate before the conversation |
Privacy Policy Notice | The notice text |
Privacy Policy Consent Checkbox Label | The checkbox label |
Privacy Policy Consent Button Text | The button label |
This tutorial was recorded before Aiomatic was renamed to Aimogen Pro. Some labels or interface elements may differ slightly from the current version.
Whether you need this depends on where your visitors are and what you do with the conversation. What is true regardless:
- Messages are sent to a third-party AI provider, potentially outside your jurisdiction.
- With persistent chat, conversations are stored in your database.
- With detailed usage tracking, prompt and response text is stored too.
- With lead capture, contact details are stored.
A notice that reflects that:
This chat is powered by AI. Your messages are sent to our AI provider to
generate a response, and are stored so we can improve our service. Do not enter
payment details, passwords or sensitive personal information.
See our privacy policy for details.%%privacy_policy_url%% renders your configured privacy policy URL.
Access restrictions#
From usage limits:
| Setting | Effect |
|---|---|
Restrict User IDs List From Using The AI | Block specific users |
Restrict User IPs List From Using The AI | Block specific IPs |
Max Guest Credits | Cap what non-logged-in visitors may consume |
Full Access Users | Users exempt from all limits |
Setting Max Guest Credits to zero effectively makes the chatbot login-only.
The aiomatic_get_ip filter lets you adjust IP detection behind a proxy or CDN, which matters if all
your traffic appears to come from one address. See Filter reference.
Output safety#
| Setting | What it does |
|---|---|
Strip JavaScript From Chatbot HTML Responses | Removes scripts from replies. Keep this on |
Enable Chatbot Full HTML Response Processing | Allows HTML at all |
Chat Compliance Text | Standing disclosure below the input |
A public-ready configuration#
AI Chatbot > Limitations
Limit User Messages: 10 per 60 seconds
Single Message Max Input Length: 2000 characters
Disable Sending Of Empty Chat Messages: on
AI Chatbot > Moderation
Blocked Words: your list
Strip JavaScript From HTML Responses: on
Require GDPR Consent: if you are in scope
AI Chatbot > API Parameters
Chatbot Max Token Count: a modest value
Store AI Prompts On OpenAI's Part: off if you process personal data
System & Logs > AI Usage Limits
Enable Global Usage Limits: on
Max Guest Credits: a low number
Time Frame: dayPlus a spend cap in your provider dashboard, which is the only control the plugin cannot bypass.
Related#
Still stuck? Open a support ticket and include the diagnostics from Aimogen Pro › System & Logs › System Info.