Content Moderation Overview
The Instant Messaging (IM) service supports content moderation.
- The IM service has a built-in sensitive word mechanism. Note that this mechanism is only a basic protection feature and is limited to text content (with a default maximum of 50 sensitive words). It cannot replace professional content moderation services.
- RC's Content Moderation Service provides comprehensive protection and support for IM content, including text, images, voice clips, and short videos, with precise identification of sensitive information.
- If you wish to implement moderation on your own or integrate with a third-party moderation service, you can use the Pre-messaging Callback service.
If a message is blocked due to being flagged as violating content, the sender will not be notified by default. If your app wishes to notify the sender that the message has been intercepted, you can submit a ticket to enable the Blocked Message Status Callback to Sender feature and set up a listener on the client side (requires Android/iOS SDK version ≧ 5.1.4, Web ≧ 5.0.2). For details, see Message Block Notification Callback.
By default, one-to-one chat messages that are flagged as containing sensitive words or fail moderation will still be stored in the sender's server-side message history. Additionally, the user will receive this message as a compensation when logging in from other devices. If you do not want messages containing sensitive words or failing moderation to be stored in the sender's message history or compensated, you can enable the Skip history for filtered messages feature in the RC Console under Configuration > Chat settings > Basic features > Security.
Sensitive Word Mechanism
- The client does not provide management interfaces for this feature, only callback interfaces to notify the sender when a message is flagged as undeliverable. For details, see Message Block Notification Callback.
- If you need to moderate text (with semantic detection), images, voice clips, or short videos, it is recommended to use RC's Content Moderation Service.
The Sensitive Word Mechanism is a basic protection feature that only supports identifying and filtering sensitive words in text message content. For messages that contain sensitive words, you can choose to block the message (not deliver it to the recipient) or replace the sensitive words according to specified rules before delivery.
Currently supported languages for sensitive word filtering include: Chinese, English, Japanese, German, Russian, Korean, and Arabic.
You can manage sensitive words for the development or production environment under your App Key using the following methods:
| Function Description | Client API | RC Server API | Console |
|---|---|---|---|
| Add sensitive words, with support for setting replacement content | Not provided | Add Sensitive Word | Sensitive Word Settings page |
| Remove sensitive words | Not provided | Remove Sensitive Word | Sensitive Word Settings page |
| Batch remove sensitive words | Not provided | Batch Remove Sensitive Word | Sensitive Word Settings page |
| Get sensitive word list, with support for retrieving replacement content | Not provided | Get Sensitive Word List | Sensitive Word Settings page |
Default Behavior
- By default, a maximum of 50 sensitive words can be set.
- By default, it only applies to messages sent from the client SDK.
- By default, it only supports identifying sensitive words in official built-in text message types (message identifier
RC:TxtMsg). Supported conversations include one-to-one chat, group chat, chatroom, and ultra group. Modified text messages in ultra groups are also subject to sensitive word identification, blocking, or filtering by default.
Configuration Adjustments
- Chat Premium Plan or Chat Ultimate Plan users can adjust the maximum number of sensitive words in the Extended Services tab under the Chat pricing plans page in the console. Specific features and fees are subject to the Billing Documentation.
- If you wish to apply sensitive word filtering to messages sent via the server API, you can enable the Server API Message Filtering for Sensitive Words switch in the Basic Features Interface in the console.
- If you need to enable the sensitive word mechanism for custom message types, you can click Set Custom Messages on the Sensitive Word Settings page. Provide the
ObjectNameof the custom message type and the corresponding key in the content (Content) JSON structure to filter the value of that key for sensitive words.
IM Content Moderation Service
The client does not provide management interfaces for this feature, only callback interfaces to notify the sender when a message is flagged as undeliverable. For details, see Message Block Notification Callback.
If you wish to comprehensively moderate IM content, you can use RC's Content Moderation Service, which provides IM Moderation and RTC Moderation services.
IM Moderation is designed for instant messaging and provides the following capabilities:
- Moderation of text content
- Moderation of images
- Moderation of voice clips
- Moderation of short videos
- Moderation of custom message types (requires submitting a ticket)
- Moderation of message modifications in ultra group conversations
- Viewing moderation reports in the console
- Querying IM moderation records in the console
- Callback for moderation results
You can enable the IM Moderation service in the IM & RTC Moderation page in the console and configure the address to receive moderation result callbacks. For details, see the server documentation Moderation Result Callback.
IM Content Moderation Billing
The content moderation service is a paid service. The development environment offers a free trial, while the production environment requires prepayment to use the service. For specific billing details, see Pricing Standards · IM Moderation.
Pre-messaging Callback Service
If you wish to integrate your own moderation system or a third-party content moderation service, you can use the Pre-messaging Callback Service.
The Pre-messaging Callback Service (formerly Template Routing) provides a message filtering mechanism. You can synchronize specific messages to your designated server based on parameters such as sender ID, recipient ID, message type, and conversation type. In ultra group conversations, modifications to message content and updates to message extensions are also supported for synchronization to your designated server.
Once messages are synchronized to your designated server, you can use your own moderation system to perform content moderation or integrate with other third-party moderation systems. The RC server will determine whether to deliver the message, replace the content, and how to replace it based on the response from your application server.
You can manage the status and routing rules of the Pre-messaging Callback Service for the development or production environment under your App Key in the Pre-messaging Callback Service page in the console.
For details on how to create routing rules and the specific parameters for callbacks, please refer to the Pre-messaging Callback Service documentation.
Pre-messaging Callback Service Billing
Fees are subject to the Billing Documentation.