Last updated: 2026-08-21
This page is also available in German / auf Deutsch.
The party responsible for data processing in connection with the TimeTracker app is:
Manfred Pauli
E-mail: soccertrash.dev@gmail.com
No postal address is listed here on purpose. For any question about this app or this privacy policy, the e-mail address above is the right way to reach out.
TimeTracker is built so that the developer receives, collects, and stores nothing. All time-tracking data stays on the user's own device — or, only if the user explicitly chooses it, in their own cloud account (Google Drive or iCloud). The developer runs no server of their own and never has access to this data.
That is not the same as "the app stores no data" — the app does store data, locally on the device. The distinction is: that data never reaches the developer.
All time-tracking data — projects, entries, timestamps, settings — is stored in a local Isar database directly on the device. This database does not leave the device on its own and is never transmitted to the developer. There is no background service sending it anywhere.
On Android, TimeTracker optionally offers a backup via Google Drive. This feature is opt-in — it only happens when the user actively triggers it — and user-initiated for every single backup run.
Technically, this requests exactly one permission scope:
drive.appdata (https://www.googleapis.com/auth/drive.appdata).
The backup file is written to the hidden, app-specific appDataFolder
space — inside the user's own Google account. With this scope the
app cannot see the rest of the user's Drive content, and the developer can
never see the backup. This document makes no sensitivity classification for
that scope.
On iOS, TimeTracker correspondingly offers an optional, likewise opt-in and user-initiated backup via iCloud. This backup, too, is written exclusively into the user's own iCloud container and is governed by Apple's own privacy terms. The developer has no access to it.
TimeTracker can show an end-of-day reminder directly on the device. This runs
entirely locally — there is no push server, no device token, and nothing
leaves the device for it. On Android the app declares exactly two permissions
for this: RECEIVE_BOOT_COMPLETED, so the reminder is re-armed after
the device restarts, and SCHEDULE_EXACT_ALARM, so it fires at the
exact time.
TimeTracker can export time-tracking data as PDF or CSV. The resulting file is either handed to the operating system's own share sheet or saved to a location the user picks themselves. What happens to the exported file afterwards is entirely the user's own choice — outside the app's control.
The app has an in-app feedback link. It opens the user's own mail app via a
mailto link, addressed to
soccertrash.dev@gmail.com. The
app itself sends no e-mail — that is handled by the user's own mail provider.
Device and app-version information is read locally only to prefill this
mail; the app never transmits this information anywhere itself — it is only
shared once the user sends the mail.
TimeTracker contains no analytics software, no crash reporting, no advertising, and no tracking SDK of any kind. There is no server operated by the developer for anything to be sent to. This claim is backed by an audit of every dependency, maintained in the app's own source-code repository.
Local data can be deleted by deleting individual entries in the app or by uninstalling the app entirely — either removes the local Isar database. A Google Drive backup can be removed through the user's own Google account: Drive settings -> "Manage apps" ("Apps verwalten" in the German-language UI) -> select TimeTracker -> remove access and associated data. An iCloud backup can likewise be managed and deleted through the device's own iCloud settings.
Under the GDPR, the following rights generally apply:
Because the developer holds no personal data belonging to the user, there is nothing for the developer to disclose, correct, export, or erase — these rights are, in practice, exercised directly on the user's own device or in their own cloud account, for instance by deleting entries or a backup. For any question about this, the contact address above remains available. Users also have the right to lodge a complaint with a data protection supervisory authority.
For the opt-in cloud backup (Google Drive or iCloud), the legal basis is Art. 6(1)(a) GDPR — consent. This consent is given by actively using the backup feature and can be withdrawn at any time by simply not using it, or by deleting the backup. For everything else, only local processing on the device takes place, entirely under the user's own control — the developer processes no data at all for these features.
TimeTracker is not directed at children under 13 and contains no child-specific features.
Changes to this privacy policy are published as a new version of this page with an updated last-updated date. The version history lives in the app's own source-code repository.