Privacy Policy
countertime
This policy explains how countertime processes personal data when providing stopwatch, countdown, session history, and synchronization features across devices.
Henrique Braga is responsible for the application and acts as the data controller. For privacy questions and requests, contact henriqueprofbrg@gmail.com.
1. Data processed by the application
- Session data: identifiers, the name you provide, timer mode, status, start and end dates and times, configured duration, elapsed time, and time markers. Information needed to manage synchronization is also stored.
- Account data, when you sign in with Google: your user identifier, name, and email address provided by the authentication service. The application receives a token to authenticate access; it does not receive your Google password.
- Technical and usage data: the application integrates Google Analytics for Firebase, which may automatically collect usage events, interactions, app instance identifiers, and information about your device, operating system, and app version. The service may also derive approximate location from your IP address. Collection depends on SDK, service, and device settings.
- Communications: if you send an email, your sender address, message, and any information you choose to provide will be processed to handle your request.
The application does not request access to your camera, microphone, contacts, or precise location. Training records are entered or generated while using the timer; the application does not read health sensors.
2. How we use data
- Run timers and let you view your session history.
- Authenticate your account and associate synchronized sessions with it.
- Upload and retrieve sessions across devices when you use your Google account.
- Understand app usage, evaluate how the app functions, and guide improvements using statistics.
- Respond to support, privacy, and deletion requests, protect the service, and meet applicable legal obligations.
Depending on the purpose and applicable law, processing may rely on performance of the service you request, compliance with legal obligations, legitimate interests consistent with your rights, or consent where required. Authorizing Google sign-in does not constitute unrestricted consent for other purposes.
3. Local storage and synchronization
Sessions are stored in a database on your device. You can use local features without signing in with Google. Using the app without an account does not, by itself, disable technical data collection by the Analytics SDK.
When you sign in with Google, completed sessions may be uploaded to Cloud Firestore, linked to your account identifier, and previously synchronized sessions may be retrieved on your device. Synchronization may take place automatically, including in the background, or when you trigger it manually.
Signing out stops synchronization associated with the authenticated session, but does not delete local history or records already stored in the cloud. Depending on your Android settings, local data may also be included in system-managed backups and device transfers.
4. Third-party services and sharing
We use Google/Firebase services for authentication (Firebase Authentication and Sign in with Google), storage and synchronization (Cloud Firestore), and usage statistics (Google Analytics for Firebase). These providers process the data necessary to deliver their respective services and may process it on servers outside Brazil, subject to their terms and applicable safeguards.
countertime does not sell your personal data and has no advertising integration in its current code. Data may also be disclosed when necessary to comply with a legal obligation or a valid order from a competent authority.
See the Google Privacy Policy, information about privacy and security in Firebase, and information about data protection in Google Analytics.
5. Retention and security
Local records remain on your device until you clear the application's data or uninstall it, subject to Android backup and restoration features. Uninstalling the application does not delete your account or sessions stored in the cloud.
Authentication data and synchronized sessions are retained while your account is active and until deletion is requested. Technical and Analytics data follow the retention periods configured in the respective Google/Firebase services. Support messages are retained for as long as necessary to handle requests and meet legal obligations.
After deletion, backups and technical records may remain temporarily according to provider retention cycles or legal retention requirements. Where applicable, we will explain the data categories and reasons for any retention in response to your request.
Firebase services use encrypted connections to transmit data. No transmission or storage method provides absolute security. Keep your device and Google account protected.
6. Your rights and choices
Under applicable law, including Brazil's General Data Protection Law (LGPD), you may request confirmation of processing and access to your data, correction, information about sharing, portability where applicable, anonymization, blocking, or deletion of unnecessary or unlawfully processed data, and withdraw consent or exercise other rights provided by law. You may also submit a complaint to Brazil's National Data Protection Authority (ANPD).
To exercise these rights, email henriqueprofbrg@gmail.com. We may request only the information needed to verify your identity and protect your data. Requests will be handled within applicable legal time limits.
7. How to request account and data deletion
You can request deletion without reinstalling the application. Email henriqueprofbrg@gmail.com with the subject “Account and data deletion — countertime”, preferably from the email address you used to sign in with Google.
Specify whether you want to delete your account and all associated data or only specific data. Never send your password or authentication codes.
Once the request has been verified, your countertime authentication account and the sessions and time markers associated with it in Cloud Firestore will be deleted, subject to the retention exceptions described in this policy. This request does not delete your Google account or data in other Google services.
To remove local copies, clear countertime's storage/data in Android settings. Also manage any backups in your system settings. Before removing local copies, sign out to prevent further uploads of pending sessions. Deleting your account does not prevent a new account from being created if you sign in with Google again.
8. Children and teenagers
countertime does not request your age or date of birth. If a parent or guardian identifies processing of a child's or teenager's data that requires their intervention, they may contact us for information and appropriate action. Processing of such data must comply with applicable law and the best interests of the child or teenager.
9. Changes and contact
This policy may be updated to reflect changes to features, services, or legislation. The date of the current version appears at the top of this page. Changes requiring additional notice or consent will be handled in accordance with applicable law.
Data controller: Henrique Braga
Application: countertime (dev.henriquesbraga.countertime)
Email: henriqueprofbrg@gmail.com