This Privacy Policy explains how the Counter application (the “App”) handles personal data.

The controller is Aleksei Samsonov,
Wuhlestraße 7a, 12683 Berlin, Germany.
For privacy questions or requests, contact contact@stawd.dev.

The App stores counter content, progress, and customization settings on your device, together with app preferences. Consent choices and privacy-option state are managed by Google User Messaging Platform in SDK-managed storage.

Counter content is used to provide the App’s functions and is not sent to an app-operated server. You can create, edit, reorder, delete, and undo a counter deletion in the App. Deleting a counter hides it from the active list; the App does not provide an in-app hard-delete or global erase control.

If you give your consent, the App uses Google Analytics for Firebase to understand how people use the App and to improve its features. The App records counter and edit actions, screen context, review actions, privacy-policy and privacy-preference clicks, and crash-report setting changes. No counter titles, values, or custom counter contents are included in the defined event parameters. The distribution market is set as a user property after successful consent completion.

Firebase Analytics also processes technical and usage data automatically. On Android, this includes an app-instance ID, advertising ID, masked IP address from which coarse location is derived, and app-lifecycle data such as screen views and sessions. The App does not set an Analytics User-ID, use account identifiers, or record in-app purchases or subscriptions. See the Google Analytics for Firebase Android data disclosure.

For full Analytics processing after consent, the legal basis is your consent under Article 6(1)(a) GDPR. The App uses Google User Messaging Platform to present and manage the available consent choices. You can manage those choices in the App’s privacy options. See the Google Privacy Policy.

The App uses Google’s Advanced Consent Mode. When Analytics consent is not granted, Google may receive the consent state and limited measurement signals for basic measurement and modelling. Full Analytics storage and measurement starts only after consent is granted.

Firebase Analytics retains event data for two months and user data for fourteen months. The user-data retention period restarts when there is new user activity. These settings do not affect standard aggregate reports. See Firebase Privacy and Security Information.

The App starts its consent-management flow at startup. Google User Messaging Platform presents and manages the available consent choices. When privacy options are required, they are available in About > Legal. The AdMob provider is initialized and banner requests are made only when the consent state allows ad requests. UMP passes the choices to Google’s Advanced Consent Mode for downstream Firebase Analytics and AdMob processing; the App does not duplicate this mapping with a separate Firebase API call. After a denial or withdrawal, downstream processing follows the no-consent state.

The App uses Google Mobile Ads through its AdMob integration for an adaptive banner in the regular Counter list. The App requests a banner only when the consent state allows ad requests; an ad request does not guarantee that a banner is displayed.

On Android, the Google Mobile Ads SDK automatically collects and shares IP address, user product interactions, diagnostic information, and device or account identifiers for advertising, analytics, and fraud prevention. Google may use the IP address to estimate approximate location. The App does not request Android location permission. There is no separate ad or location-data toggle. See the Google Mobile Ads Android data disclosure.

The App uses Firebase Crashlytics to diagnose crashes and errors and improve the App’s stability. Crash reporting is disabled by default. If you choose to enable it, Crashlytics processes crash reports. On Android, these can include stack traces, relevant app state, point-in-time device metadata, and a Crashlytics Installation UUID. Crashlytics also relies on Firebase Installation and session information. The App forwards release ERROR-level logs and exceptions and does not send a custom user ID or custom Crashlytics keys.

The legal basis is your consent under Article 6(1)(a) GDPR. You can choose whether to enable crash reporting in the App; declining does not restrict the App’s functions. If you turn crash reporting off, the change applies on the next App start. Turning off crash reporting does not delete reports already sent to Crashlytics.

Firebase states that it keeps crash stack traces, extracted minidump data, and associated identifiers for ninety days before beginning their removal from live and backup systems. See Firebase Privacy and Security Information.

Google Ireland Limited and its affiliates and subprocessors provide Firebase Analytics, Firebase Crashlytics, and Google User Messaging Platform. Google Mobile Ads (AdMob) provides the banner advertising described above. Firebase services may process data globally, including outside the European Economic Area. Google’s Firebase Data Processing and Security Terms incorporate the European Commission’s Standard Contractual Clauses for applicable transfers.

If you choose to open or submit an App review, the relevant app store processes that interaction under its own privacy information, such as the Apple Privacy Policy.

Depending on applicable law, you may have the right to request access to, rectification or erasure of your personal data, restriction of processing, data portability, or to object to processing. You may withdraw consent at any time; withdrawal does not affect processing that was lawful before it.

To exercise your rights, contact contact@stawd.dev. You also have the right to lodge a complaint with a data-protection supervisory authority.

We may update this Privacy Policy when the App’s data practices or applicable law change. The effective date below shows when the current version took effect.

This Privacy Policy is effective as of 2026-09-12.