Counter Privacy Policy
Last updated
About this policy
This policy applies to Counter: Tally & History for Android
(app.counter.dailycount). You can use Counter without creating an account.
For privacy questions or requests, contact Counter’s developer at
anyd3v@gmail.com.
Your counters and history
Counter stores the titles you enter, the type of each counter, and a history of your increases and decreases with their dates and times. The app uses those records to show totals, activity and charts. It uses your device’s time zone to group daily counts.
These records stay in the app’s private storage. If you use Android backup or device transfer, Android may also copy the records to your backup or your new device. Manage those copies through Android or your backup provider.
App usage and crash reports
- Google Analytics for Firebase. Counter sends screen views and interaction labels, such as opening history or tapping a counter control, to help the developer understand how people use the app. Analytics can also receive session activity, app and device information, an app-instance identifier, and an approximate location derived from the network connection. The events Counter records contain labels for actions and screens, while counter titles, amounts, and saved history stay in app storage or Android backups.
- Firebase Crashlytics. To help the developer fix crashes and freezes, Google can receive crash and diagnostic reports containing stack traces, app and device information, installation identifiers, and recent app events that help explain what happened before the issue.
Counter uses these services for app measurement and troubleshooting. Firebase protects these transmissions with HTTPS. Google may process the data in countries other than your own. Read more about privacy and security in Firebase and how Google Analytics handles data.
Retention and deletion
- Counter records. Deleting a counter in the app removes it from your list. Its records remain in app storage until you clear Counter’s storage in Android settings or uninstall the app. Manage any remaining backups separately to prevent them from restoring the records.
- Analytics. Google retains individual usage records according to the property’s data retention settings. The default period is two months. Aggregated reports can remain after that period. See Google Analytics data retention.
- Crash reports. Google retains Crashlytics crash traces and associated identifiers for 90 days before it starts removing them from active and backup systems.
- Support email. If you contact the developer, your email address and any details you provide are used to respond and handle your request. The correspondence is kept as needed for follow-up, dispute resolution, or legal obligations.
For a request involving information already sent to Google or shared with the developer, email anyd3v@gmail.com. The developer may need enough information to verify your request and locate the relevant records.
This policy page
Google’s Firebase Hosting serves this page. It processes visitors’ IP addresses to deliver the page and help detect abuse. Google keeps this IP data for a few months.
Your privacy rights
Depending on the law that applies, you may have the right to access, correct, or delete your personal data, obtain a copy, restrict its use, or object to its processing. You may also be able to complain to your local data protection authority. To make a request, email anyd3v@gmail.com.
Any updates to this policy will appear on this page with a revised date.