DevMate Privacy Policy (Android China)
Version 2.3.1. Effective date: 2026-10-16. 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 DevMate for Android distributed through mainland China channels and related deeplink testing, command lookup, device information, memos, schedule/alarm reminders, developer tools, feedback, legal page, analytics, advertising, and support services.
2. Information We Process
- URLs, JSON, text, timestamps, colors, QR code content, commands, memos, schedules, reminder times, and reminder rules that you enter or generate. Unless you actively submit, share, or use an online feature, tool input is generally processed locally.
- Device information tool results. The app does not read Android ID as a general startup identifier; only when you actively open the Device Info tool does the app read Android ID through Android system APIs to display or copy it locally.
- QR/barcode content in the camera view when you actively scan, feedback content, contact details, screenshots or image attachments, 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 impression, click, and redirect 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.
- First-party promotion center: used for our own app promotions, operating slots, impressions, clicks, and redirect statistics.
- Android WebView, system camera, system file picker, system alarm, and notification capabilities: used for legal/page display, scanning, feedback attachments, and local reminders.
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
DevMate Android China may use network access, network state, camera, notifications, exact alarm, boot-completed broadcast, legacy storage/media selection, system file picker, clipboard write, WebView, and advertising-related system capabilities. Restart recovery is used only while valid schedule/alarm reminders exist and is no longer used for reminder recovery after all valid reminders are deleted or disabled.
Boot start (restoring enabled reminders)
After you have agreed to this Privacy Policy and at least one valid, future, non-all-day reminder exists on the device, the app enables its local BootReceiver component. It receives the system broadcast android.intent.action.BOOT_COMPLETED, reads the corresponding local reminder rules after the device finishes restarting, and re-registers the system alarms to restore the local reminders you enabled. This broadcast is used to restore the reminders you enabled; it is not used to open a foreground app page or for promotional re-engagement through the boot broadcast.
If you have not agreed to this Privacy Policy, or no such reminder remains valid, the component remains disabled. After all valid reminders are disabled or deleted, the app disables the boot recovery described above; you can stop the corresponding recovery by disabling or deleting the reminder.
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. DevMate is a general developer 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: URLs, JSON, text, timestamps, colors, commands, QR content, memos, schedules, and reminder rules that you enter or generate continue to be processed mainly on the device. The Device Info tool reads Android ID and other results through Android system APIs only when you actively open it and displays them locally. 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, screenshots or image attachments, app version, channel, device maker/model, OS version, and installation ID are used for issue submission, diagnosis, and response. Android Umeng analytics, GroMore/Pangle advertising, and first-party promotion continue to use the Android ID, OAID, device/network/IP data, sensor list, app events, ad events, and promotion events described in the relevant sections of this Policy.
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.