1. Scope and developer
This policy concerns DingDing: Alarm Clock & Timer, a product of ThinkBlox PH operated by Juan Carlos Claridad in the Philippines. It is distinct from the ThinkBlox PH website policy and from other products' policies.
2. Data accessed or handled
- Alarms, labels, timer settings, medicine names or labels, reminder schedules, and dose-completion history that a user chooses to enter in the app.
- Device alarm and notification functions needed to deliver scheduled reminders. The precise Android permissions and any use of boot or background scheduling must be checked against the release manifest.
3. Data collected or stored
- Users can create alarms, medicine schedules, and dose records within DingDing. Whether this information stays entirely on the device, is included in backups, or is sent to any external service has not yet been independently verified.
- The presence or absence of third-party diagnostics, analytics, or device identifiers in the release build is still being checked. This notice does not claim there is no third-party data collection.
4. Purposes
- To schedule and display alarms, medicine reminders, snooze events, cooking countdowns, and dose progress.
- To generate QR codes or message content when a user explicitly chooses to share an alarm or medicine schedule.
5. Sharing and recipients
- If you deliberately share an alarm or medicine schedule by QR code or message, the people or applications you choose to share it with may receive the schedule details.
- Any automatic sharing by SDKs, backups, or network requests has not yet been confirmed.
6. External services
Additional third-party services and SDK behavior have not yet been confirmed. This notice does not claim that the product uses no third-party services.
7. Device or browser permissions
- Device notifications and alarm scheduling are used for the advertised reminder features. Actual permission names, purpose, and behavior must be confirmed from the AndroidManifest.xml and runtime permission requests.
- QR-based sharing behavior, including whether camera permission is requested for scanning, must be confirmed from the released app.
8. Security
The release app's storage protections, backups, network connections, and SDK behavior have not yet been audited. Information about these safeguards will be updated when confirmed.
9. Retention
The period for which alarms, medication schedules, and completion history remain on-device or in backups has not yet been verified. No specific automatic deletion or retention period is currently stated.
10. Deletion and account controls
Any in-app removal or clearing of schedules and medicine records must be tested before it is described as a complete deletion method. For privacy questions, contact the developer using the address below.
11. Children and age-related privacy
DingDing is an everyday reminder application. Any children-related use, target audience settings, and additional protections require confirmation before release.
12. International data handling
Whether any technical or user data leaves the device (for example through SDKs, backup, or integrations) requires verification. Sharing through third-party messaging services may involve processing under those services' own policies.
Policy updates
This notice may change after implementation reviews or product updates. The updated date will be revised when the disclosed practices change. Android app policies must agree with their current Google Play Data safety disclosures.
Contact for privacy inquiries
Developer: ThinkBlox PH · Juan Carlos Claridad · Philippines
Email: juanc.claridad@gmail.com
Include the product name and the nature of your request. Do not include passwords, recovery phrases or private keys.