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 a basic protection measure and is limited to text content (up to 50 sensitive words by default). It cannot replace professional content moderation services.
- RC's Content Moderation Service Product includes IM Moderation services, which provide 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 your own moderation or integrate with a third-party moderation service, you can use the Message Callback Service.
If a message is blocked due to being flagged as violating rules, the sender will not be notified by default. If the app wishes to notify the sender that the message has been blocked, 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 more details, refer to Message Block Notification Callback.
Sensitive Word Mechanism
Note
- The client does not provide a management interface for this feature, only a callback interface to notify the sender when a message is flagged as undeliverable. For more details, refer to 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 Product.
The Sensitive Word Mechanism is a basic protection mechanism that only supports the identification and filtering of sensitive words in text message content. For messages that contain 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 through 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 the list of sensitive words, 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 Adjustment
- 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 Instructions document.
- If you wish to filter sensitive words in 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 JSON structure to filter the value of that key for sensitive words.
IM Content Moderation Service
Note
The client does not provide a management interface for this feature, only a callback interface to notify the sender when a message is flagged as undeliverable. For more details, refer to Message Block Notification Callback.
If you wish to comprehensively moderate IM content, you can use RC's Content Moderation Service Product, which provides IM Moderation and RTC Moderation services.
IM Moderation is tailored for instant messaging and offers the following capabilities:
- Moderation of text content
- Moderation of images
- Moderation of voice clips
- Moderation of short videos
- Moderation of custom message types (requires ticket submission)
- Moderation of 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 address to receive moderation result callbacks. For more details, refer to the server-side 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 to use the service. For specific billing details, refer to Pricing Standards · IM Moderation.
Message Callback Service
If you wish 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 relevant messages to your specified server based on parameters such as sender ID, recipient ID, message type, and conversation type. In ultra group business, modifications to message content and updates to message extensions are also supported for synchronization to your specified server.
Once messages are synchronized to your specified server, you can use your own moderation system to perform content moderation or integrate with a third-party moderation system. RC's server will determine whether to deliver the message, replace the content, and how to replace the content based on the response from your application 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 parameters for callbacks, refer to the Message Callback Service documentation.
Message Callback Service Billing
Fees are subject to the Billing Instructions document.