tiday

Tiday Privacy Policy

Developer
Beijing Chenghan Bowen Education Technology Co., Ltd.
Platform
android
Region
Global
Language
en-US
Privacy Policy Version
2.1.0
Effective Date
2026-10-05
Status
Active

Tiday Privacy Policy (Android Global)

Prepared on: October 1, 2026

Effective date: October 5, 2026

Version: 2.1.0

Platform: Android

Distribution region: overseas/global distribution build

Status: Active

Developer: Beijing Chenghan Bowen Education Technology Co., Ltd.

Contact: contact@chenghanbowen.com

This English version is provided for convenience. If it differs from the Chinese version, the Chinese version will prevail to the extent permitted by applicable law.

1. Scope

This Policy applies to Tiday for Android distributed through overseas/global channels and related schedule management, calendar, memos, local reminders, feedback, legal pages, analytics, advertising, diagnostics, first-party promotion, and support services. Mainland China builds use a separate policy.

2. Basic Service Mode

You may choose Basic Service first. Basic Service does not proactively request ads, enable personalized ad recommendations, or report to the first-party promotion center; analytics/diagnostic collection remains off before the required privacy consent, while local schedules, calendar, memos, and basic browsing remain available. Some SDK base instances, consent management, system diagnostics, or vendor-automatic behavior may exist or run depending on version, platform, and network state; this policy does not guarantee zero SDK activity in Basic Service. After applicable consent and the relevant feature, configuration, and release configuration are ready, those analytics and advertising features may be enabled according to configuration.

3. Information We Process

  • Schedule titles, notes, reminder times, repeat rules, ringtone or reminder settings, calendar preferences, memo content, and local restoration state. These items are mainly processed locally unless you actively submit feedback, share, or use an online service.
  • Feedback content, contact details, screenshots or image attachments, app version, device model, system version, channel, installation instance ID, and legal-page parameters.
  • After applicable consent and feature enablement, Firebase installation or instance identifiers, Google Advertising ID where allowed by system and Google policies, device/app information, network status, IP address, page/tap/crash events, ad impression/click/close events, consent state, and first-party promotion events.

Automatic SDK processing is accounted for separately from the app's business-data allowlist. After applicable privacy consent and feature enablement, SDKs may automatically process device and app information, IP address, network state, advertising or installation identifiers, consent state, ad request/fill/impression/click/close/failure results, and security, anti-fraud, or diagnostic signals. This SDK field list does not mean that business content is uploaded to ad or analytics providers; schedules, calendar, memos, reminders, and feedback remain processed according to the relevant feature and your active action.

4. Region-Specific SDKs and Services

  • Firebase Analytics for app-usage measurement after applicable privacy consent and analytics enablement.
  • Firebase Crashlytics for crash and stability diagnostics after applicable privacy consent and stability-diagnostic enablement.
  • Google Mobile Ads (GMA/AdMob) for advertising, measurement, frequency control, and invalid-traffic prevention under the applicable consent state and ad configuration.
  • Google User Messaging Platform (UMP) for advertising and privacy-consent choices and privacy-options management in applicable regions.
  • TopOn mediation SDK for Global mediation, demand-source configuration, bidding or waterfall management, and ad measurement; it works only after applicable consent, ad configuration, and release configuration are ready.
  • Pangle as a demand source configured through TopOn, only where the region, format, account authorization, and consent state permit it.
  • The Android Pangle advertising dependency also includes an optional TikTok App Events technical module. This app does not actively enable the TikTok App Events service. Packaging the module does not mean event reporting is enabled, nor does it establish that every internal component processes no data. Pangle advertising purposes and regional policies are linked below.
  • TopOn ADX is an advertising-resource service configured through TopOn mediation for ad delivery, measurement and fraud prevention, subject to applicable privacy choices and advertising configuration. TopOn may work with affiliates and advertising or technical-service partners described in its policy; details and privacy-request channels are provided below.
  • The first-party promotion center, system file picker, and Android scheduling capabilities for first-party promotion, attachments, and reminders.

These providers process information under their own terms and privacy policies. Ad requests, analytics/diagnostic collection, and demand-source features are controlled by applicable primary privacy consent, advertising consent, UMP, app configuration, and release configuration. Some SDK base instances, consent management, system diagnostics, or vendor-automatic behavior may exist or run earlier depending on version, platform, and network state; this policy does not guarantee zero SDK activity before consent. The Global build does not load domestic-market commerce or advertising SDKs. The actual data scope of advertising and analytics SDKs varies by region, consent, app configuration, account status, and version; this policy does not promise a fixed third-party retention period, cross-border route, or automatic field set.

5. Permissions and Opt-Out

Tiday Android Global may use network access, network state, notifications, exact alarm, boot-completed broadcast, legacy storage/media selection, the system file picker, WebView, Google Advertising ID, and advertising-consent 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. You can limit personalized ad recommendations in the app or Google privacy/ad settings and manage notification, alarm, and reminder permissions in system settings.

Provider Privacy Policies

Current official policy links are Firebase privacy information, Google Ads privacy policy, Android UMP privacy guidance, the TopOn current privacy policy and TopOn terms, and the Pangle regional entity/policy map. These policies describe possible device/app information, IP address, network state, advertising or installation identifiers, ad requests and ad interactions, and security, anti-fraud, or diagnostic signals; they do not prove that every listed field is collected by this app. Processing and retention depend on the services you use, applicable privacy choices, current provider policies, contracts and legal obligations; there is no universal deletion deadline for every SDK or data category.

TopOn service entities and processing

The TopOn advertising-services policy dated 2026-07-10 assigns U.S. citizens and entities organized under U.S. law to Ascent Pro Technology Limited, and other cases to TOPON PTE. LTD., subject also to applicable service agreements. This identifies TopOn itself, not every indirect component's recipient.

TopOn describes IP, device/ad identifiers, device/network/app information, ad interactions, diagnostics and consent information for mediation, measurement and anti-fraud. Actual processing depends on version, configuration and applicable choices; not every listed field is collected by this app. TopOn names Singapore and the United States as primary processing locations, with possible other partner locations. Its general retention is up to two years from collection, subject to necessity and legal/contractual obligations. This is not a universal deletion deadline for app feedback or other SDKs. TopOn privacy requests: privacy@toponad.net.

Privacy Choices and Withdrawal

Use the app's Privacy Choices/Privacy Management entry in Settings to review or make a choice. If you previously gave explicit consent, confirm “Withdraw Privacy Consent” before switching to Basic Services; canceling that confirmation leaves the existing choice unchanged. Choosing again requires your explicit consent before the optional features can resume. Withdrawal cancels current ad preparation and pending presentation; it does not replay prior ad requests or impressions. It stops new advertising requests and disables optional analytics and diagnostics controlled by the app; basic features remain available. SDK base instances, consent-management components, system diagnostics, or vendor-automatic behavior may still exist or run; this does not mean all SDKs automatically stop and is not a guarantee of zero SDK activity before consent. Withdrawal does not affect processing already lawfully completed and does not automatically delete submitted feedback or other previously processed information.

The app's main privacy choice is separate from advertising-privacy choices. UMP appears only where applicable and when the required conditions are met; it is not a universal global prompt and does not replace the main privacy choice. On iOS, ATT applies only to cross-app tracking/IDFA where applicable and does not replace the app-level privacy, analytics, or diagnostic choice.

6. Sharing, Retention, Security, and Your Rights

We do not sell your personal information. We share information only as needed with the providers described above, hosting and security providers, professional advisers, authorities where legally required, or a successor in a lawful business transfer. Information may be processed outside your country or region; TopOn’s primary processing locations are described above, Pangle operates under its regional policies, and Google uses global infrastructure. Provider policies describe their processing locations, sharing and safeguards.

We retain information only for as long as reasonably necessary for the purposes described in this Policy, legal obligations, dispute resolution, security, and fraud prevention. You can manage permissions and personalized-ad preferences in Android or Google settings, or contact contact@chenghanbowen.com to request access, correction, deletion, or withdrawal of consent.

7. Changes and Contact

We may update this Policy as the app, providers, law, or platform requirements change and will provide appropriate notice where required.

For privacy questions or requests, contact contact@chenghanbowen.com.