Multi Counter Privacy Policy

Effective date: October 5, 2026

Seulgiroun Saenghwal Yeonguso (the “Developer,” a romanization of the Korean developer name shown on Google Play) respects the privacy of people who use Multi Counter. This policy explains what information the app processes, why it is processed, how it is retained or deleted, and the choices and requests available to users.

1. Information entered into the app and its purpose

Counter names, values, colors, steps, limits, action buttons, and tags are stored in the app's private local storage to provide counter and tag organization features. This information is not sent to a server operated by the Developer, and the Developer cannot access it remotely. The app has no account or sign-in feature.

If Android backup is enabled, app data may be backed up or transferred to a new device by the operating system or device manufacturer's backup and transfer services. That processing is governed by the settings and privacy policy of the backup service used by the user.

2. Information processed for advertising and consent

The app uses Google AdMob to display advertisements and Google User Messaging Platform to provide privacy choices where required. To provide and measure ads, perform analytics, prevent fraud and abuse, maintain security, and comply with applicable requirements, the Google Mobile Ads SDK may automatically collect or share the following categories of information:

This information may be processed by Google and by advertising technology providers selected according to the user's region and advertising configuration. Data is encrypted in transit. More information is available in the Google Privacy Policy, the Google Mobile Ads SDK data disclosure, and the consent or privacy choices screens shown in the app.

3. App usage analytics

The app uses Google Analytics for Firebase to understand and improve app usage and stability. Google Analytics for Firebase may automatically process an app-instance ID, the advertising ID when available, approximate location derived from a masked IP address, app lifecycle events such as app launches, screen views, sessions, and device and app information. The Developer may use this information to analyze app usage and screen engagement, improve the app, and, when connected to advertising services, measure advertising performance and attribution.

Where applicable law or Google's consent requirements apply, choices collected through Google User Messaging Platform are reflected in analytics-storage and advertising-related processing through Google Consent Mode. The actual scope of processing may vary according to the user's region, consent choices, device settings, and the Google service settings configured by the Developer. Analytics information is processed using Firebase and Google Analytics infrastructure and is encrypted in transit. More information is available in the Google Analytics for Firebase Google Play data disclosure, Google Analytics data safeguards, and the Google Privacy Policy.

4. Crash reporting

The app uses Firebase Crashlytics to identify and diagnose crashes. Crashlytics processes crash traces, installation and session identifiers, timestamps, app version information, and device and operating-system diagnostics. Google states that Crashlytics retains crash traces and associated identifiers for 90 days before beginning removal, encrypts this data in transit and at rest, and may process it on global infrastructure. The app does not attach an account ID, counter names, tags, or other user-entered counter content to crash reports through application code. More information is available in Privacy and Security in Firebase.

5. Privacy choices and user rights

When required by applicable law or Google's consent requirements, a “Privacy choices” item appears in the app menu. Users can review or change their consent choices there. Advertising ID choices can also be managed in Android settings.

Users can edit or delete counters and tags in the app. They can delete local app data by clearing the app's data in Android settings or uninstalling the app. Requests to access, correct, delete, restrict, or otherwise exercise rights available under applicable law can be submitted through the Developer contact shown under “App support” on the app's Google Play Store listing.

The app does not provide user accounts, so there is no separate account deletion process.

6. Retention and deletion

Local counter and tag data remains on the device until the user deletes an item, clears the app's data, or uninstalls the app. When a user deletes an item in the app, that item is removed from the app's active local storage. The Developer does not retain a copy of this local data and therefore cannot delete it remotely.

Copies retained in Android backup are governed by the backup service's settings and retention and deletion policies. Retention and deletion of advertising and consent-related data are governed by the policies of Google and the relevant advertising technology providers. Retention of Google Analytics for Firebase data follows the data-retention settings of the linked Google Analytics property and Google's policies. The app does not currently provide a per-installation control for deleting analytics data.

Crashlytics crash traces and associated installation identifiers follow Firebase's documented retention and deletion practices. Users may submit a privacy request through the contact method below, but the app does not currently provide a per-installation Crashlytics deletion control.

7. Security measures

Information entered into the app is stored in app-specific storage isolated by Android. Data transmitted by the Google Mobile Ads SDK and Google Analytics for Firebase is encrypted in transit using transport-layer security. Firebase states that Crashlytics data is encrypted in transit and at rest. The Developer does not send information entered into the app to a separate developer-operated server when it is not required for app functionality.

8. Children's privacy

The app is not directed to children under 13. The Developer does not knowingly collect personal information directly from children through the app. A parent or guardian who believes a child's information has been processed improperly may use the contact method below.

9. Changes to this policy

This policy may be updated when the app, its service providers, or applicable requirements change. Material changes will be indicated by updating the effective date above.

10. Privacy contact

Seulgiroun Saenghwal Yeonguso is responsible for privacy inquiries and related complaints.

Privacy inquiries and requests to exercise user rights can be submitted through the Developer contact shown under “App support” on the app's Google Play Store listing.