Dao Le Me Privacy Policy
Last updated: July 9, 2026 Effective date: July 16, 2026 Version: 2.0
Important notice (please read first)
Dao Le Me ( “we”, “us”, “our”, or the “App” ) is a self-management health-habit tracking and support application offering logging, statistics, meditation audio, community interaction, reminders, device pairing, and related features.
This Privacy Policy (the “Policy”) explains how we collect, use, store, share, transfer across borders, and protect your personal information, and the rights you have under law.
Special reminders:
- The Service may process data related to your behavior habits, mood/energy self-ratings, and impulse/release logs. In some jurisdictions such data may be sensitive personal information / special-category data / health-related information. We process it only as needed for core features and apply stricter protections.
- The Service is not a medical device and does not provide diagnosis, treatment, or prescriptions; statistics and prompts are for self-management reference only.
- The Service is primarily for adults aged 18+. We do not intentionally market to children.
- Before use, carefully read this Policy and the Dao Le Me Terms of Service. If you disagree, stop registering, logging in, or using the Service.
- This document is a product compliance template and does not replace professional legal advice. Before public release, have qualified counsel review it against your entity, server locations, SDKs, and actual processing.
Questions: see “How to contact us”.
Table of contents
- Definitions and scope
- Categories of personal information we process
- Purposes, legal bases, and necessity
- Cookies and local storage
- Device permissions
- Sharing, processors, transfer, and public disclosure
- Cross-border transfers
- Storage location, retention, and security
- Your rights (China / EU / US common rights)
- Automated decision-making and personalization
- Minors
- Third-party services and SDKs
- Updates to this Policy
- How to contact us
- Governing law and dispute resolution
1. Definitions and scope
1.1 Definitions
| Term | Meaning |
|---|---|
| Personal information | Information recorded electronically or otherwise relating to an identified or identifiable natural person |
| Sensitive personal information / special-category data | Personal information that, if leaked or misused, may harm personal or property safety or dignity; in this Service mainly includes health-habit logs and mood/energy self-ratings (as classified under applicable law) |
| Processing | Collection, storage, use, handling, transmission, provision, disclosure, deletion, etc. |
| Service | Dao Le Me App (iOS / Android / other official clients), related backend APIs, and supporting services |
| User / you | A natural person who registers, logs in, or uses the Service |
1.2 Scope
This Policy applies to personal information processing when you use the Service via official clients, the website, or other entrances we recognize. It does not apply to third-party websites, third-party apps, or independent privacy policies of third-party community publishers (review those separately).
1.3 Controller identity
Under applicable law, the Dao Le Me operator is the controller / processor of your personal information (terminology varies by jurisdiction). For legal entity name, registered address, unified social credit code, or DPO details, request the latest entity information page by email.
Public contact email: dlm-support@jituiadmin.click
2. Categories of personal information we process
We follow principles of lawfulness, fairness, necessity, good faith, and data minimization. Bold items below are typically required for core features; others are optional or collected only when you enable related features.
2.1 Account and identity
- Username and password (passwords stored with irreversible or industry-standard protection)
- User ID and login credentials (e.g. session tokens / JWT)
- Optional: nickname, avatar, bio
- Optional: language preference, dark mode, app-lock settings (including local PIN configuration; PINs are not uploaded or are handled only in protected form, depending on implementation)
2.2 Health-habit and status information (may be sensitive)
When you use logging, stats, achievements, etc., we may process:
- Log type (e.g. impulse, release/relapse categories you submit)
- Time, frequency, notes, triggers, and other content you enter
- Energy, mood, or other self-rating scores or tags
- Derived streaks, status scores, trends, goal progress, XP, levels, achievements
- Aggregate statistics used for risk tips or predictive displays (if any)
We do not proactively require medical records, prescriptions, genetic data, or clinical diagnosis reports. Do not put others’ private data or highly sensitive unrelated information in notes.
2.3 Community and social
- Posts, comments, likes, favorites, topics, and ranking interactions
- Friend relationships, friend requests, invite-code use (if any)
- Profile information you choose to publish; search history (if any)
- Report, block, and other safety-moderation actions
Content you publish publicly may be viewed, shared, or quoted by others—post carefully.
2.4 Content consumption
- Meditation/audio progress, duration, playlists, and favorites
- Article reading records and browsing history
2.5 Messages, reminders, and notifications
- In-app messages, system notices, and read status
- Reminder times, recurrence, and toggles you set
- Device push identifiers needed for delivery (e.g. system push token after you allow notifications)
2.6 Device, logs, and security
To keep the Service secure and stable, we may automatically collect:
- Device model, OS version, App version, language, and time zone
- Device identifiers (within lawful and necessary scope, e.g. risk control, anti-abuse, device management)
- IP address, network type, request time, API access logs
- Crash logs and performance diagnostics
- Login device lists and abnormal-login detection data
2.7 Watch / paired devices (if used)
- Pairing status, device name/model-type identifiers, authorization and unbind records
- Temporary codes or session data needed to complete pairing
2.8 Information we do not proactively collect
- Precise location (unless a future feature clearly requests and you authorize it)
- Contacts, SMS, call logs
- National ID, bank card numbers, or biometric templates you did not provide (system face/fingerprint unlock is handled by the OS; we generally cannot read raw biometric templates)
3. Purposes, legal bases, and necessity
3.1 Main purposes
| Purpose | Main data | Required? |
|---|---|---|
| Registration/login, account security, sessions | Account, credentials, device & logs | Yes |
| Habit logs, stats, goals, achievements | Logs and status data | Required when using the feature |
| Community and content distribution | Community content and relationships | Required when using the feature |
| Audio/article content | Play/read records | Required when using the feature |
| Reminders and messages | Reminder config, push IDs | Required when enabled |
| Device pairing | Device and pairing info | Required when using the feature |
| Security, anti-fraud, audit/compliance | Logs, device, behavioral signals | Yes |
| Product improvement and bug fixes | De-identified/aggregate analysis, crash logs | Usually legitimate interests or consent |
| Rights requests and support | Contact info and ticket content | As needed |
3.2 Legal bases (as applicable where you live)
Depending on jurisdiction, we may process personal information based on one or more of:
- Contract performance / providing the Service you request (e.g. account, log sync)
- Consent (especially sensitive data, push notifications, optional profiling)
- Legal obligation (e.g. regulatory requirements, retaining certain logs)
- Legitimate interests (e.g. security, abuse prevention; balanced against your rights)
- Vital interests (emergencies, where law allows)
In the People’s Republic of China, we primarily rely on the Personal Information Protection Law, Cybersecurity Law, Data Security Law, and similar rules, using notice-and-consent, contract necessity, legal obligations, and other lawful bases; for sensitive personal information we obtain separate consent or rely on other statutory exceptions.
In the EEA / UK / Switzerland, we rely on GDPR / UK GDPR bases; special-category data is processed only with explicit consent or other lawful exceptions.
In California and other US states, we disclose business purposes, rights, and “sale/share” practices as required (see §9.3).
4. Cookies and local storage
We may use:
- Local storage (e.g. SharedPreferences, secure storage, cache) for login state, theme, language, drafts, etc.
- Cookie-like technologies (if any web surfaces exist) for sessions and preferences
Uses: stay signed in, security, preferences, performance. You may clear App data/cache in system settings; you may need to log in again and some local preferences may be lost.
We do not use local storage to sell your habit logs to third-party ad networks.
5. Device permissions
| Permission | Use | Can refuse? |
|---|---|---|
| Notifications | Reminders, push messages | Yes; no push if refused |
| Photos/camera (if used) | Avatar, post images | Yes; related uploads unavailable |
| Network | Sync data, load content | Online features unavailable if refused |
| Bluetooth / nearby devices (if needed for watch pairing) | Device connection | Yes; pairing unavailable |
Permission prompts explain purpose when the feature is used. You can revoke permissions anytime in system settings.
6. Sharing, processors, transfer, and public disclosure
6.1 General principles
We do not sell your personal information. We share only what is necessary for the purposes in this Policy and require recipients to protect data at least as well as this Policy requires.
6.2 Possible sharing / processing scenarios
- With your consent or at your direction (e.g. public profile, community posts)
- Service providers / processors: cloud hosting, object storage, push, email, crash analytics, CDN, etc. (only as needed to run the Service)
- Affiliates: to provide the Service under purpose limitation and security requirements
- Legal requirements: lawful requests from courts or regulators
- Emergencies: protecting your or others’ vital interests
6.3 Transfer
In mergers, acquisitions, reorganizations, or bankruptcy, if personal information is transferred, we will require the successor to honor this Policy or obtain new authorization where required by law.
6.4 Public disclosure
Except with your clear consent or legal mandate, we do not publicly disclose your personal information, other than content you voluntarily post in the community.
6.5 De-identification and anonymization
We may use de-identified or aggregated data to improve the product; fully anonymized data may no longer be subject to personal information obligations under applicable law.
7. Cross-border transfers
7.1 Default storage
Personal information collected and generated in the People’s Republic of China is in principle stored in mainland China.
7.2 If cross-border transfer occurs
If cloud services, global collaboration, or your cross-border use require providing personal information overseas, we will:
- inform you of overseas recipient identity/contact, purposes, means, categories, and how to exercise rights (when required by law);
- obtain separate consent or other lawful bases as required;
- use SCCs, certification, security assessments, or other applicable safeguards;
- transfer only the minimum data needed.
EEA/UK users: transfers follow GDPR Chapter V mechanisms (adequacy, SCCs, etc.).
8. Storage location, retention, and security
8.1 Retention
We keep personal information only as long as needed for the purposes, for example:
| Data type | Typical retention (may be adjusted as required by law) |
|---|---|
| Account data | While the account exists + post-deletion legal periods for disputes/compliance |
| Habit logs and stats | While the account exists, or cleared per policy after delete/deletion request |
| Community content | Until delete/compliance handling completes |
| Logs and security data | Usually 6–24 months, or longer if required by law |
| Backups | Rolling backup cycle, then overwrite or destroy |
After the period ends we delete or anonymize, unless law requires otherwise.
8.2 Security measures
We take reasonable technical and organizational measures, including:
- transport encryption (e.g. TLS)
- access control, least privilege, audit logs
- password and credential protection
- secure development lifecycle and vulnerability response
- employee confidentiality and permission management
- incident response plans; timely notice to you and regulators when required if an incident may harm your rights
Note: no measure is absolutely secure. Protect your password, enable optional app lock, and avoid staying logged in on shared devices.
9. Your rights
To the extent applicable law allows, you may exercise the following rights via in-app features or email:
9.1 General rights
- To be informed and to decide: understand processing rules; choose whether to consent
- Access / copy: obtain a copy of your personal information
- Correction / completion: correct inaccurate or incomplete information
- Deletion: request deletion where legal grounds apply
- Withdraw consent: without affecting processing based on consent before withdrawal
- Delete account: stop the Service and delete or anonymize as required by law
- Explanation: request explanation of processing rules
- Complaint: complain to a competent authority
9.2 Additional rights in EU / UK and similar regions (if applicable)
- Restriction of processing
- Data portability
- Object to processing based on legitimate interests
- Object to direct marketing
- Not be subject to decisions based solely on automated processing (including profiling) that produce legal or similarly significant effects (we do not currently make such solely automated decisions with major legal effects)
- Lodge a complaint with a supervisory authority
We respond to valid requests as soon as possible and usually within 30 days (extensions allowed by law for complex cases, with reasons).
9.3 US state rights (e.g. California) (if applicable)
California residents may have rights to:
- know categories of personal information collected and business purposes
- delete and correct
- opt out of “sale” or “sharing” of personal information (we do not sell personal information as a business; if future “sharing” for cross-context behavioral advertising exists, we will provide an opt-out)
- exercise privacy rights without discrimination
How to request: email dlm-support@jituiadmin.click with subject “Privacy Request”, stating request type and verifiable identity information.
9.4 China-specific notes
Under the PIPL you may access, copy, correct, delete, withdraw consent, and delete accounts, among other rights. For sensitive personal information we fulfill separate consent and impact-notice duties (except statutory exceptions). We process requests within 15 working days (or other statutory timelines).
9.5 Limits
We may lawfully be unable to fully fulfill requests involving national security, public security, litigation evidence, others’ legitimate rights, or technical infeasibility. We will explain reasons.
10. Automated decision-making and personalization
We may use rules or models to produce:
- statistical displays such as status scores, trends, and goal completion
- content ranking or recommendation lists (if any)
These usually improve experience and do not constitute automated decisions with legal or similarly significant effects. You may reduce use of related features, adjust settings, or contact us to limit non-essential personalization.
11. Minors
- The Service is primarily for adults 18+.
- We do not knowingly collect personal information from children under 13 (or a higher age threshold where you live, e.g. 16).
- If you are a minor, read this Policy with a guardian and use only with guardian consent.
- If we learn we collected children’s information without valid consent, we will delete it promptly.
- Guardians exercising rights should email us with reasonable proof of guardianship.
Areas with adult-oriented or sensitive community content (if any) are for adults only; do not help minors bypass restrictions.
12. Third-party services and SDKs
To provide push, crash analytics, cloud storage, etc., we may integrate third-party SDKs or services. We will:
- integrate only what is needed for functionality
- require security and data-processing commitments
- update in-app notices, this Policy, or a third-party list when the inventory changes
Principle: your detailed health-habit records are not provided to ad platforms for cross-app ad tracking.
Request the latest third-party SDK list (name, purpose, fields, privacy links) by email.
13. Updates to this Policy
We may revise this Policy from time to time. For material changes we will notify you via prominent in-app notice, dialog, or inbox message, and update the date and version at the top.
Material changes include, without limitation:
- major changes to purposes, means, or categories of personal information
- major changes to controller identity or organization
- major changes to main sharing/cross-border recipients
- major changes to your rights or how to exercise them
If renewed consent is required, we will seek it before you continue use. Historical versions may be requested from us.
14. How to contact us
- Email: dlm-support@jituiadmin.click
- Suggested subjects:
- “Privacy rights request”
- “Data deletion / account deletion”
- “Security incident report”
We respond within applicable statutory timelines (commonly 15 working days in mainland China; 30 days under GDPR, with lawful extensions).
If unsatisfied with our response, you may complain to a competent personal information / data protection authority where you live.
15. Governing law and dispute resolution
- Formation, validity, interpretation, and dispute resolution under this Policy are primarily governed by the laws of the People’s Republic of China (for this Policy, excluding Hong Kong, Macao, and Taiwan law), except where mandatory consumer or data-protection rules provide otherwise (e.g. non-waivable rights of EEA users).
- Disputes should first be negotiated amicably; failing that, either party may sue in a people’s court with jurisdiction at our domicile, unless mandatory jurisdiction rules apply.
- If this Policy conflicts with the Dao Le Me Terms of Service, personal information protection matters are governed by this Policy.
- Invalidity of part of this Policy does not affect the remainder.
Appendix A: Personal information collection list (summary)
| Scenario | Information | Purpose | Can refuse? |
|---|---|---|---|
| Register/login | Username, password, token | Account service | No (otherwise cannot register/login) |
| Profile | Nickname, avatar, bio | Display and social | Yes |
| Habit logs | Log content, time, self-ratings | Core tracking | Not required if feature unused |
| Stats/achievements | Derived stats, XP, levels | Feedback and motivation | Produced from logs |
| Community | Posts, comments, interactions | Community features | Yes |
| Audio/articles | Play/read records | Content experience | Yes |
| Reminders/messages | Reminder config, push token | Notifications | Yes |
| Security logs | Device, IP, logs | Security and compliance | Usually necessary |
| Device pairing | Device IDs and pairing status | Watch and related features | Yes |
Appendix B: Sensitive personal information processing (summary)
| Type | Purpose | Key protections |
|---|---|---|
| Habit/impulse/release logs and self-ratings | Logging, stats, goals, achievements | Transport encryption, access control, minimization, not for sale |
| Community content that may contain sensitive meaning | User publication and moderation | Do not post others’ private data; handle violations as required by law |
Dao Le Me Team Version 2.0 · July 9, 2026