Content Moderation Overview
The Instant Messaging (IM) service supports content moderation for IM messages.
- 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 Product provides comprehensive support for IM content, including text, images, voice clips, and short videos, ensuring accurate identification of sensitive information.
- If you wish to implement moderation yourself or integrate a third-party moderation service, you can use the Message Callback Service.
If a message is flagged as violating content policies and cannot be delivered to the recipient, the sender will not be notified by default. If your app wants to notify the sender that the message has been blocked, you can submit a ticket to enable the 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). For details, see Message Block Notification Callback.
By default, if a one-to-one chat message contains sensitive words or fails moderation, it will still be stored in the sender's server-side message history. Additionally, the user will receive a message compensation when logging in from other devices. If you do not want messages containing sensitive words or failing moderation to be saved in the sender's history or to trigger message compensation, you can enable the Do Not Save Sensitive Messages to Sender’s History 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.
- To moderate text (with semantic detection), images, voice clips, and short videos, it is recommended to use RC's Content Moderation Service Product.
The Sensitive Word Mechanism is a basic protection feature that only identifies and filters sensitive words in text message content. For messages containing sensitive words, you can choose to block the message (preventing it from being delivered 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 in 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, up to 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 want to apply sensitive word filtering to messages sent via the server API, you can enable the Server API Message Sensitive Word Filtering switch in the Basic Features Interface in the console.
- If you want 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 JSON structure, and the value of that key will be subject to sensitive word filtering.
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 want comprehensive moderation of IM content, you can use RC's Content Moderation Service Product, which provides IM Moderation and RTC Moderation services.
IM Moderation is designed for instant messaging and offers the following capabilities:
- Moderate text content
- Moderate images
- Moderate voice clips
- Moderate short videos
- Moderate custom message types (requires a ticket for application)
- Moderate message modifications in ultra group business
- View moderation reports in the console
- Query IM moderation records in the console
- Moderation result callbacks
You can enable the IM Moderation service in the IM & RTC Moderation page in the console and configure the callback address for moderation results. For details, see the server documentation Moderation Result Callback.
IM Content Moderation Billing
The content moderation service is a paid service. The development environment can be used for free, but the production environment requires prepayment. For specific billing details, see Pricing Standards · IM Moderation.
Message Callback Service
If you want to integrate your own moderation system or a third-party content moderation service, you can use the Message Callback Service.
The Message Callback Service (formerly Template Routing) provides a message filtering mechanism. You can synchronize messages to your specified server based on parameters such as sender ID, recipient ID, message type, and conversation type. In ultra group business, message content modifications and message extensions are also supported for synchronization to your specified server.
After messages are synchronized to your specified server, you can use your own moderation system or integrate a third-party moderation system. The RC server will determine whether to deliver the message, replace its content, and how to replace it based on the response from your app server.
You can manage the status and routing rules of the Message Callback Service for the development or production environment under your App Key in the Message Callback Service page in the console.
For details on how to create routing rules and the specific callback parameters, see the Message Callback Service documentation.
Message Callback Service Billing
Fees are subject to the Billing Documentation.