Mirly Privacy Policy (Android China)
Version 2.3.0. Effective date: 2026-10-14. Applies to the android / cn release.
Platform: Android Distribution region: mainland China channels Developer: Beijing Chenghan Bowen Education Technology Co., Ltd. Contact: contact@chenghanbowen.com
1. Scope
This Policy applies to Mirly for Android distributed through mainland China channels and related mirror preview, photo capture, video recording, media saving, sharing, feedback, legal page, analytics, advertising, first-party promotion, and support services.
2. Information We Process
- Real-time camera preview, front/rear camera switching, zoom, brightness, lighting, and other local states. By default, preview frames are processed locally in real time and are not used for face recognition.
- Photos, videos, and video audio that you actively capture, preview, save, or share, and image/video files or feedback attachments that you actively select.
- Feedback content, contact details, app version, device model, system version, channel, installation instance ID, and legal page parameters.
- After you consent, Android ID, OAID/GUID, device/app information, network status, IP address, page/tap/crash events, ad impression/click/close events, and first-party promotion events.
3. Region-Specific SDKs and Services
- Umeng mobile analytics: used only after privacy consent for basic analytics, channel analysis, and diagnostics.
- GroMore / Pangle advertising SDK: used only after privacy consent and when ad configuration is enabled for ad requests, impressions, clicks, frequency control, measurement, and anti-fraud.
- Android CameraX / system media services: used for mirror preview, photo capture, video recording, media saving, and sharing.
- First-party promotion center: used for our own app promotions, operating slots, impressions, clicks, and redirect statistics.
Third-party SDKs or services work only after you agree to this Privacy Policy, grant any required system permission, and enable the relevant feature or ad configuration.
4. Permissions and System Capabilities
Mirly Android China may use camera, microphone, image/video read and write, photo/video selection, notifications, network access, network state, WebView, advertising-related system capabilities, and first-party promotion-related system capabilities. Camera, microphone, and media permissions are requested only when needed for mirror preview, photo capture, video recording, saving, sharing, or feedback attachments; microphone audio is not collected when you are not recording video.
5. Your Rights
We do not sell your personal information. You can manage permissions in Android settings or contact contact@chenghanbowen.com to request access, correction, deletion, or withdrawal of consent. If this Policy differs from a feature-specific notice, the notice that better protects user rights will apply.
Children's Personal Information Protection Rules
This is a standalone children's personal information section within this Privacy Policy. “Child” means a minor under 14. Mirly is a general mirror tool and is not specifically directed to children.
When the app is first opened or asks for privacy consent again, if the user may be under 14, a guardian should read this section and this Policy first and decide whether to consent. Before guardian consent, you may continue to use Basic Services that do not depend on that consent. Processing that needs separate consent or an active request occurs only when its stated conditions are met. We do not ask children to provide a birthday, age, identity document, or similar information for routine use.
Current processing facts for this platform:
- Local content: Real-time camera preview, camera switching, zoom, brightness, photos, videos, video audio, media saving/reading, and system sharing continue to be processed on the device for the existing features; preview frames are processed locally in real time and are not used for face recognition. The three platforms currently provide no account registration or sign-in.
- Active feedback, installation, device, and SDK data: When you actively submit feedback, feedback content, contact details, app version, device model, OS version, channel, installation ID, and selected image/video attachments are used for issue handling. Android Umeng, GroMore/Pangle, and first-party promotion are described in the relevant sections of this Policy to process Android ID, OAID/GUID, device/network/IP data, sensor list, app events, ad events, and promotion events; no mirror preview, photo, or video content is newly provided to those SDKs.
The retention period, storage location, sharing scope, and handling by third-party services for children's information are described in the corresponding storage, sharing, and third-party service sections of this Policy. When a guardian makes a request, we handle it under this Policy and applicable law; previously submitted feedback or saved data is not automatically deleted.
A guardian may contact contact@chenghanbowen.com to request access to, correction or deletion of children's personal information, or withdrawal of the related consent. To prevent impersonation, we perform only necessary and proportionate verification for an application. If we discover that children's personal information was processed without guardian consent, we will stop the related processing and delete or anonymize it as required by applicable law.
Privacy Choices and Withdrawal
Use the app's Privacy Choices/Privacy Management entry in Settings to review the current state or choose again. If you previously consented, confirm “Withdraw Privacy Consent” before switching to Basic Services; canceling that confirmation leaves the existing choice unchanged. Resuming the relevant optional features requires your explicit consent and does not replay prior ad requests or impressions.
Withdrawal cancels current ad preparation and pending presentation, stops new advertising requests, and disables optional analytics and diagnostics controlled by the app. Basic features that do not depend on that consent remain available. SDK base instances, system diagnostics, or vendor-automatic behavior may still exist or run; this does not mean all SDKs automatically stop and does not guarantee zero SDK activity before consent. Withdrawal does not affect processing already lawfully completed or automatically delete submitted feedback or previously saved data. Deletion requests use the existing contact and handling procedures.
The app's main privacy choice is separate from system permissions and personalized-ad settings. Limiting personalization neither withdraws main privacy consent nor means ads process no information. This CN shell does not add the Global Google/Firebase/AdMob/UMP route. Any ATT system authorization that actually applies on iOS does not replace the app's main privacy choice.