TrackizyThis policy explains what personal data the Trackizy Command and Trackizy Staff mobile applications collect, why we collect it, who it is shared with, and what you can do about it. It applies to both apps and to the Trackizy service they connect to.
These apps collect location data, including in the background on Trackizy Staff. Section 3 explains exactly when we collect it, what is recorded, and who can see it.
1. Who is responsible for your data
Trackizy is a workplace fleet- and workforce-management service. It is sold to organisations (employers), and it is used by the people who work for them. That creates two distinct roles:
| Role | Who | What they decide |
|---|---|---|
| Your employer the organisation that gave you the app |
The Trackizy customer | Whether tracking is on, when it runs, who inside the organisation can see it, and how long records are kept |
| Appaka FZ-LLC “we”, “us” |
Publisher and operator of Trackizy | How the service is built and secured, and which processors it uses |
If you are a worker using Trackizy Staff, your employer decides whether your location is collected and who inside your organisation can see it. Questions about why you are being tracked, or requests to stop, should go to your employer first. We can act on requests about how the service itself handles data — see section 10.
2. Which apps this covers
- Trackizy Command
io.appaka.trackizyfleet— the manager/administrator app. Shows the live map, vehicles, alerts, reports and chat. - Trackizy Staff
io.appaka.trackizystaff— the worker app. Shift tracking, assigned work, proof of delivery, check-ins, emergency SOS and chat.
Both connect to the same Trackizy backend operated by Appaka FZ-LLC.
3. Location data
This is the most sensitive category of data the apps handle, so it is described in full.
3.1 Trackizy Staff — precise location, including in the background
What we collect. Latitude and longitude, horizontal accuracy, altitude, speed, heading, the device battery percentage, the time of the GPS fix, and the app version that recorded it.
When we collect it. While you are on shift, and only after you grant location permission. Trackizy Staff requests background location so that tracking continues when your screen is off or the app is not in the foreground — this is what makes the delivery verification, arrival detection and lone-worker safety features work. On Android this runs as a foreground service with a persistent notification, so you can always see when tracking is active.
Why we collect it.
- to show your employer’s dispatchers where you are during a shift;
- to automatically detect arrival at an assigned stop and complete it;
- to attach a location to a delivery, inspection or check-in as proof of where it happened;
- to route help to you if you trigger an SOS, miss a check-in, or are asked to respond to an emergency roll call;
- to evaluate the safety and operational alert rules your employer has configured — for example, entering a high-risk area, or leaving a site.
Where it goes. Your positions are sent to the Trackizy backend and stored there. Inside your organisation, they can be seen by administrators and managers. They are not shared with other organisations, and they are not sold or used for advertising.
When we do not collect it. When you are off shift, when you have not granted permission, and when you have revoked it. Revoking location permission stops collection; it may also stop features that depend on it from working.
3.2 Trackizy Command — foreground location only
Trackizy Command requests location while the app is in use, to centre the map on you and to hand off a destination to your maps app. It does not request background location and does not track a manager’s movements.
3.3 Vehicle locations
Both apps display positions reported by GPS hardware installed in vehicles. That data comes from the tracking devices, not from your phone. Where a vehicle is assigned to a named driver, its position history can be linked to that person by their employer.
4. Other data we collect
Account and identity
Name, email address, phone number, the organisation(s) you belong to, your role, your language preference, and a securely hashed password. Trackizy Staff accounts are created by phone number with a one-time SMS code.
Photos and camera
Photos you take or choose — proof of delivery, form and inspection attachments, chat photos, and custom map icons. The camera and photo library are accessed only when you actively use one of those features.
Voice messages
Voice messages sent from the Trackizy web application can be received and shown in the mobile apps. The mobile apps do not record audio and do not request microphone access.
Signatures
Where your employer requires a signature to complete a job, the signature you draw is stored with that job record.
Messages
The content of chat messages, conversations and broadcasts you send or receive within your organisation.
Safety and welfare records
SOS alerts — including the location at the moment they were raised — check-ins and missed check-ins, muster/roll-call responses, and incident records.
Work records
Assigned jobs and stops, their outcomes and any reason you gave for a failed stop, shift start and end times, and the performance figures shown on your personal scorecard.
Device and diagnostic data
Device model, operating system version, app version, a push notification token and IP address. Where crash reporting is enabled for a release, crash and error reports are also collected.
Biometrics — stays on your device
If you enable Face ID, Touch ID or fingerprint unlock, authentication is performed by your device’s operating system. We never receive, see or store your biometric data. The app is only told whether the check succeeded.
5. Why we use your data
- To provide the features described above.
- To deliver notifications, alerts and emergency messages.
- To keep the service secure — authentication, abuse prevention and audit logging.
- To diagnose crashes and fix defects.
- To meet legal obligations.
We do not use your data for advertising, we do not sell it, and we do not share it with data brokers.
6. Automated decisions
Trackizy evaluates rules your employer configures — for example, alerting when a vehicle speeds, when a worker enters a defined area, or when a check-in is missed. These rules generate notifications and records. They do not by themselves make decisions that produce legal or similarly significant effects about you. How your employer acts on an alert is your employer’s decision, and their policies govern it.
8. International transfers
Trackizy’s servers are located in Germany. Some of the providers listed in section 7 process data in other countries, including the United States. Where required, we rely on appropriate safeguards for those transfers.
9. How long we keep your data
- Account data is kept while your account exists.
- Location history, work records, messages and safety records are retained by your employer as part of their operational record. We do not automatically delete this data after a fixed period — it is kept until the account is deleted or the organisation’s data is removed. Your employer may apply its own retention rules.
- Crash diagnostics are retained according to our diagnostics provider’s schedule.
10. Your rights and your choices
Permissions
You can grant or revoke location, camera, photo, microphone and notification permissions at any time in your device settings. Revoking a permission disables the features that need it.
Deleting your account (Trackizy Staff)
You can delete your account from inside the app: Profile → Delete account. When you do:
Permanently deleted
- your entire location history
- your push notification registrations
- your linked messaging channels
- your inclusion in alert rules that target you individually
- your membership of the organisation, which ends your access
Retained, no longer linked to you
Records of work performed for your employer — completed jobs, forms, inspections and safety records — remain with your employer as their business record, attached to an anonymised placeholder rather than to your name, phone number or email.
Deleting your account cannot be undone.
Trackizy Command accounts are created and removed by your organisation’s administrator.
Access, correction, objection and portability
To request a copy of your data, correct it, object to processing or request erasure, contact your employer’s Trackizy administrator first — they control the data. You can also contact us at hello@appaka.io and we will assist. If you are in the EEA or UK you have rights under the GDPR, including the right to complain to your national supervisory authority.
11. Children
Trackizy is a workplace tool intended for people aged 18 and over. It is not directed at children and we do not knowingly collect data from them. If you believe a child has provided us data, contact us and we will delete it.
12. Security
Data is transmitted over encrypted connections (HTTPS/TLS). Credentials and session tokens are stored in the device’s secure keystore — iOS Keychain or Android Keystore. Access is scoped so that each organisation can only reach its own data, and privileged actions are audit-logged. No system can be guaranteed perfectly secure, but we work to protect your data and to respond quickly if something goes wrong.
13. Changes to this policy
We will post any changes on this page and update the date at the top. Material changes will be communicated in-app or by email before they take effect.
14. Contact
AL Hamra Industrial Zone-FZ,
Ras Al Khaimah, United Arab Emirates hello@appaka.io