Money Counter Privacy Policy

Effective date September 26 2026

Seulgiroun Saenghwal Yeonguso, the Developer whose Korean name appears on Google Play, respects the privacy of people who use Money 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.

Information entered into the app

Denomination quantities entered by a user and the resulting total are processed on the device to provide the cash-counting feature. The current count may be included temporarily in Android saved state so the screen can be restored, but it is not sent to a server operated by the Developer or stored in an account. The app has no account or sign-in feature.

The selected currency code is stored in app-private SharedPreferences so the app can restore the same currency later. Users can replace this value by selecting another currency, or delete it by clearing the app's data in Android settings or uninstalling the app.

If Android backup is enabled, app-private data such as the selected currency may be processed by operating-system or device-manufacturer backup and transfer services. That processing is governed by the settings and privacy policy of the backup service used by the user.

Sharing

When a user taps Share, Money Counter creates a plain-text denomination breakdown and total and opens the Android share sheet. The information is transferred only to the app the user selects. The recipient app's privacy policy and settings govern its processing and retention after sharing.

Usage analytics

The app uses Google Analytics for Firebase to understand feature use and app quality. Google Analytics may automatically process an app-instance ID, the Android advertising ID, approximate location derived from a masked IP address, app launches, sessions, and other app interaction information.

The app disables Analytics collection by default and decides whether to enable collection after UMP refreshes consent information. Collection is enabled only when UMP's ad-storage, ad-user-data, ad-personalization, and analytics-storage purposes are all reported as granted or not applicable. Analytics remains disabled for any denied, pending, unconfigured, missing, or malformed value. Firebase's runtime collection setting can persist into a later app launch and is evaluated again after the UMP refresh. For users subject to European regulations, consent signals are handled through the published AdMob European regulations message and its advertising-purpose and Analytics-purpose consent mode configuration; if a purpose is returned as unconfigured, Analytics remains disabled.

The app records events for starting and completing a count, sharing a breakdown, and selecting a currency. These events may include the selected currency code and completion method. They do not include denomination quantities or the calculated cash total. As of the effective date, Google Ads linking, Google Signals, and BigQuery export are not configured.

See the Google Analytics for Firebase data disclosure and the Google Privacy Policy for more information.

Advertising and consent management

The app uses Google AdMob to show banner and app-open advertisements and Google User Messaging Platform to provide privacy choices where required. Ad requests begin only after UMP reports that the app may request ads.

For ad delivery and measurement, analytics, fraud prevention, security, and compliance, the Google Mobile Ads SDK may automatically collect or share:

The app itself does not request Android approximate-location or precise-location permission and does not directly obtain GPS location. The UMP consent form may nevertheless identify precise-geolocation use as potential processing for which selected advertising technology providers request consent. Actual processing depends on signals available from the device, the user's choices, region, and provider configuration. Users can review the relevant purposes and provider details through Manage options and the partner list in the UMP form.

Google and advertising technology providers selected according to the user's region and advertising configuration may process this information. Data is encrypted in transit. See the Google Mobile Ads SDK data disclosure and How Google uses information from partner apps for more information.

Crash reporting

The app uses Firebase Crashlytics to diagnose crashes and app-not-responding events. Crashlytics may process crash traces, installation and session identifiers, timestamps, app version information, device and operating-system diagnostics, and Analytics events recorded shortly before a crash.

The app does not attach an account ID, denomination quantities, or cash totals to Crashlytics through application code. Firebase states that Crashlytics keeps crash traces and associated identifiers for 90 days before beginning removal. See Privacy and Security in Firebase for more information.

Privacy choices and user rights

When a published UMP message requires a privacy entry point, a Privacy options button appears at the top of the app. Users can review or change advertising choices there. Users can also reset or delete the Android advertising ID in Android settings.

The app does not currently provide a separate control that lets every user disable Google Analytics or Crashlytics collection. 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.

Retention and deletion

The selected currency remains on the device until the user selects another currency, clears app data, or uninstalls the app. The current count is cleared when the user resets it or changes currency and may be retained temporarily by Android for screen-state restoration. The Developer does not keep a server copy of this local information and cannot delete it remotely.

Copies retained in Android backup follow the backup service's retention and deletion policies. Information processed by Google Analytics, AdMob, UMP, and Crashlytics follows the retention and deletion policies of Google and the relevant advertising technology providers. Users may submit a privacy request through the Google Play App support contact.

Security measures

Information entered directly into the app is processed in Android app-isolated storage and screen state. Google states that data collected by Google Analytics and the Mobile Ads SDK is encrypted in transit using transport-layer security. Firebase states that Crashlytics data is encrypted in transit and at rest.

Adult audience

Money Counter is intended for users aged 18 and over and is not directed to children. If the target audience or service changes, the Developer will review the related data handling and this policy.

Changes to this policy

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

Privacy contact

Seulgiroun Saenghwal Yeonguso is responsible for privacy inquiries. 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.