Last updated: 22 August 2026
TClock (“the app”) is a smart time and location alarm app developed by Tabfires. This policy explains what information the app handles, why, and what control you have over it. It is written to meet India’s Digital Personal Data Protection Act, 2023 (DPDP Act) and Google Play’s User Data policy.
When you create an account we collect a username, your email address and a password. Sign-in is handled by Google Firebase Authentication: your password is sent directly to Firebase and is never seen or stored by us or by the app. If you sign in with Google instead, we receive your Google account identifier, email address and display name.
Your alarms are stored on your device. In addition, your time alarms — the time, the note you typed for the alarm, and whether it is switched on — are backed up to your account in Google Cloud Firestore, so that reinstalling the app or moving to a new phone restores them when you log in. Please avoid putting sensitive personal details in an alarm note.
Your alarm tone choice and app settings stay only on your device and are not backed up.
The location alarm (“LOC Alarm”) uses your phone’s location to measure the distance to a destination you pick. This happens entirely on your device. Your position, your destination, the alarm radius and your movements are never transmitted to us or to any server, and are not retained after tracking stops.
The one thing that does reach your account is a single true/false flag recording that a location alarm is currently running. It contains no coordinates, no destination and no radius — only the fact that tracking is active.
The app uses Google Analytics for Firebase to count how often features are used. The events it records are: app opened, sign-up, login, a time alarm was switched on, a time alarm rang, and a location alarm was started, fired or stopped. The only details attached to any of them are the alarm radius in kilometres and, for a sign-up or login, which method you used — the word “email” or “google”, never your address itself.
These events carry no coordinates, no destination names and no alarm notes. However, as part of its normal operation Google Analytics for Firebase also collects a randomly generated app-instance identifier, your device model, operating-system and app version, and an approximate location at country level derived from your IP address. This identifier is not your name or email, and we do not use it to identify you personally.
| What | Why |
|---|---|
| Account information | To create your account, sign you in, and let you recover your password. |
| Time alarms and their notes | To ring your alarms, and to restore them after a reinstall or phone change. |
| Location (on-device) | To detect that you have arrived at your destination and ring the alarm. |
| “Currently tracking” flag | To reflect, on your own account, that a location alarm is running. |
| Usage events | To understand which features are used, so the app can be improved. |
Under the DPDP Act, we process this data on the basis of the consent you give by creating an account and granting the permissions described below. You may withdraw that consent at any time by deleting your account.
| Permission | What it is used for |
|---|---|
| Location (while the app is in use) | Measuring the distance to your destination for a location alarm. The app does not request background-location access. |
| Notifications | Showing the ringing alarm, the trip progress notification, and the quiet “alarm set” indicator. |
| Alarms & reminders (exact alarms) | Ringing a time alarm at the exact minute you chose, even in battery-saving modes. |
| Foreground service (location & media playback) | Keeping a trip tracked after you leave the app, and playing the alarm tone until you stop it. |
| Reading an audio file you select | Only the single file you pick as a custom alarm tone. The app cannot browse your storage. |
The app relies on the following Google services:
asia-south1).These services are operated by Google, which acts as our data processor and may process some data (in particular analytics data) on servers outside India. Google’s own handling of data is governed by the Google Privacy Policy.
Traffic between the app and Google’s services is encrypted in transit (HTTPS/TLS). Your backed-up alarm data is protected by server-side security rules that allow only your own signed-in account to read or write it. No other user, and no unauthenticated request, can reach it.
You can delete your account at any time from Settings → Delete Account inside the app. This permanently deletes your account and your backed-up alarm data from our servers; it cannot be undone. Alarms and settings held on the device itself are removed when you clear the app’s data or uninstall it.
You may also request deletion by writing to the address in section 13.
Under the DPDP Act you have the right to access a summary of the personal data we hold about you, to have it corrected or completed, to have it erased, to withdraw your consent, and to have any grievance addressed. Account deletion inside the app exercises the erasure and withdrawal rights immediately; for anything else, write to us at the address below and we will respond within 30 days.
TClock is available worldwide, so this section sets out the additional information the UK and EU General Data Protection Regulation require. Where it conflicts with anything above, this section governs for users in those regions.
Tabfires is the data controller for the information described in this policy, and can be reached at tclock.support@gmail.com. We are based in India and have not appointed an EU or UK representative; we are a sole developer operating below the thresholds at which one is required.
| What | Lawful basis |
|---|---|
| Account information | Contract (Art. 6(1)(b)) — we cannot give you an account without it. |
| Time alarms and their notes | Contract — ringing and restoring your alarms is the service you asked for. |
| Location, on your device | Consent (Art. 6(1)(a)), given through the Android permission prompt. Nothing is transmitted, and you can withdraw it in your phone's settings at any time. |
| Usage and diagnostic events | Legitimate interests (Art. 6(1)(f)) — understanding which features are used so the app can be improved. No profiling, no advertising, no decisions are made about you. |
You have the right to access your personal data, to have it rectified, to have it erased, to restrict or object to its processing, and to data portability. Where we rely on consent, you may withdraw it at any time without affecting processing already carried out. Deleting your account in Settings → Delete Account exercises the erasure right immediately and completely; for anything else, write to the address above and we will respond within one month.
You also have the right to lodge a complaint with your local supervisory authority. You are welcome to raise it with us first, but you do not have to.
We are in India, and your account information and alarm backup are stored in Google Cloud Firestore in the Mumbai region. Analytics data may be processed by Google on servers elsewhere. Transfers out of the EEA and UK rely on the Standard Contractual Clauses that Google incorporates into its terms as our processor. Your location data is never transferred anywhere, because it never leaves your phone.
We do not carry out profiling or automated decision-making that produces legal or similarly significant effects.
If a breach occurs that is likely to result in a risk to your rights and freedoms, we will notify the relevant supervisory authority within 72 hours of becoming aware of it where the GDPR requires, report it to the Data Protection Board of India as the DPDP Act requires, and tell affected users directly without undue delay.
TClock is not directed at children. India's DPDP Act treats anyone under 18 as a child, and we do not knowingly collect their personal data. In the EEA and UK, where the digital-consent age is between 13 and 16 depending on the country, we do not knowingly collect personal data from anyone below the age that applies where they live. If you believe a child has provided us with personal data, contact us and we will delete it.
For any privacy question, data request or grievance under the DPDP Act, contact the person responsible for data protection at Tabfires:
Tabfires
Email: tclock.support@gmail.com
If this policy changes, the updated version will be published at this same address with a new “Last updated” date. Significant changes will also be announced in the app.