CountPace Privacy Policy

Information handled by the app

CountPace does not require account creation or login and has no developer-operated server receiving your workout data. Advertising-related processing by Google is described separately below.

Counter names, counts, goals, Pace and Interval settings, and shared sound preferences are stored locally on your device using AsyncStorage. The app does not send those inputs to EzekielDevStudio or include them in its ad requests. A timestamp recording the expiry of an earned banner-hiding reward is also stored locally.

Local storage and deletion

Saved counts and preferences survive app restarts and compatible updates. Running timer progress is not saved as a resumable workout. CountPace does not provide workout history, its own cloud storage, or account synchronization. Operating-system backup and restore may handle app data according to your device settings.

You can reset counts and edit or remove counters within the app. Clearing the app’s storage in Android settings removes its local saved data, including the banner-hiding expiry. Uninstalling removes the installed app’s local data; device backups may be managed separately by your operating system. EzekielDevStudio has no server-side workout records to retain or delete.

Advertising, analytics, and tracking

CountPace is free and uses Google AdMob banners and optional rewarded ads. Completing a rewarded ad can hide banners until the next local midnight. There are no active purchases, subscriptions, or in-app billing SDKs in this release.

The Google Mobile Ads SDK can collect and share IP addresses (which may indicate approximate location), app and ad interactions, diagnostic information, and device or account identifiers such as advertising IDs and app set IDs for advertising, measurement, and fraud prevention. Processing depends on SDK configuration and device settings. Data is encrypted in transit.

The app requests non-personalized ads. This does not mean the advertising SDK collects no data. CountPace does not add a separate analytics SDK or send your counter names, counts, goals, or workout settings to advertisers. Google’s processing and retention are governed by its policies. You can manage your advertising ID in Android settings.

See Google’s Privacy Policy, Google advertising information, and Google Mobile Ads SDK data disclosures.

External pages and email

Help and privacy links open in your external browser. Visiting a web page sends ordinary web requests to its hosting provider; the browser and hosting provider may handle technical information under their own policies. This does not upload your counter inputs or workout settings.

If you choose to email us, your email address and message are received through our email provider and used to respond to your request. This is separate from data processed locally by the app. Please do not include sensitive information that is not needed for support.

Changes to this policy

Future versions may change how data is handled. If those practices change, we will update this policy and its effective date to describe them.

Contact

For questions about this policy, contact EzekielDevStudio at ezekieldevstudio@gmail.com.