Privacy
Privacy in Taskloc — what data is collected, when GPS coordinates are recorded, where data is stored in Russia, retention periods and who sees the data
Updated:
What is collected
GPS coordinates
GPS coordinates are recorded only during an active tracking session for a specific task. The app does not record coordinates in the background without your explicit action — pressing Start is required.
GPS tracking is off by default. You can turn it on in Settings → Tracking.
Tracker credentials
Tokens and passwords for all trackers are stored only on the device in encrypted Android storage (Android Keystore, Encrypted SharedPreferences). They are used for the direct connection of your device to the tracker: the device writes tasks, comments and time to the tracker directly. A token reaches the Taskloc server only if you turn on its upload yourself.
When you sign in with Redmine or Taiga, the Taskloc server checks the credentials in transit and does not store them.
For OAuth sign-in to Bitrix24, Jira Cloud, Linear and Yandex, the Taskloc server takes part in exchanging and refreshing the token but does not store the token itself.
Task cache
The task list, comments and projects are cached locally on the device (Room) and updated when syncing with the tracker.
Diagnostic events
Anonymized crashes and network errors are sent to a self-hosted GlitchTip (hosted in Russia). They contain no coordinates, passwords or message text.
Report a problem
A diagnostic snapshot is collected only when you tap "Report a problem" in the app, and it is shown to you in full before sending.
The snapshot contains: the app and Android versions, the device model, language and time zone; the account and organization identifiers; the types and addresses of connected trackers and their status; counters and error codes of the delivery queue; whether a tracking session is active and how long ago the last point was recorded; the results of permission, GPS and network checks; the id of the last GlitchTip event.
The snapshot does not contain: coordinates, task titles or texts, passwords or tokens, the device identifier, email.
The snapshot goes only where you send it yourself — to the support email or the support Telegram bot. The app transmits nothing on its own. No separate consent is required: sending it is the consent.
Usage statistics (optional, off by default)
If you turn on Settings → Send usage statistics, the app sends events about how it is used to the Taskloc server: the first launch and opening the app, a sign-in starting or failing, the task list loading, your answer to a permission request, the first steps in the app. Without your consent the app sends a single anonymous counter — the fact that the sign-in screen was shown, with the app version. It carries no installation ID, account, country or app store, and nothing is written to the device for it.
An event contains: a random installation ID (not linked to the device identifier), the app version, the store it was installed from and a two-letter country code. If you are signed in, the event is linked to your account.
Events do not contain: task content, coordinates, tracker credentials. The IP address is not stored on the server.
Turning the setting off erases the installation ID on the device and stops sending. Events are kept for 13 months; events linked to an account are deleted together with it, earlier than that. The sign-in screen counter is kept for the same 13 months. The record that consent was given or withdrawn is not subject to this period — it is the proof of the consent itself.
Geofences (optional, off by default)
If you turn on geofence reminders, the app compares your position with the sites pinned to tasks in the background. The coordinates of the sites are stored in your Taskloc account; the processing happens on the device.
Visit log (optional, off by default)
If you explicitly turn on the visit log, when you leave a task site the app sends a structured record to the Taskloc server (arrival time, departure time, site coordinates). Turning it on comes with a separate consent.
Where the data is stored
- Locally on the device: Android Keystore, Encrypted SharedPreferences, Room.
- Taskloc server: PostgreSQL in the Russian Federation (meets the requirements of Russian law 152-FZ).
Retention periods
| Data | Period |
|---|---|
| GPS sessions (with start and finish addresses) | by the organization's plan: Free — 90 days, Team — 365 days |
| GPS track points | 365 days |
| GPS batch receipts | 5 years |
| Visit log | 365 days |
| Audit log | 365 days |
| Sign-in events | 180 days |
| Delivery log, notifications, invitations | 90 days |
| Sign-in tokens, access decision log | 30 days |
| Diagnostic events | 30 days |
| Usage statistics | 13 months |
| Location view log | 365 days |
| Bitrix24 token exchange and refresh log (without the tokens themselves) | 3 to 4 days |
| Account (email, name, organizations, integrations) | until the account is deleted |
| Local cache on the device | until you sign out or clear it |
You can delete any session earlier from Routes.
Cookies and local storage (web dashboard)
This section is about the website and the web dashboard in a browser; the Android app does not use cookies.
| Cookie | Purpose | Lifetime | Accessible to scripts |
|---|---|---|---|
nuxt-session | Sign-in session | 30 days | no (httpOnly) |
oauth_web_state | Protects tracker sign-in against a forged response | 10 minutes | no (httpOnly) |
i18n_redirected | The chosen interface language | about a year | yes |
There are no other cookies: we do not set advertising or analytics cookies, do not use third-party counters, and serve fonts from our own servers. That is why the site does not ask for separate cookie consent — all three cookies are strictly necessary for it to work.
Visit counter: visits to the home page, the pricing page and the landing pages are counted by Umami, hosted on Taskloc's own server. It sets no cookies. There is no counter in the web dashboard or in the documentation; it is turned on by an instance setting — if the setting is not set, the script is not loaded at all.
Browser local storage (localStorage): a profile cache with your email and name (taskloc:cache:user_profile), caches of the organization list, settings and reference lists, your Redmine address, and a persistent browser identifier (taskloc-device-id) — a random number created on the first sign-in, not a device fingerprint. It is sent to the server with requests and tells your devices apart in the session list.
Tab storage (sessionStorage): the identifier of an unfinished payment — only for the duration of the payment.
Everything listed above lives in your browser and is removed by clearing the site data.
Error collection: interface errors are sent to a self-hosted GlitchTip. It is turned on by an instance setting; if the setting is not set, no reports are sent at all. GlitchTip sets no cookies and leaves nothing in browser storage.
External requests: the only request to a third-party service is for map tiles. With the public map source (used by default), the browser loads them directly from tile.openstreetmap.org, and OpenStreetMap sees your IP address and the address of the page the request came from. With your own tile source, the map loads from Taskloc servers and nothing goes outside.
Who sees the data
- You — all data collected about you.
- Your organization — according to the access policies. Access to other people's routes is possible only through membership in a shared tracker project.
- Manager (live map) — if the organization has turned on Team online, managers and admins see your location during an active or paused tracking session and only if you share a project with them. Outside a session and with tracking off, you are not on the map. This is monitoring during working hours, turned on by the organization deliberately.
- Your tracker — the tasks, comments and time the device writes to it directly; the tracker then processes them under its own policy. If you connect a tracker based abroad (Jira Cloud, Linear, GitHub, Asana and others), the data goes there from the device.
- Third parties — none: there are no advertising networks or third-party analytics services. App usage statistics and the site visit counter run on Taskloc servers and are not shared with third parties. The exception is the public map source: OpenStreetMap sees the IP address that requested the tiles (see "Cookies and local storage").
Who viewed my location
Every time someone else opens your location data, the server records it in a log: who, when, in which role and what exactly they opened. The kinds of entries: session track, live session track, your workday, team day, weekly timesheet, place history, visit registry, live map. The log holds no coordinates.
Only you can see the log: in the app — Settings → Tracking → Who viewed my location, in the web dashboard — the Who viewed my location block on the profile page. Entries are kept for one year.
Your rights
- Viewing routes: the Routes section in the app.
- Deleting a session: swipe the item in Routes → Delete.
- Deleting active sessions and the queue on the device: Settings → Tracking → Clear active sessions.
- Signing out: removes the credentials from the device.
- Deleting the whole account: in the app — Settings → Delete account, in the web dashboard — in the profile settings. The owner of a team organization with other members first transfers or deletes the organization.
- Access, correction, data export, objection, withdrawing consent: write to support@taskloc.com and include the email of your account. Usage statistics, the visit log and geofences can be turned off in settings — withdrawing consent applies from then on.
- Complaint: to Roskomnadzor (Russia) or to the data protection authority of your EU country.
App permissions
| Permission | When it is requested | Why |
|---|---|---|
| Location (precise) | On the first start of GPS tracking | Recording the route |
| Background location | When turning on geofences | Comparing your position with sites in the background |
| Notifications | On the first start of tracking | A foreground service requires a notification |
| Network | Always | Syncing with the tracker and Taskloc |
The full privacy policy is available at /privacy and in the app: Settings → Privacy → Privacy Policy.
On this phone only
Settings has an "On this phone only" mode.
The app does not contact the Taskloc server: tracks, time and tasks never leave the device, and data is written only to your tracker.
Technically this means the app makes no requests to the Taskloc server at all — not to sign in, not to check connectivity, not to check for updates. Only requests to your tracker and map tile downloads leave the phone. Error reports, analytics and address lookup are off in this mode.
How to sign in. Redmine, Kaiten, OpenProject, GitHub and Taiga sign in as usual — with a login or a token. Trackers that normally sign in via OAuth need a personal token in this mode:
- Jira Cloud — email and API token;
- Linear — personal API key;
- Wrike — permanent token;
- Bitrix24 — the portal's inbound webhook;
- Yandex Tracker — sign in with Yandex without auto-renewal: when the token expires, sign in again. With your own Yandex OAuth app the token renews on its own.
Limitations:
- the mode is available only outside an organization — organization members cannot turn it on;
- data lives only on the phone: losing the phone means losing the data;
- CSV + GPX export is the only copy of your tracks outside the phone;
- app updates come through the app store.
Leaving the mode. Turn the switch off and sign in to a Taskloc account. If the phone holds sessions recorded in the mode, the app asks whether to upload them to the account.