DayPilot Privacy Policy
Effective date: January 1, 2026
Last updated: 2026-10-24
Hangzhou Meita Technology Co., Ltd. operates DayPilot, also named 时光小筑 in Chinese. This policy describes how we collect, use, store, share and protect personal information across the unified app's Mainland China (CN) and International (GLOBAL) services and supported distribution channels.
Please read this policy before using the app. Contact us at contact@meita.app if you have questions. The company's name and registered address are given below.
Ad-free release
Starting with the ad-free release 1.0.68, Android, iOS and the subsequently updated HarmonyOS NEXT clients no longer include advertising SDKs, display app-open or list ads, or provide ad-personalization preferences. Basic analytics, first-party diagnostics and business functions retain their own consent and service-region controls. Advertising SDK disclosures for version 1.0.67 and earlier describe historical clients only; server ad switches are disabled, but older binaries may still contain SDKs, and disabling ads does not unload them.
1. Service regions and your account
CN and GLOBAL maintain separate accounts, business data, attachments and memberships. CN business servers are in mainland China; GLOBAL business servers are currently in the United States. CN attachments use Alibaba Cloud OSS; GLOBAL attachments use Cloudflare R2. Third-party login, email, AI, content safety, transcription and SDK processing may occur elsewhere, including mainland China. International service does not mean that every processor operates exclusively in the United States.
Language and service region are separate settings. On iOS you can choose a service on the login page after signing out. Domestic Android distribution and Harmony use CN; Google Play distribution uses GLOBAL. Switching does not transfer your account, content or membership. Sign in again when returning to a service. Purchases, restoration, renewals and refunds remain associated with the original service and account. Transactions with unproven ownership remain pending rather than being reassigned to the current account.
GLOBAL does not enable domestic advertising or Umeng analytics. The unified iOS app still includes SDKs used by CN. A region switch cannot guarantee the complete unloading of SDKs already initialized in CN. The disclosures in this policy cover the whole app, including CN functionality and historical versions where identified.
See the Personal Information Collection List and Third-Party Sharing List for additional details.
2. Information we process
Information you provide
- Accounts: GLOBAL email registration/login processes your email, verification codes, password credentials and verification/security results. Login passwords are not stored in plain text. Phone login processes your phone number and SMS code. Supported Harmony one-tap login processes phone and carrier authentication results. Apple, Google, WeChat, QQ, Douyin or Gitee login processes the identifiers and profile information returned within your authorization. Only the methods shown for your platform and service are available. We assign an account ID within its service region.
- Your content: event titles, dates, recurrence rules, reminders and notes; Countdown titles, types, original dates, repeat start dates, recurrence rules, reminders and notes; Habit goals and check-ins; Focus settings, durations and records; Notes, tags and categories; To-do titles, quadrants, schedule categories, deadlines and completion state; journals and preferences. We use this information to provide the functions you request and synchronize within the same service.
- Purchases: plan, price, order and transaction identifiers, payment channel, signed transaction records, account binding and fulfillment status. iOS digital memberships use Apple in-app purchase. Supported domestic Android/Harmony channels may offer one-time Alipay or WeChat payments. Payment providers handle payment passwords and payment account/card details. The app does not store merchant private keys or grant membership solely from a client SDK's result.
- AI Chat: your prompts, questions and conversation context; replies, proposed actions and execution results; necessary information from your own account's events, habits, Focus, Notes, To-dos, journals, tags, categories and summaries. Member image messages are re-encoded on the server to remove location/device metadata. Necessary prompts, images and context may be sent to DeepSeek and, when enabled, Alibaba Cloud content safety. We do not publish your private content to other users. Ordinary planning functions do not automatically send their content to AI providers.
- Attachments and voice: files, images, audio and necessary metadata such as name, size, MIME type, duration and format. When you request transcription, the selected audio or a temporary download link, task status, transcript and errors may be processed by Tencent Cloud speech recognition.
- App Lock: local lock settings and operating-system biometric verification results. We do not store raw fingerprints or facial templates on our servers.
- Support: the messages, contact details and attachments you choose to provide.
Read-only device calendars
Device calendar display is off by default on supported Android/iOS versions. Only after you enable it and grant access does the app read selected calendar names, sources, colors, event titles, start/end times, all-day status, locations and notes. These are displayed locally and are not uploaded or used for AI, advertising, analytics or logs. The app does not modify calendars, add event reminders or save event copies on disk. Disabling display, revoking access or signing out clears event memory. Device display preferences are not synchronized across accounts. Android requests read access only; iOS 17 and later require full calendar access to read events, although this feature remains read-only.
Device, network and diagnostic information
After privacy consent, processing may include app/OS versions, device model, platform, distribution channel, language, time zone, network state, IP address, request time, usage events and diagnostic details. Core requests use an app device identity. Platform or third-party capabilities may use IDFV, Android ID/OAID or Harmony OAID/ODID/AAID, subject to their actual integration, permissions and settings. Analytics SDKs may process approximate location, application-list visibility, carrier and Wi-Fi information when their functions actually use it.
Current client runtime logs are sent directly to our servers, subject to switches, levels, sampling and environment controls. They contain diagnostic fields, error summaries, app/build/platform information and, when authenticated, the account ID identified by the server. The request device identity is used for rate limiting and is not retained with these logs. The server filters tokens, passwords, phone numbers and emails again. We seek to avoid Note bodies, full AI conversations, audio or attachment contents in diagnostic logs. Historical clients used Alibaba Cloud SLS; clients predating Bugly removal used Bugly. Current clients no longer integrate those client SDKs. Native platform crash reports and local diagnostic records remain relevant.
iOS privacy and service regions
The ad-free app does not request App Tracking Transparency authorization or collect IDFA. Mainland China basic Umeng analytics starts only after valid service privacy consent; GLOBAL does not enable it. Switching service or withdrawing consent applies public analytics controls without promising that an already initialized analytics SDK can be completely unloaded.
Historical versions before 1.0.67 could request ATT; version 1.0.67 configured ads as non-personalized and disabled IDFA collection. These historical ad SDK behaviors do not apply to the ad-free binary.
Domestic analytics and Harmony capabilities
On supported domestic Android distributions, Umeng Mobile Analytics/Common initializes only after explicit privacy consent. Its actual processing may include model/manufacturer/OS, Android ID/OAID, IP, network/Wi-Fi/carrier information, app version/channel and usage events; installed application information may be processed for anomaly detection or fraud prevention when actually used by the SDK. This information can be transmitted to Umeng. Refusing consent prevents formal initialization and statistical reporting.
The ad-free release has no domestic ad SDK, ad scenes or personalization preferences. Older versions could include advertising partners that processed device/ad identifiers, network and ad interaction data, approximate location and application-list/storage permission information; those historical disclosures appear in the SDK list below. Harmony identifiers and cross-app association permissions remain subject to actual analytics, login or payment SDK use and system settings; unavailable identifiers may be empty or zero. These capabilities are not required for core planning functions.
Website download attribution
Download/marketing pages may use a first-party sg_visit_id cookie (default 30 days), visit/download times, page scene, campaign/source/material/placement/search/QR identifiers, explicitly supplied media click IDs, selected download target/channel and redirect result. Browser/device environment is derived from User-Agent. Marketing events store an IP digest produced with a server-secret HMAC rotated daily, rather than raw IP. This supports campaign measurement, redirect troubleshooting and fraud/stability checks; it is not used for personal profiling, personalized pricing or decisions significantly affecting your rights. Clear browser cookies to reset the identifier.
3. Purposes and permissions
We process the information above to authenticate and protect accounts, store and synchronize your content, deliver reminders, provide requested AI/transcription/support, fulfill purchases, diagnose failures and, after the relevant consent, measure usage. We do not use private device-calendar content for these online purposes.
Network access is needed for online functions. Notifications/exact alarms and system wake-up/background capabilities support your scheduled reminders or Focus audio. Microphone, camera, photos/files, biometrics and calendar access are requested for the corresponding functions. You can decline optional permissions or change them in system settings. Reminder-related wake-ups after reboot, app update or at scheduled times restore/trigger your unexpired reminders; they do not automatically open the app, launch other apps or serve unrelated advertising/engagement purposes. Disabling notifications, alarms or background access may reduce reminder reliability.
We do not use contacts, SMS contents, call histories, precise location or non-resettable hardware identifiers as core business account identifiers. Sensitive information such as identity/card numbers is not requested by core functions unless you choose to provide it. Third-party analytics capabilities and historical advertising SDKs are disclosed separately.
4. Storage, retention and security
Business data and accounts stay with their selected service. Switching regions or language does not copy them into the other service. Third-party features can involve processing in another country or region; consult the named processors below before sending information to these functions.
We retain information for the period necessary for the service and applicable legal obligations. Default retention includes:
- first-party client runtime logs: no more than 14 days;
- raw website download/marketing events: no more than 180 days; browser identifier cookie: 30 days;
- AI Chat images: 180 days after upload; selected but unsent images: 24 hours. Rejected images are deleted immediately, retaining moderation results and a non-reversible digest for safety audit. Expired images are replaced by an expiration notice in the conversation;
- account deletion: handled under applicable legal requirements; transaction or other legally required records may remain where required. Deletion does not cancel a store subscription.
We use HTTPS/TLS, access controls and security monitoring to protect information. No security measure makes processing entirely risk-free.
5. Sharing
We do not sell, rent or trade your personal information. We share necessary information with the providers used for the requested login, verification, email, storage, payment, AI, safety, transcription, diagnostics or consented analytics functions, and where legally required. Third-party providers process information under their own policies. The Third-Party Sharing List identifies providers and triggers, including Cloudflare R2 for GLOBAL, Alibaba Cloud OSS for CN, Apple/Google login, Apple purchases, DeepSeek, Alibaba Cloud safety/email and Tencent Cloud transcription.
The following domestic Android SDK disclosures also apply where those SDKs are used. Historical-only entries are explicitly marked.
| SDK / operator | Information and purpose | Trigger | Provider policy |
|---|---|---|---|
| Alipay App Payment / 支付宝(杭州)信息技术有限公司 | Order, amount, payment status and necessary device/network/app/risk information. | Your payment request on a supported domestic platform; not iOS digital membership. | https://opendocs.alipay.com/open/54/01g6qm#%E6%94%AF%E4%BB%98%E5%AE%9D%20App%20%E6%94%AF%E4%BB%98%E5%AE%A2%E6%88%B7%E7%AB%AF%20SDK%20%E9%9A%90%E7%A7%81%E6%94%BF%E7%AD%96 |
| Bugly Android (historical versions only) / 深圳市腾讯计算机系统有限公司 | Crash stacks, diagnostics and device/app/network information. Current clients no longer integrate this SDK. | Historical clients after privacy consent. | https://privacy.qq.com/document/preview/fc748b3d96224fdb825ea79e132c1a56 |
| QQ Connect Android / 深圳市腾讯计算机系统有限公司 | Authorized QQ identifiers/profile and necessary device/network/app information. | Your authorization on an available QQ login entry. | https://wiki.connect.qq.com/qq%e4%ba%92%e8%81%94sdk%e9%9a%90%e7%a7%81%e4%bf%9d%e6%8a%a4%e5%a3%b0%e6%98%8e |
| Alibaba Cloud SLS Android (historical versions only) / 阿里云计算有限公司 | App-triggered diagnostic logs, random local app identity, version/build, OS/model/language/time zone, errors/routes/state and necessary authenticated user ID. No configured MAC-address or installed-app-list collection; private Note/chat/audio/file content is avoided. Current clients send runtime logs directly to our servers. | Historical clients after consent, subject to log switches, sampling and environment. | https://terms.aliyun.com/legal-agreement/terms/suit_bu1_ali_cloud/suit_bu1_ali_cloud202112131013_69952.html |
| Umeng Mobile Analytics / Common / 友盟同欣(北京)科技有限公司 | Model/manufacturer/OS, Android ID/OAID, IP/Wi-Fi/network/carrier, version/channel and usage events; installed application information when actually processed for anomaly/fraud detection. The SDK reads/collects and transmits information to Umeng. | Only after explicit privacy consent; no formal initialization/statistical reporting without consent. Not enabled by GLOBAL. | https://www.umeng.com/page/policy |
| WeChat OpenSDK Android / 深圳市腾讯计算机系统有限公司 | Authorized account identifiers/profile, payment-process and necessary device/network/app information. | Your available login/payment request; not iOS digital membership payments. | https://support.weixin.qq.com/cgi-bin/mmsupportacctnodeweb-bin/pages/RYiYJkLOrQwu0nb8 |
| Douyin SDK Android / 北京微播视界科技有限公司 | Authorized account and necessary device/network/app information. | Your authorization on an available login entry. | https://developer.open-douyin.com/docs/resource/zh-CN/dop/operation-standard/service-protocol/douyinsdk_pingtaiyinsizhengce |
| Douyin OpenSDK Android / 北京微播视界科技有限公司 | Authorized account and necessary device/network/app information. | Your authorization on an available login entry. | https://developer.open-douyin.com/docs/resource/zh-CN/dop/operation-standard/service-protocol/douyinsdk_pingtaiyinsizhengce |
Historical advertising SDKs — version 1.0.67 and earlier
Starting with the ad-free release 1.0.68, Android, iOS and the subsequently updated HarmonyOS NEXT clients no longer include advertising SDKs, display app-open or list ads, or provide ad-personalization preferences. Basic analytics, first-party diagnostics and business functions retain their own consent and service-region controls. Advertising SDK disclosures for version 1.0.67 and earlier describe historical clients only; server ad switches are disabled, but older binaries may still contain SDKs, and disabling ads does not unload them.
| SDK / operator | Information and purpose | Trigger | Provider policy |
|---|---|---|---|
| Sigmob Android / 北京创智汇聚科技股份有限公司 | Device/app identifiers and environment, network and ad interactions; SDK-dependent approximate location, installed application visibility and storage permission state. | Enabled domestic ads after consent, subject to login, ad-free status, eligibility and scene. | https://doc.sigmob.com/sigmob/140/ |
| Kuaishou Ads Android / 北京快手科技有限公司 | Device/app identifiers and environment, network and ad interactions; SDK-dependent approximate location, installed application visibility and storage permission state. | Enabled domestic ads after consent and eligibility. | https://u.kuaishou.com/home/help/detail/1337/1425 |
| Pangle Ads / 北京巨量引擎网络技术有限公司 | Device/app identifiers and environment, network and ad interactions; SDK-dependent approximate location, installed application visibility and storage permission state. | Enabled domestic ads after consent and eligibility. | https://www.csjplatform.com/privacy |
| Tencent GDT Android / 深圳市腾讯计算机系统有限公司 | Device/app identifiers and environment, network and ad interactions; SDK-dependent approximate location, installed application visibility and storage permission state. | Enabled domestic ads after consent and eligibility. | https://e.qq.com/dev/help_detail.html?cid=2005&pid=5983 |
| Baidu oCPX Conversion Tracking / 北京百度网讯科技有限公司 | Device/app identifiers and environment, network and ad interactions; SDK-dependent approximate location, installed application visibility and storage permission state. Conversion events. | Enabled domestic ad/conversion measurement after consent and eligibility. | https://ocpx-devcenter.bj.bcebos.com/%E5%BA%94%E7%94%A8SDK%E8%B5%84%E6%BA%90/%E3%80%90%E7%99%BE%E5%BA%A6oCPX%E8%BD%AC%E5%8C%96%E8%BF%BD%E8%B8%AASDK%E3%80%91%E9%9A%90%E7%A7%81%E6%94%BF%E7%AD%96%2020250303.pdf?authorization=bce-auth-v1/e2ea496b5e7f4e20bd0e5d1ce5533588/2025-03-03T03%3A24%3A50Z/-1/host/f51f435fb61f7078188b3f185fcbffa4f08b54840da573f0050f6c90ce7dcb70 |
| Baidu Mobile Ads / 北京百度网讯科技有限公司 | Device/app identifiers and environment, network and ad interactions; SDK-dependent approximate location, installed application visibility and storage permission state. | Enabled domestic ads after consent and eligibility. | https://union.baidu.com/bqt/#/legal/policies |
6. Your choices and rights
You can access, correct or delete your information and request account deletion. In the app, open Me → Privacy & Security → Account & Security → Delete Account. Use Support & Feedback or contact@meita.app if you need help, including an access/export/deletion request. Specify CN or GLOBAL and the affected account; do not send passwords or verification codes. Requests concern the account in that service rather than both regions automatically.
You can disable optional features/permissions or withdraw privacy consent through the app's available privacy controls. Withdrawal does not undo processing already performed. Some online functions require the information described above. Manage/cancel Apple subscriptions in App Store account settings separately from signing out, uninstalling or deleting your app account.
7. Updates and contact
We may update this policy and provide notice through the app or other reasonable means. Updated policies take effect upon publication, with consent sought where required.
- Email: contact@meita.app
- Company: Hangzhou Meita Technology Co., Ltd.
- Registered address: 浙江省杭州市滨江区西兴街道54号17475室