Transmaster Tracking

Privacy notice

Updated 14 October 2026

This notice describes information handled by Transmaster Tracking and its owner backup integration, Transmaster Backup.

Information handled by the service

Depending on the features used, records can include office and staff names, email addresses, login credentials stored as password hashes, truck and driver details, phone numbers, SIM tracking consent status, GPS locations and journey history, destinations, loading and freight records, e-way bill information and support requests. Session cookies support sign-in. A transport office is responsible for the information it enters and the tracking or sharing it requests.

Purpose and access

These records support account access, consent-based truck tracking, maps, trip sharing, operational reports and backup or recovery. Customer workspaces restrict records to authorized office accounts. Public truck or group links expose the tracking information selected for that link; anyone who receives a valid sharing link may view its contents. Share links only with intended recipients.

Providers and storage

Cloudflare hosts the website, databases and private cloud backups. Telenity supplies SIM tracking and consent services. Google Maps services provide maps and location tools. Resend supports application email delivery where configured. These services process the information required for their respective functions.

Google Drive backup integration

Google Drive backup is optional and must be authorized by the owner. When configured, Transmaster Backup uses the drive.file permission to create its backup folder and JSON backup files, and to inspect files accessible to this integration to identify its existing backups. This permission does not grant access to every unrelated file in the account.

The backup folder is named Transmaster Private Backups. Complete backups include operational and customer database records, including private contact and tracking information and password hashes. Google Drive file identifiers, upload status and timestamps are recorded to track backup results. The server uses a stored OAuth refresh token to obtain temporary access tokens for unattended uploads. The backup integration uses Google Drive access for backup operations; it does not use it for advertising or AI model training.

Uploaded files are stored in the owner's Google Drive and consume that account's storage. The integration does not create public sharing permissions. Access also depends on any sharing or account settings applied by the Drive owner. The separate Cloudflare backup remains available when a Drive upload fails.

Retention, deletion and revocation

Operational records and backup copies can remain until removed through account administration or storage management. Closing a trip does not necessarily erase its history or previously saved backups. No fixed automatic expiry for all backup files is currently specified. The Drive owner can delete backup copies in Google Drive and revoke Transmaster Backup access through Google Account settings. Revoking Drive access stops future authorized Drive uploads but does not delete already saved copies or Cloudflare backups. Contact support for account information corrections, deletion requests or help managing backup retention.

Security and contact

Access controls, HTTPS and server-side credential storage help protect the service. Downloaded backup files and sharing links must also be kept private by their recipients.

For privacy questions or requests, contact support@transmaster-tracking.com or call 8603333334. This notice may be updated when the service or integrations change.