Privacy Policy

DSP-OPS TRACKR ("TRACKR", "the App") is the companion Android application for the DSP-OPS platform, provided by CLJ Ventures ("we", "us", "our"). It is built for Delivery Service Partners (DSPs) to manage, monitor, and locate the company-owned work phones they issue to their own employees.

TRACKR is a business tool distributed to our DSP-OPS customers for installation on devices they own and issue for work. It is not available to the general public and is not intended for personal, non-work devices.

This Privacy Policy describes what information TRACKR collects, why, how it is used, stored, and protected, when it may be shared, and the choices available to users and organizations.

TRACKR does not collect anything until an employee enters their employer's DSP Code and a manager at that DSP approves the specific device in DSP-OPS. Once a device is enrolled and approved, depending on the permissions granted on that device, TRACKR may process:

• Precise device location (latitude, longitude, accuracy, and provider), reported periodically.

• Device manufacturer, model, Android version, and app version.

• Battery level and charging status.

• Network type and signal strength.

• Whether location services and permissions are enabled, and whether the tracking service is running.

• Phone number, only if available and only after the user confirms it with a single tap through Android's Phone Number Hint feature (a Google-provided picker) — this does not require or use any Android permission, and a manager can also enter the number by hand in DSP-OPS instead.

• A random, per-installation identifier generated by the app. It is not a hardware serial number.

TRACKR does not collect contacts, messages, call logs, browsing history, photos, or microphone or camera data, and never reads data belonging to other apps.

This information is used to provide the device-management features of DSP-OPS: showing an organization which of its devices are active, where its vehicles or equipment are, and whether a device is reporting correctly, and to help identify and contact a device when needed.

TRACKR is intended for use on company-issued or authorized work devices only. It is never used to build advertising profiles, for behavioral advertising, or to track anyone outside of their employer's own DSP-OPS account.

Information reported by a device is associated only with the DSP-OPS organization that approved it. Only authorized users within that same organization can view that device's details, status, and location — never another organization's users, and never DSP-OPS staff outside of ordinary platform operation.

Information is used solely to operate the device-management, monitoring, and location features of DSP-OPS. It is not sold, and it is not used to build advertising profiles or for behavioral advertising.

Device information is transmitted over HTTPS and stored in the DSP-OPS platform's backend infrastructure (hosted on Supabase), which acts on our behalf under a standard data-processing arrangement.

On the device itself, the credential TRACKR uses to authenticate with DSP-OPS is stored using the Android Keystore (hardware-backed encryption where the device supports it) and is excluded from cloud backups and device-to-device transfer. It is never exposed to the app's user interface.

Access to a device's information within DSP-OPS is limited to authorized users of that device's own organization.

Device information is shared only within the organization that approved the device, and with the infrastructure providers (currently Supabase) that operate the DSP-OPS platform on our behalf. We do not sell device information and do not share it with third parties for their own marketing purposes.

Information may also be disclosed where required by law, regulation, or valid legal process.

TRACKR's core function is reporting a device's location to the DSP-OPS organization that approved it, including while the app is not open (for example, while the phone is locked or the employee is using another app). This is why TRACKR requests "Allow all the time" location access.

Tracking is never silent: whenever it is active, Android shows a persistent notification on the device stating that location tracking is active, and the app's own screen shows the same status. Location is only reported once a device has been approved by a manager, and a manager can revoke a device at any time, which immediately stops reporting.

Users can review or change location permissions at any time in the device's system settings; doing so is also reflected honestly in the app and in DSP-OPS.

TRACKR requests the following Android permissions, and no others:

• Location (precise, and "Allow all the time") — reports the device's location, including in the background.

• Notifications — shows the persistent "tracking active" notification and status alerts.

• Boot / restart (RECEIVE_BOOT_COMPLETED) — restores tracking after the phone restarts, only for a device that was already approved; it never re-enables tracking for a device that isn't.

• Phone state (READ_PHONE_STATE) — optional and never prompted for; used only to show a more specific cellular network type (such as LTE or 5G) if that permission has already been granted by an organization's mobile-device-management policy. Declining or not having it has no effect on any other feature.

The phone number described in Section 1 is obtained through Android's Phone Number Hint picker, which is a Google Play services feature, not an Android permission — TRACKR does not request any permission to read the SIM's phone number.

Device location and status history is kept for as long as the device remains enrolled and approved. DSP-OPS organizations can configure automatic deletion of older location history (30 days by default once enabled); an organization may also choose not to enable automatic deletion, in which case history is kept until removed.

A device's access credential and queued data are deleted from the device immediately if the app is uninstalled or its data is cleared. On the backend, a device's data is deleted or disconnected when a manager revokes it in DSP-OPS. An employee can ask their employer's DSP-OPS administrator to disconnect and delete a device's data at any time.

Users can review or withdraw location, notification, and phone-number permissions at any time in the device's Android settings. Declining or withdrawing any permission never causes the app to misrepresent its status — it always shows the truth about what it can and cannot currently do.

Organizations control enrollment end-to-end: a device reports nothing until it is approved by that organization's own manager, and that manager can revoke a device at any time from DSP-OPS, immediately disconnecting it.

CLJ Ventures may update this Privacy Policy as TRACKR's features change. When we make a material change, we will update this page and revise the "Last updated" date above.

If you have questions about this Privacy Policy, or a request to review or delete a device's data, contact us at:

Email: Support@DSP-OPS.com