Clock-In Assistant Privacy Policy

Updated: August 26, 2026
Effective: August 26, 2026

This policy applies to the Android app “Clock-In Assistant” (called “划水大王” in some domestic distribution channels; package name: com.longstudio.punchclockhelper).

1. Operator and scope

Clock-In Assistant is operated by Guangzhou Aiyoule Network Technology Co., Ltd. (“we,” “us,” or “our”). The app reminds users at configured times and attempts to open an app or a user-confirmed deep link selected by the user.

2. Information processed by the app

• Task configuration and execution: target app name and package name, or a deep link entered and confirmed by the user; task time, repeat mode, random delay, and enabled state. This information is stored and processed only on the device and is not uploaded to our servers.
• Execution history and diagnostics: scheduled time, completion time, attempt count, execution result, and local diagnostic logs, used only to show recent task status on the device.
• Permission and runtime state: display-over-other-apps, exact alarms, notifications, battery-optimization exclusion, and network state, used to assess feature availability and explain required settings.
• Membership purchase and restoration: depending on the distribution channel, Huawei signed order data or Google Play purchase token, product and base-plan IDs, order number, subscription state, purchase and expiry time, and a randomly generated app installation identifier. This data is sent over an encrypted connection to our entitlement service to verify purchases with the relevant platform, confirm purchases, prevent duplicate grants, restore or revoke entitlements, and investigate errors.
• Google Play subscription notifications: Google Play may send Real-time Developer Notifications (RTDN) through Google Cloud Pub/Sub, including a message ID, notification type, purchase token, and event time. Our server then queries the Google Play Developer API and relies on the platform’s current state, rather than granting entitlement from the notification body alone.

Our server retains necessary purchase state, order or token fingerprints, hashed installation identifiers, and audit fields. Because purchase tokens are needed to verify later renewals, refunds, revocations, and recovery, Google Play purchase tokens are encrypted using an application-server key; complete tokens are not written to logs. The app does not require registration and does not collect names, identity-card numbers, payment passwords, or complete card details. Payment is processed by the applicable app store, and we do not receive complete payment-instrument information.

3. Advertising SDKs and free-task rules

The unified free-use rules are: users receive 10 starter task runs, and the first five successful target-app launches do not request ads. During the 30-day trial, from the sixth launch onward, a successful banner or task-transition interstitial unlocks unlimited tasks for that day. If no ad is shown, one remaining starter credit is deducted only after the target app opens successfully. Payment and rewarded-video options are not shown during the trial. After the trial, remaining starter or reward credits are used first. When credits are exhausted, a user may become a member or choose a reward video; completing one adds 10 task-run credits.

Google Play: Google AdMob

The Google Play version uses Google Mobile Ads SDK 25.4.0 for Home and task-screen banners, task-transition interstitials, and reward videos chosen by the user. Version 19 removes Unity LevelPlay, Unity Ads, and their adapters. A successfully displayed task-transition interstitial is not repeated for one hour. In ordinary regions, ads are requested according to the task rules. Where required by law or Google policy, the app uses Google User Messaging Platform (UMP 4.0.0) and follows the user’s privacy choices. Paid members may still see ads, but ad initialization failure, loading failure, no fill, display failure, timeout, or an unavailable required privacy choice never blocks a paid task.

• Purposes: ad delivery, impression and interaction measurement, performance analysis, anti-fraud, security, and diagnostics.
• Information that may be processed: approximate location inferred from IP address; device or other identifiers; device, operating-system, and app information; ad request, impression, click, and completion events; app interaction; and diagnostics, subject to Google’s actual SDK behavior and policies.
• Privacy choices: users may disable personalized advertising, in which case non-personalized ads may still appear. Where UMP is required, the app provides a Google privacy-options entry so users can manage or withdraw applicable choices.

Google Privacy Policy · Google Advertising Technologies

Huawei, Xiaomi, and other domestic channels: Pangle

Domestic-channel builds initialize the Pangle advertising SDK only after explicit advertising and privacy consent. These builds may request splash or transition ads, banners, and reward videos chosen by the user. Declining consent prevents SDK initialization. Basic task configuration remains available, but ad-supported free access and reward capabilities may be unavailable.

Pangle Privacy Policy · Pangle Compliance Guide

4. In-app purchase services

Google Play Billing

The Google version uses Google Play Billing to query subscription products and base plans, start purchases, and restore purchases. Purchase tokens are sent to our server, which uses the Google Play Developer API to verify subscriptions, acknowledge purchases, and process renewal, cancellation, grace period, pause, refund, revocation, and expiry state. Google may process Google account, device, network, transaction, and risk-control information under its own rules. See the Google Privacy Policy.

Ordinary app startup reads only the local entitlement cache and does not contact the verification service every time. Requests may occur after a purchase, when restoring purchases, on the membership screen, or during a controlled fallback refresh scheduled approximately every 24–48 hours per installation. RTDN is used to update renewal, cancellation, refund, and revocation state promptly.

Huawei in-app purchases

The Huawei-channel version uses HMS Core In-App Purchases to query products, start a purchase, receive order results, and restore purchases. We process only the signed order data required to verify entitlement when a user purchases or restores. See the Huawei Consumer Business Privacy Statement.

5. Personalized advertising choices

Users can disable or re-enable personalized advertising in “Permissions and privacy.” The app passes that choice to the advertising SDK configured for the current channel. Non-personalized ads may still appear. Domestic-channel users may withdraw the app’s advertising consent. In the Google Play version, where UMP is required, users can manage or withdraw applicable choices through the Google privacy-options entry.

6. Firebase Analytics (Google Play only)

The Google Play version includes Firebase Analytics. Where legally permitted and Google UMP determines that no additional privacy choice is required, low-sensitivity analytics is enabled by default after the regional privacy state has been refreshed. In the EEA, the UK, Switzerland, and other applicable regions that require consent, Google UMP/CMP privacy messages and Consent Mode manage analytics_storage. Analytics remains disabled while the regional or privacy state is unresolved, if the CMP does not respond, or if initialization fails. None of those analytics states blocks task configuration, task execution, advertising, or membership.

Users can disable usage analytics at any time in “Permissions and privacy.” The app then stops future analytics collection and resets its local Firebase Analytics identifier. An explicit opt-out made in an older version remains disabled after upgrade unless the user actively enables analytics again. Where Google privacy choices are required, users can also manage or withdraw the applicable choice through the in-app Google privacy-options entry.

• Purposes: understand installation sources, the number of app opens per day, the number of task executions per day, task-feature usage, coarse success or failure categories, membership and purchase-flow entry points, and advertising load or display results.
• Events and parameters: first open, foreground entry, session and activity; Google Play purchases; task create, update, delete, enable/disable and launch results; daily task-count snapshots; membership-page visits; purchase-flow starts; purchase restoration; advertising delivery and gate results; and reward-credit grants. Custom parameters are limited to coarse categories such as schedule type, random-delay bucket, success or failure category, enabled state, and bounded task counts.
• Distribution labels: every custom event contains the fixed non-user labels distribution_channel=google_play and distribution_id=punchclockhelper_google_play, and the same values are set as Firebase user properties to distinguish the Google Play build. These values are identical for all users of this distribution and are not unique user, device, or installation identifiers.
• Not uploaded: target-app names or package names, task IDs, deep links, exact scheduled times, task notes, email addresses, order numbers, purchase tokens, or device serial numbers.
• Information Firebase may process: a Firebase-generated app-instance identifier, app version, device category, operating system, language, country or approximate region, sessions and app interactions, purchase item and localized price/currency fields needed for Analytics. The app does not create an additional personal or device-unique analytics identifier. Advertising ID, SSAID, and advertising-personalization signals are disabled for Analytics.

Firebase Privacy and Security · Google Privacy Policy

7. System permissions

• Internet and network state: determine whether a task’s network requirement is available and load ads or send low-sensitivity analytics according to the current region and privacy choices.
• Exact alarms: trigger tasks as close as possible to the time selected by the user.
• Display over other apps and background pop-up: improve reliability when opening the task flow in the background or from the lock screen.
• Battery-optimization exclusion: reduce task failures caused by background cleanup.
• Boot and system-time change broadcasts: reschedule tasks after restart, app update, or a system-time change.
• Notifications: provide a tappable continuation when Android blocks a background launch.

8. Retention and security

Task configuration, execution history, and diagnostic logs remain on the user’s device. Users can delete tasks, and uninstalling the app removes local app data. Purchase-verification ledgers, encrypted purchase tokens, and RTDN audit records are retained only for the minimum period necessary to perform transactions and renewal verification, provide support, resolve disputes, and satisfy legal obligations, after which they are deleted or anonymized. Installation identifiers are stored only as hashes on the server. Firebase Analytics data is handled under the retention period configured for the project and Google’s service rules; after analytics is disabled or consent is withdrawn, the app stops sending new events and resets the local analytics identifier. We use access controls, transport encryption, token encryption, log redaction, and data-minimization measures.

9. User rights and deletion requests

Users can view, change, pause, or delete tasks; disable related system permissions; opt out of personalized advertising; withdraw advertising consent; disable usage analytics; manage applicable Google privacy choices; or uninstall the app. To request deletion of server data, email hklongcaresu@gmail.com with the subject “Clock-In Assistant data deletion request.” If a purchase was made, include the Google Play order number and approximate purchase time, but never send a payment password or card information. After verifying the relationship between the requester and the order, we will delete or anonymize installation-identifier hashes, purchase tokens, entitlement records, and support records that can be associated with that installation or order. Transaction and audit records required by law or an unresolved refund or dispute will be isolated and retained only for the necessary period.

10. Children

The app is not directed to children. A minor should use it only with the guidance and consent of a guardian. A guardian who believes a minor’s information was processed improperly may contact us for review and action.

11. Policy updates

We may update this policy when features, third-party SDKs, or legal requirements materially change. We will provide an in-app notice or another appropriate notice, and obtain consent again where required.

12. Contact

Operator: Guangzhou Aiyoule Network Technology Co., Ltd.
Email: hklongcaresu@gmail.com