# User Privacy Protection Guidelines
In order to regulate the user's personal information processing activities of developers and protect the legitimate rights and interests of users, developers who deal with the user's personal information in Mini programs and plug-ins need to supplement the corresponding user privacy protection guidelines.
Fill in the detailed explaination can be seenPrivacy Protection Guidelines for Small Program Users、Plug-in user privacy protection instructions content。
# I. Guidelines on Privacy Protection for Users of Mini Programs
# 1, fill in the current network version user privacy protection guidelines
Entry 1: SettingFunction settingsUser Privacy Policy
Developers can improve or update the privacy agreement based on the current version of the Mini Program at any time, and it will take effect after the review is passed. Users can view the privacy guidelines in the Mini Program More Information page and in the pop-up window.
# 2. User Privacy Protection Guidelines
Entry 2: ManagementVersion managementSubmit Code ReviewInformation Fill Out Page
Each time the developer submits the code for review, the platform defaults to pull the current network version of the Mini Program privacy agreement, and enters the platform for review as the development version of the privacy agreement. If the development version submitted for review has a discrepancy between the privacy interface call and the privacy agreement content, or the privacy agreement content is empty, the developer will be reminded to update at the time of arraignment.
Changes to the content of the development version of the Privacy Agreement at this entrance will not affect the current version of the Privacy Agreement. Similarly, the changes to Portal 1 are only for the current version of the privacy agreement. If the development version is approved and released, the privacy agreement of that version will be released at the same time as the privacy agreement of the previous version of the current network.
Note: If the arraignment version is blocked, please update the privacy agreement at the current entrance, Entrance 2.
# 3. User Privacy Protection Guidelines for Configuration of Small Programs Through Interfaces
On behalf of the development of small procedures can only be configured through the interface user privacy protection guidelines, you can refer to[Guidelines for Third Party Platforms](https://developers.weixin.qq.com/doc/oplatform /Third-party_Platforms/2.0/product/privacy_setting.html)。
# II. Plug-in User Privacy Protection Instructions
# 1, fill in the online version of the user privacy protection instructions
Entry 1: Mini Program plug-inSet upUser Privacy Protection
Developers can improve or update the privacy statement of the latest online version of the plugin at any time, and it will take effect after the approval. Users can view this version of the Mini Program in the More Information page, Privacy Guide.
Improvements or updates to the Privacy Statement for online non-current versions are not supported at this time.
# 2. Fill in the Arraignment Version User Privacy Protection Instructions
Entry 2: Mini Program plug-inSubmission for reviewUnable to submit review popup - go to perfect
Each time the developer submits the code for review, the platform pulls the latest online version of the plugin by default. Compared with the privacy interface call of the current submission audit version, if the current submission audit release calls the privacy interface that is not included in the latest online version of the privacy statement, the developer will be reminded to submit the privacy statement for review first.
After developers improve the privacy statement, they need to wait for the privacy statement to be approved before submitting a version. Approval of the privacy statement will be notified to the plugin developer via a service notice.
Note: If the arraignment version is blocked, please update the privacy agreement at the current entrance, Entrance 2.
If the current submission review version removes the privacy interface included in the privacy statement of the latest online version and cannot be edited at arraignment, it is recommended that developers make changes through Entry 1 after the release of the version.
