According to the requirements of the relevant app compliance departments, a pop-up box prompting the user agreement and privacy policy will pop up when the app is launched for the first time. Basically, most apps have already implemented this function. The first pop-up box usually has two buttons, agree and continue and disagree. Now it is required that when the user clicks to disagree, they cannot exit the app directly, and the user needs to be provided with a browsing mode.
Browsing mode cannot collect any user information. There are generally two methods: the first is to remove all functions on the app homepage that require permissions and obtain and collect sensitive device information. The second one is to write a special browsing mode, which only provides browsing for about two or three pages. The first one is more troublesome to implement, mainly because it requires additional logical judgment and has better experience, while the second one is relatively simple. But no matter which approach you take, don’t forget to add the logic of user agreement and privacy policy pop-up boxes to prompt users for some functions that require permissions or device information. My approach here is the second one, is it also responding to compliance?
As shown in the following three pictures, when the user clicks on the still experience to jump to the browsing mode, when the user clicks on the camera in the upper right corner of the browsing mode, a prompt box will pop up because this function involves user permissions. When the user clicks to agree and continues to restart the app, the logic will be exactly the same as starting the app normally. (Picture source from the Internet, deleted due to infringement)
Hope this article is helpful to you. I wish you an early escape from the hardships of compliance rectification.