Privacy Policy

Effective Date: April 9, 2025

1. Introduction

1.1 Developer Information

This Privacy Policy (hereinafter referred to as "this Policy") applies to mobile applications developed and operated by CatchingNow (hereinafter referred to as "we" or "us").

1.2 Scope of Application

This Policy uniformly applies to the following applications (hereinafter collectively referred to as "the Applications"):

• Inputting Plus: https://play.google.com/store/apps/details?id=com.catchingnow.undo
• Clip Stack: https://play.google.com/store/apps/details?id=com.catchingnow.tinyclipboardmanager
• IceBox: https://play.google.com/store/apps/details?id=com.catchingnow.icebox
• FilterBox: https://play.google.com/store/apps/details?id=com.catchingnow.np
• ClipCloud: https://play.google.com/store/apps/details?id=com.catchingnow.share
• AI Bubble: https://play.google.com/store/apps/details?id=the.bravenewworld.input

This Policy describes how we access, collect, use, and share your personal information and sensitive user data.

1.3 Privacy Commitment and Compliance Statement

We understand the importance of personal information to you and are committed to protecting your privacy. We promise to comply with applicable data protection laws and regulations, particularly the Google Play Developer Program Policies, including its User Data policy.[1, 2] Explicitly stating compliance with Google Play policies is not only to meet core requirements [2, 3] but also aims to set a compliant tone, indicating that we will provide detailed disclosures according to these high standards.

1.4 Effective Date

This Policy is effective from the date indicated above.

1.5 Policy Labeling

This document is clearly identified as a "Privacy Policy," complying with Google Play's requirements.[2, 3]

2. Information We Collect

2.1 Data Collection Overview

This section details the types of information we may collect when you use the Applications, the methods of collection (e.g., automatically collected or provided by you), and the purposes of collection.

To enhance transparency and provide users with a clear understanding of the scope of data processing, we first emphasize that, except for specific features (such as the ClipCloud synchronization service, detailed in Section 2.4), most user content and settings generated while using these applications (e.g., rules you create, clipboard history, application settings) are primarily stored on your local device. We generally do not access this local data, nor do we transfer it to our servers. This point is crucial for managing user expectations and building trust, as it clarifies that interaction between the developer's servers and user data is limited.

However, to provide and improve services, certain application features rely on third-party services, and in specific cases (like ClipCloud), limited server-side processing is required. The following details the collection of various types of information.

2.2 Information Collected Automatically Through Third-Party Services

To ensure the basic functionality of the applications, conduct data analysis to optimize user experience, and improve application stability, we integrate specific third-party Software Development Kits (SDKs). According to Google Play policy, developers are responsible for the data processing practices of the SDKs included in their apps.[1] Therefore, we explicitly disclose the types of data these third-party services may collect and their purposes. These services collect and process data according to their own privacy policies.

2.2.1 Firebase (Google LLC)

The Applications use several services provided by Google's Firebase platform, which may include Firebase Analytics, Firebase Crashlytics, Firebase Authentication, Firebase Cloud Messaging, Firebase Remote Config, etc..[4] Depending on the specific Firebase services used, Google may automatically collect the following types of data:

• Identifiers:
  • Firebase installation ID (FID): Used to identify unique installation instances of the app, associating analytics data, crash reports, remote configuration, and push messages.[4]
  • Crashlytics Installation UUID: Used to associate crash data with specific app installation instances.[4]
  • App instance ID (via Google Analytics for Firebase): Used to measure user interactions.[5]
• Device Information: Device model, operating system version, hardware information (e.g., RAM, disk space), user agent string (browser or app environment information), etc..[4]
• Usage Data: App interaction details (e.g., feature usage frequency), session information, performance data (e.g., app startup time, duration of network requests, URL path (excluding parameters), response code, request/response size, latency), etc..[4]
• Crash Information: Detailed crash stack traces, device state information at the time of the crash (e.g., memory usage), Breakpad minidump data for NDK crashes (temporarily stored for processing).[4] This data is crucial for diagnosing and fixing app stability issues.
• IP Addresses: Several Firebase services (like Authentication, Cloud Functions, Hosting, Performance Monitoring, Realtime Database) collect IP addresses, primarily for:
  • Security Protection: Detecting and preventing abuse.[4]
  • Service Provision: E.g., determining approximate geographic location based on IP for regional services or optimizing network connections.[4]
  • Diagnostic Analysis: E.g., Hosting uses it to analyze usage, Realtime Database to analyze usage trends.[4]
  • Performance Monitoring: Mapping performance events to countries/regions.[4]
  • Firebase retains IP addresses based on service needs, e.g., Authentication for a few weeks, Hosting for a few months, Performance Monitoring for 30 days.[4]

Purposes of Collection:

• Application Functionality: Implementing core features like push notifications (Cloud Messaging), user authentication (Authentication), dynamic configuration delivery (Remote Config).
• Analysis & Improvement: Understanding how users interact with the app through Firebase Analytics, identifying usage patterns, providing data support for product iteration.[4]
• Performance Monitoring: Monitoring app performance metrics, identifying and resolving performance bottlenecks.[4]
• Stability Assurance: Collecting crash reports via Crashlytics to quickly locate and fix issues causing app crashes, improving app stability.[4]
• Security: Enhancing service security using collected information (like IP addresses, user agents) to prevent fraud and abuse.[4]

Firebase Privacy Policy Links:

• For detailed information on how Firebase handles data, please refer to Firebase Privacy & Security.[4]
• Firebase services are also subject to the Google Privacy Policy.[6, 7]

Developers are responsible for understanding and enabling only necessary Firebase modules. Even though Google acts as a data processor, its extensive data collection means developers need to ensure their apps comply with privacy best practices and accurately reflect the services used in their privacy policy.[4]

2.2.2 Google Analytics (via Firebase)

The Applications use Google Analytics (specifically the Google Analytics for Firebase SDK) to collect and analyze data on how users use the Applications, helping us improve our products.

Main Data Collected:

• App-instance identifier: A randomly generated number that uniquely identifies a specific installation instance of the app. This identifier may be reset under certain circumstances (e.g., app uninstall/reinstall).[5]
• Aggregated usage statistics: Such as the number of app launches, session duration, number of views on different pages within the app, clicks on specific features, and other events configured by the developer.

Purposes of Collection: Analyzing user behavior, understanding user preferences, evaluating feature effectiveness, optimizing app design and user experience.[5, 8]

Google Analytics Privacy Policy Links:

• To understand how Google uses data collected through its services, please refer to How Google uses information from sites or apps that use our services.[5]
• Google Analytics data processing is also subject to the Google Privacy Policy.[6, 7]

Although Google Analytics for Firebase primarily relies on the app instance ID for data collection [5], Google's overall Analytics terms of service also emphasize the use of cookies and users' opt-out rights.[5, 9] To ensure comprehensive disclosure, we provide links to Google's general policies to cover all potential data processing practices.

2.3 Information You Provide or Generate (Locally Stored)

We reiterate that the following application-related data is primarily stored on your local device, and we generally do not access or transfer it to our servers. Explicitly listing these locally processed data types is intended to meet Google Play's requirement for comprehensive disclosure of data access and collection [2, 3]; even if user data does not leave the device, users should be informed about what information the app is processing.

• Inputting Plus: Input method shortcuts you create, custom settings, local usage statistics related to input efficiency.
• Clip Stack: History entries copied to your clipboard (may include text, images, etc., depending on device and app features), user settings, pinned clipboard items.
• IceBox: The list of applications you choose to add to IceBox for management (freezing), user settings, related configuration data.
• FilterBox: Notification filtering rules you define, locally stored notification history (if the app offers this feature), user settings.
• AI Bubble: Text you input for interaction with the AI model (Please note: If AI Bubble uses an external third-party AI service for processing, user input may be sent to that third-party service, and its processing will be governed by that third-party's privacy policy. Here, it is assumed processing is primarily local or via standard interfaces; the developer needs to confirm and supplement disclosure accordingly), user settings, interaction history with the AI (usually stored locally).

2.4 Information Collected/Processed for Specific Features (ClipCloud)

ClipCloud's core functionality is synchronizing clipboard content across devices, which requires data transit and account management via our servers. Therefore, ClipCloud involves the following specific information collection and processing:

2.4.1 Google Account Information (via Google Sign-In/OAuth)

• Collection Method: ClipCloud uses Google Sign-In (OAuth 2.0) service for user authentication and account creation/login.
• Data Collected: When you choose to log in to ClipCloud using your Google account, with your explicit authorization, we access the following information from your Google account:
  • Email address
  • Basic profile information (e.g., your Google account nickname or name) [7, 10, 11]
• Storage and Use: Your email address and nickname are stored on our servers. The sole purpose of storing this information is to identify your ClipCloud account, manage your login status, and link your multiple devices to enable the clipboard synchronization feature.
• Google Privacy Policy & Compliance Statement:
  • Google has strict policy requirements for data accessed via its OAuth services. You can review the Google Privacy Policy [7, 10] and the Google API Services User Data Policy [10] for details.
  • We hereby declare: CatchingNow's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Including this specific statement is a key compliance point for the Google OAuth verification process, ensuring our handling of user data meets Google's stringent standards.[10, 12]

2.4.2 Clipboard Data (ClipCloud Synchronization)

• Processing Method: When you use ClipCloud to synchronize clipboard content, this content needs to pass through our servers for distribution.
• Security Measures: We highly value the privacy of your clipboard content.
  • End-to-End Encryption: Your clipboard data is end-to-end encrypted before it leaves your device. This means only devices holding your key can decrypt and view the original content.
  • Server Cannot Decrypt: We cannot decrypt or access your encrypted clipboard content on our servers.
• Storage and Retention:
  • Temporary Transit: Encrypted data is only temporarily stored on our servers for the sole purpose of distributing it as quickly as possible to your other associated devices logged into ClipCloud.
  • No History Storage: Once the data is successfully distributed to your target devices, or after a brief distribution attempt period, this encrypted data is immediately deleted from the server queue. We do not save your clipboard synchronization history on the server side.

Clearly explaining end-to-end encryption and the transient, temporary nature of server storage is crucial for building user trust. It demonstrates that we employ robust technical measures to protect user privacy and limit server interaction to the minimum necessary for the synchronization feature.

2.5 Payment Information (Non-Google Play Versions Only)

We must clearly differentiate the payment processing between application versions obtained through the Google Play Store and those obtained through other channels to ensure compliance with Google Play's payment policy.[1]

• Google Play Version:
  • If you download and install the Application from the Google Play Store, any in-app purchases or subscription services will be processed through Google Play's in-app billing system.
  • In this case, we do not collect, process, or store your payment card information (such as credit card numbers), bank account information, or other sensitive financial details. Your payment is handled directly by Google and is subject to the Google Play Terms of Service (or relevant Google Payments policies).
• Non-Google Play Version:
  • If you obtained the Application through channels other than the Google Play Store (e.g., downloaded directly from the developer's website), we may offer third-party payment options besides Google Play, such as Alipay or WeChat Pay.
  • When you choose to use these third-party payment services, you will provide your payment information directly to the respective payment provider. Your information will be governed by their respective privacy policies.
  • We do not collect, store, or process your full payment card number, bank account details, or other core financial information. We may only receive necessary transaction confirmation information from the payment provider, such as whether the payment was successful, the transaction ID, order amount, and time, to complete your purchase and provide necessary customer support.
• Third-Party Payment Privacy Policy Links:
  • Alipay: https://intl.alipay.com/docs/ac/platform/privacy
  • WeChat Pay: https://www.wechat.com/en/privacy_policy.html

Data Collection Summary Table

To provide a clearer, more intuitive overview of the information we collect and process, the following table summarizes the main data types, involved applications, collection purposes, storage locations, and relevant third-party services:

Note: The table above provides an overview. For detailed processing methods for each data type, please refer to the corresponding sections of this Policy.

3. How We Use Your Information

3.1 Overall Purposes of Using Information

We collect and use your information primarily for the following purposes:

• Providing and Maintaining Services: Ensuring the Applications operate normally and provide the core functionalities you expect, such as input assistance in Inputting Plus, clipboard management in Clip Stack, app freezing in IceBox, notification filtering in FilterBox, AI interaction in AI Bubble, and cross-device synchronization in ClipCloud.
• Improving Services: Understanding user habits and preferences by analyzing anonymized or aggregated usage data provided by Firebase and Google Analytics, identifying popular features and potential issues, thereby optimizing existing features, developing new ones, and enhancing the overall user experience.[4, 5, 7]
• Personalization (Limited): Remembering user settings and preferences (primarily stored locally). Firebase Remote Config may be used to deliver feature flags or conduct A/B testing to optimize the user interface or experience.[4]
• Ensuring Security and Stability:
  • Using information collected by Firebase, such as IP addresses and device identifiers, to detect and prevent fraud, abuse, and other security risks.[4]
  • Monitoring application performance via Firebase Performance Monitoring to identify and resolve potential performance bottlenecks.[4]
  • Collecting and analyzing crash reports via Firebase Crashlytics to diagnose and fix errors causing application instability.[4]
• Authentication: Using Google Sign-In to verify user identity for services requiring login (like ClipCloud), ensuring account security.[7, 10]
• Communication: Using information you provide (like contact details) to communicate with you and resolve issues when you proactively contact us for support or provide feedback.
• Complying with Laws and Regulations: Fulfilling obligations stipulated by applicable laws and regulations.

3.2 Association of Purposes and Data Types

We use specific types of data for specific purposes. For example:

• We use Firebase installation IDs and crash data to diagnose and fix app stability issues.
• We use your Google email address stored on our servers solely to manage your ClipCloud account and associate devices.
• We use aggregated usage data collected via Google Analytics to analyze which features are most popular, prioritizing improvements accordingly.

This principle of purpose limitation ensures we only use your data when necessary to provide value to users or ensure service operation, complying with Google Play's requirement for clear disclosure of data collection purposes [2, 3, 15, 16], and Google OAuth's rule that data use must be limited to disclosed purposes.[10, 17]

3.3 Prohibition of Other Uses

We solemnly promise not to use your personal information for purposes other than those explicitly stated in this Policy. Specifically, we will never sell your personal information to any third party.[10, 17] Clearly stating these limitations, especially the prohibition of data sales, helps build user trust and directly addresses requirements in regulations like the Google API Services User Data Policy [10, 17], ensuring transparency and compliance in data usage.

4. How We Share Your Information

4.1 Information Sharing Overview

We highly value the security of your personal information and will not share it with any third party, except in the following limited, necessary circumstances. We reiterate that we do not sell your personal information. Clearly categorizing information sharing (service providers, legal requirements, business transfers, user consent) helps users understand the limited conditions under which their data might be shared, enhancing the policy's structure and readability.

4.2 Third-Party Service Providers

To provide complete functionality and analysis services, we may need to share information with the following types of third-party service providers:

• Google (Firebase, Google Analytics, Google Sign-In):
  • Shared Content: As described in Section 2.2, data collected via Firebase and Google Analytics (e.g., device information, usage statistics, crash reports, identifiers, IP addresses) is shared with Google LLC and its affiliates for Google to provide these platform services. When you use Google Sign-In to log into ClipCloud, your authentication information is processed by Google.
  • Purpose: To enable analytics, crash reporting, push notifications, authentication, etc.
  • Google's Role: Google typically acts as a data processor or service provider when handling this data.[4, 5] For how Google processes this data, please refer to their privacy policies (links in Section 2.2).
• Payment Processors (Alipay/WeChat Pay - Non-Google Play Versions Only):
  • Shared Content: If you choose to use Alipay or WeChat Pay in non-Google Play versions of the app, your transaction information (non-sensitive payment info) will be shared directly with the respective payment service provider.
  • Purpose: To process your payment request.
  • Privacy Policy: Their data processing is governed by their respective privacy policies (links in Section 2.5).
• (Potential) AI Service Providers (AI Bubble):
  • Shared Content: If the AI Bubble app uses a third-party cloud AI service to process your input, your input content may be shared with that AI service provider.
  • Purpose: To enable AI functionalities (e.g., text generation, Q&A).
  • Disclosure: If such sharing exists, we will explicitly state the provider's name here and note that their data processing follows the provider's terms and privacy policy. (Developer needs to confirm and supplement this part based on AI Bubble's actual implementation.)

According to Google Play policy, we must disclose who we share user data with.[2, 3] Firebase/GA policies also require disclosure of data sharing with Google [15], and Google OAuth policy has strict limitations on data transfer.[10, 17]

4.3 Legal Requirements

We may need to share your information by law in the following circumstances:

• To comply with applicable laws, regulations, legal processes (such as subpoenas, court orders), or enforceable governmental requests.[7, 18, 19]
• To enforce our terms of service, investigate potential violations.
• To detect, prevent, or otherwise address fraud, security, or technical issues.
• To protect against harm to the rights, property, or safety of us, our users, or the public as required or permitted by law.[7, 18]

4.4 Business Transfers

If we are involved in a merger, acquisition, or asset sale, your personal information may be transferred as part of that transaction. In such cases, we will provide notice to you and ensure the receiving party continues to comply with this Privacy Policy or a policy providing equivalent protection.[7, 18, 19]

4.5 With Your Explicit Consent

Except for the situations described above, we will obtain your explicit consent before sharing your personal information with third parties.[6, 7]

5. Data Security

5.1 Security Measures We Take

We implement reasonable technical and administrative measures to protect the security of your personal information against unauthorized access, use, disclosure, modification, or damage.

• Encryption Technology:
  • ClipCloud Data: For clipboard data synchronized via ClipCloud, we use end-to-end encryption technology to ensure confidentiality during transmission and temporary storage on servers (which we cannot decrypt).
  • Transmission Encryption: Communication with third-party services like Firebase, Google, and our own servers (for ClipCloud) uses industry-standard HTTPS protocol for encrypted transmission, protecting data security during network transfer.[4, 20]
  • Storage Encryption: For sensitive information stored on servers (like ClipCloud user emails and nicknames), we employ appropriate encryption measures for protection.[17]
• Local Storage Security: The security of data stored on your local device (e.g., Clip Stack history, IceBox app list) largely depends on your device's own security settings and your usage habits.
• Third-Party Security Practices: We rely on the security practices of third-party service providers like Google (Firebase, Google Analytics, Google Sign-In) [4, 21] and payment processors (Alipay/WeChat Pay) [22, 23, 24] to protect the data they process. Acknowledging reliance on third-party security is an important part of transparency, as the overall security posture combines the developer's own practices with the robust systems of major providers like Google.
• Access Control (Developer Side): For ClipCloud account information (email, nickname) stored on our servers, we implement strict access control mechanisms, allowing access only to necessary personnel performing their duties.[4]
• Compliance Requirements: Google Play requires developers to outline their secure data handling procedures in the privacy policy.[2, 3] Google OAuth policy also requires description of data protection mechanisms.[17]

5.2 Your Responsibility

We recommend that you properly safeguard your device and account credentials (especially the Google account password used for ClipCloud login) and take necessary security measures (like setting screen locks, updating the system promptly) to protect data stored on your device.

5.3 Disclaimer

Although we strive to use commercially acceptable means to protect your personal information, no method of transmission over the Internet, or method of electronic storage, is 100% secure. Therefore, we cannot guarantee its absolute security.[18, 25]

6. Data Retention and Deletion

6.1 Data Retention Policy Overview

We retain your personal information only for the period necessary to fulfill the purposes described in this Policy, provide services, and comply with applicable laws and regulations.[14, 17, 18, 23, 26, 27] Google Play requires developers to clearly state their data retention and deletion policies.[2, 3]

6.2 Retention Periods for Specific Data

• Locally Stored Data: Data stored locally on your device (e.g., Clip Stack clipboard history, FilterBox rules, IceBox app list, settings for various apps) will remain on your device until you clear the app data/cache through Android system settings, uninstall the application, or manually delete the relevant content within the app (if the app provides such functionality).
• Firebase/Google Analytics Data: The retention period for data collected by Firebase and Google Analytics is determined by Google's policies. For example:
  • Firebase Crashlytics crash data and associated identifiers are typically retained for 90 days.[4]
  • Firebase Performance Monitoring IP-related events are kept for 30 days, other performance data for 60 days.[4]
  • IP addresses logged by Firebase Authentication are kept for a few weeks, while other authentication information (like email) is retained until we receive and process your deletion request.[4]
  • Google Analytics data retention periods can be configured in the Firebase console but have default settings.[21]
  • Please refer to relevant Google and Firebase documentation for specific retention policies.
• ClipCloud Account Data (Email/Nickname): Your ClipCloud account association information (email address and nickname) stored on our servers will be retained until you stop using the ClipCloud service and request the deletion of your account (see Section 6.3).
• ClipCloud Sync Data (Encrypted Content): As mentioned earlier, end-to-end encrypted clipboard content synchronized via ClipCloud is only temporarily transited through servers for distribution purposes and is not retained long-term or stored as history.
• Payment Transaction Data (Non-GP Versions): We do not store your sensitive payment information. Transaction confirmation information we might receive (e.g., transaction status, ID, amount) will be retained for the necessary period required by accounting and legal regulations for bookkeeping and customer support.

6.3 User Data Deletion Requests

You have the right to request the deletion of your personal information.

• Local Data: You can delete data stored on your local device by clearing the specific app's data and cache via the Android system's "App Info" page, or by uninstalling the application.
• ClipCloud Account and Associated Data:
  • Deletion Pathways: If you wish to delete your ClipCloud account and the associated information stored on our servers (email address, nickname), you can submit a request through the following two methods:
    1. In-App: Initiate a deletion request through the account settings or relevant options within the ClipCloud application.
    2. Out-of-App: Send an email to the contact address provided in Section 10, clearly stating your account deletion request.
  • Processing: Upon receiving your valid deletion request, we will process it within a reasonable timeframe. Your account information will first be removed from active databases and may be completely purged from backup systems within a period consistent with industry practice (e.g., similar to Firebase's 180 days [4]).
  • Google Play Requirement: Google Play policy mandates providing both in-app and out-of-app account deletion pathways.[2] This ensures users have a channel to request deletion of their account data even if they have uninstalled the app, reflecting respect for user data control rights, while also imposing corresponding implementation and process management responsibilities on developers.
• Data Held by Third-Party Services: For data collected and stored by third-party services like Google (Firebase, Google Analytics, Google Sign-In), Alipay, WeChat Pay, etc., you need to interact directly with these third-party services to manage or delete your data. You can usually do this through their account settings or by contacting their customer service. For example, you can manage data associated with your Google account via Google My Activity [6, 21] or the Google Account [6] console.

7. Your Privacy Rights

7.1 Overview of Your Rights

Depending on the applicable data protection laws in your location, you may have the following rights regarding your personal information:

• Right of Access: The right to access the personal information we hold about you (primarily applicable to ClipCloud account information).
• Right to Rectification: The right to request correction if you believe the information we hold about you is inaccurate or incomplete (e.g., if ClipCloud allows nickname modification).
• Right to Erasure (Deletion): The right to request the deletion of your personal information (specific methods detailed in Section 6.3).
• Right to Object/Restrict Processing: The right to object to or request restriction of our processing of your personal information under certain circumstances (applicability may be limited given that much of our data processing is necessary for core functionalities).
• Right to Data Portability: The right to request a copy of your personal information in a structured, commonly used, and machine-readable format and to transmit it to another controller under certain conditions (primarily applicable to ClipCloud account information).
• Right to Withdraw Consent: If our processing of your information is based on your consent (e.g., you consented to use Google Sign-In for ClipCloud, or consented to non-essential analytics tracking), you have the right to withdraw consent at any time. Withdrawal does not affect the lawfulness of processing based on consent before its withdrawal.

These rights are standard provisions in major privacy regulations like GDPR and CCPA [8, 26, 28], and are also reflected in the policies of Google [6, 21] and Alipay/WeChat Pay.[18, 27]

7.2 How to Exercise Your Rights

If you wish to exercise any of the rights listed above, please contact us using the contact information provided in Section 10. We may need to verify your identity before processing your request.

Please note that for data held and processed by third-party services (such as Google, Alipay, WeChat Pay), you need to contact these third parties directly to exercise your rights. You can consult their privacy policies or visit their user control panels (like Google Account [6], Google My Activity [21]) for more information.

7.3 Your Choices and Controls (Opt-Out Mechanisms)

In addition to the rights above, you can manage your information and preferences through the following means:

• Google Analytics Choice: Google provides information on how users can manage their choices regarding data collected by Google Analytics, often through browser settings or specific opt-out tools provided by Google.[5, 9]
• App Permissions: You can view and change the permissions granted to the Applications (e.g., storage, location) at any time through the Android system's permission manager.
• Google Account Linking: You can manage third-party apps (including ClipCloud) that have been granted access to your Google account data in your Google account settings.[6, 7]

Providing clear pathways for exercising rights and managing preferences is not only a legal requirement but also key to building user trust and empowerment, aligning with the spirit of privacy regulations.

8. Children's Privacy

8.1 Age Limitation

The Applications and their services are not directed to children under the age of 13 (or a higher age as stipulated in your jurisdiction, e.g., 16 in some EU countries).

8.2 No Knowing Collection

We do not knowingly collect any personal information from children under the specified age limit. Google Play has strict policies for children's apps [1, 3], Firebase prohibits the transmission of children's data [26], Google API policy prohibits using Google Sign-In for apps primarily directed at children [10], and Alipay and WeChat Pay also state their services are not for children.[18, 27] Clearly stating our apps are not directed at children is an important compliance step to avoid triggering these stricter regulatory requirements.

8.3 Handling of Discovered Collection

If we discover that we have inadvertently collected personal information from a child below the specified age without prior verifiable parental consent, we will take reasonable steps to delete that information as soon as possible. If you are a parent or guardian and believe your child has provided personal information to us, please contact us immediately using the contact information in Section 10.

9. Changes to This Privacy Policy

9.1 Policy Updates

We may update this Privacy Policy from time to time to reflect changes in our practices, service adjustments, or legal requirements. Privacy policies are dynamic documents and need to be kept up-to-date.[26]

9.2 Notification of Changes

For any material changes to this Policy, we will post a notice within the Applications or update the "Effective Date" at the top of this Policy page, and may notify you through other appropriate means (such as a website announcement). We encourage you to review this Policy periodically for the latest information. According to policies like Google OAuth, significant changes in data usage may require obtaining user consent again.[10]

9.3 Significance of Continued Use

Your continued use of the Applications after this Policy has been updated signifies your acceptance of the revised Privacy Policy.

10. Contact Us

10.1 Contact Information

If you have any questions, comments, or concerns about this Privacy Policy or how we handle your personal information, or if you wish to exercise your privacy rights, please contact us via:

• Developer/Company Name: CatchingNow
• Contact Email: [email protected]