RC Chat provides a built-in sensitive word feature. This guide shows how to set it up in the Console. Supported languages for filtering include: Chinese, English, Japanese, German, Russian, Korean, and Arabic.
The sensitive word feature is a basic protection tool for text only (default limit: 50 words).
Steps
Go to the RC Console - Sensitive Words Settings page to:
-
Add or remove sensitive words
-
Choose actions: block messages or replace sensitive characters
-
Export the sensitive word list
-
Add custom message types for filtering (default: only works with RCâs built-in text messages, ObjectName:
RC:TxtMsg)
Click Add on the Sensitive Words Settings page and select the tab to add words.
Notify senders when a message is blocked
By default, senders arenât notified if a message is blocked due to sensitive words. If you want senders to know, submit a ticket to enable Blocked Message Status Callback to Sender and set up a listener on the client side (requires Android/iOS SDK version â§ 5.1.4, Web â§ 5.0.2).
See the âMessage Block Notification Callbackâ docs for each client:
-
Android: https://docs.rongcloud.io/android-imlib/moderation/sensitive
-
iOS: https://docs.rongcloud.io/ios-imlib/moderation/sensitive
-
Web: https://docs.rongcloud.io/web-imlib/moderation/sensitive
Enable sensitive word filtering for server API messages
By default, messages sent via the server API arenât filtered. To enable it, go to the Basic Features section in the Console and turn on Filter server API messages.
Set up sensitive word filtering for custom messages
Click Set custom messages on the Sensitive Words Settings page. Provide the ObjectName of the custom message type and the key in the content JSON structure. Once set up, the value for this key will be filtered.
Notes on message identifiers:
-
All message identifiers (ObjectName) you add will filter the content of their corresponding key. For example, the built-in âText Messageâ type (ObjectName:
RC:TxtMsg) filters the value of the âcontentâ key in the message body. -
Custom messages must follow SDK standards and be valid JSON.
-
Avoid starting with âRC:â to prevent conflicts with RCâs built-in message ObjectNames.
-
Test in the development environment before deploying to production to ensure filtering works. If it fails, submit a ticket.
References
Need help?
Submit a ticket if you have questions.


