Privacy Policy
Effective date: September 8, 2026
Your information exists to serve you — not to become a product.
Salix Technologies does not sell, rent, trade, or provide Trip Master user information to advertisers, data brokers, or unrelated companies for marketing, behavioral profiling, or advertising. We do not build a business around tracking users. Information handled by Trip Master exists to operate, secure, support, and improve the service the user asked us to provide.
This Privacy Policy explains how Salix Technologies (“Salix Technologies,” “we,” “us,” or “our”) handles information when you use Trip Master, including the Android application, Trip Master Web, and related support and administrative services (collectively, the “Service”).
1. Information Trip Master Uses
Depending on the features you use, the Service may process:
- Account and profile information: email address, name, display name, employee or driver number, phone number, organization information, profile photo, account identifiers, roles, and permissions.
- Trip and work records: trip identifiers, mileage, dates, completion status, stops, trailer and plate information, confirmation numbers, notes, pay settings, estimates, and related records you enter.
- Training records: trainer/trainee assignments, employee identifiers, training dates and status, backing logs, notes, evaluations, CDL-related information entered for supported workflows, and equipment information.
- Training assignment and presentation information: curriculum sections or resources assigned to a trainee, trainer-configured Truck Rules, acknowledgement status, and limited presentation-session data such as the selected Trip Master training view, whether an item is open, session timestamps, and the last time the linked tablet reported that it was connected to the presentation.
- Location-related information: when you choose a feature that uses device or browser location, Trip Master may use that location to produce the result requested by the feature. If a location result is intentionally saved as part of a record, that saved result may be stored in the cloud with the record.
- Photos and files: profile photos and photos selected or captured for supported reporting features.
- Support and administrative records: support messages, account-management actions, permission changes, and administrative audit records.
- Service and security information: limited authentication, security, diagnostic, and infrastructure metadata needed to operate and protect the Service.
2. Location: What We Do and Do Not Do
Salix Technologies does not receive a continuous live GPS feed from Trip Master and does not use the app to monitor where you travel throughout the day.
Location access is used only when a feature needs location context and the user allows that access. Location may be processed on the device or browser to perform the requested function. When a feature saves a location result into a Trip Master record, the saved information can be synchronized to the cloud as part of that record. That cloud-stored result is different from continuous device tracking.
Salix Technologies personnel do not access a user’s cloud-stored location-related records as a matter of routine. Access may occur when reasonably necessary to provide support requested by the user, maintain or secure the Service, investigate misuse, or respond to a valid legal requirement.
3. How We Use Information
We use information only for legitimate Service purposes, including to:
- operate and synchronize Trip Master features;
- authenticate accounts and manage authorized roles, permissions, and organization access;
- store and display records created through the Service;
- synchronize an authorized trainer’s Trip Master training presentation between Trip Master Web and the linked Trip Master Android training screen;
- perform user-requested location-dependent functions;
- provide support and investigate technical problems;
- protect accounts, users, and the Service from misuse or unauthorized access;
- improve the reliability and usability of our products; and
- meet applicable legal obligations.
Training presentation control
Trip Master may allow an authorized trainer to control which assigned training section, Digital TM resource, or Truck Rules view is displayed inside Trip Master on a linked trainee or training tablet. This feature synchronizes Trip Master training-interface state through our cloud service. It is not designed to provide general remote access to the device, view another app, read keystrokes, change device settings, access the camera or microphone, or observe the user’s screen outside the Trip Master training experience.
Presentation-session state is used only to operate the requested training session, confirm that the linked Trip Master client is connected, and maintain the training experience. Assignment records and acknowledgements may be retained with the training record as described elsewhere in this Policy.
4. We Do Not Sell or Share Your Data for Advertising
We do not sell personal information. We do not rent or trade it. We do not provide Trip Master user information to advertisers, data brokers, or unrelated companies so they can market to you, profile you, or track you across services.
Trip Master does use infrastructure providers needed to deliver the Service. Google Firebase and related Google Cloud services may process information on our behalf for functions such as authentication, cloud database storage, file storage, synchronization, and hosting. These providers support the operation of Trip Master; they are not given your Trip Master records by Salix Technologies for independent advertising or marketing purposes.
Information may also leave Salix Technologies when you intentionally direct a feature to send or export it, or when disclosure is required by valid law or reasonably necessary to protect users, the Service, or legal rights.
5. Company-Created and Organization-Managed Accounts
In some cases, an employer, training organization, fleet, or other authorized organization may create or arrange a Trip Master account for an end user rather than the end user independently signing up for the Service.
When this occurs, the organization may provide limited account or work-related information needed to establish the account, assign roles, connect a trainer or trainee, or provide authorized access. Organization administrators may be able to manage organization-level access and records that fall within their authorized role. Creating an account through an organization does not give that organization ownership of unrelated personal information, and it does not change Salix Technologies’ commitment not to sell or use user information for advertising.
Users of company-created accounts may contact us at support@salixtechnologies.com with questions about the account, privacy, access, or deletion. Some work or training records may also be subject to the creating organization’s legitimate recordkeeping responsibilities.
6. Synchronized Curriculum Presentation
Authorized trainers may use Trip Master Web or another supported Trip Master client to control the curriculum presentation shown inside Trip Master on an assigned trainee device. This feature synchronizes presentation state through our cloud services so, for example, opening or closing a curriculum section on the trainer view can open or close that same section on the trainee device.
The synchronized presentation feature is limited to supported Trip Master content. It does not give the trainer general remote access to the trainee device, does not allow Salix Technologies or the trainer to view the device screen, and does not provide control over other apps, calls, messages, files, settings, cameras, microphones, or unrelated device functions.
Presentation-state information is used for app functionality, training continuity, security, and troubleshooting. It may include which curriculum section was selected or opened, whether a presentation is active, resource-open requests, and timestamps or connection-status signals.
7. Photos and User-Provided Content
Users may choose to provide a profile photo or use photos in supported reporting workflows. Only provide information you are authorized to submit. Avoid including unrelated sensitive information in photos, notes, or other records.
8. Data Security
We use technical and organizational safeguards designed to protect user information, including authenticated account access, role and permission controls, restricted cloud-storage rules, and the security protections provided by our infrastructure services. Access to administrative tools is limited according to assigned permissions. We also review and improve security controls as the Service evolves.
9. Salix Technologies Personnel Access
Access to user information by Salix Technologies personnel is limited to legitimate operational needs. We do not browse user records out of curiosity or use private records for unrelated purposes. Access may be necessary to respond to a support request, troubleshoot a technical problem, administer an authorized account, protect the Service, or comply with a valid legal obligation.
10. Administrative Audit Logs and Accountability
Salix Technologies uses administrative audit logging for supported corporate and account-management actions. These logs are designed to create accountability around sensitive changes such as permission updates, account-management actions, and other supported administrative events.
Audit logs are not a license to monitor users. Their purpose is to help authorized administrators understand what administrative action occurred, when it occurred, and, where supported, who performed it. They also help Salix Technologies investigate support issues, security concerns, disputed changes, or potential misuse.
Access to corporate administrative tools and audit information is permission-controlled. We continue to expand these controls as Trip Master and the Salix corporate platform evolve.
11. Data Retention
We retain account information and user-created records while they are needed to provide the Service and for legitimate operational, security, dispute-resolution, and legal purposes. When information no longer needs to be retained, it may be deleted or de-identified. If a specific record must be retained after an account deletion for a legitimate reason, we will limit the retained information to what is reasonably necessary for that purpose.
12. Account and Data Deletion
Users can request deletion of a Trip Master account and associated personal data through our Account & Data Deletion page or by contacting support@salixtechnologies.com.
After verifying a valid request, we will delete the account and associated user-specific data, subject only to information that must legitimately be retained for reasons such as legal compliance, security, fraud prevention, dispute resolution, or necessary record integrity. Where a shared operational record must remain, we will minimize or de-identify personal information where reasonably possible.
13. Your Choices and Controls
Optional profile information and optional photos do not have to be provided unless a particular workflow requires them. Device and browser permissions, including location access, can be controlled through the applicable device or browser settings. Disabling a permission may prevent the related feature from working.
14. Children’s Privacy
Trip Master is intended for professional and work-related use and is not directed to children under 13. We do not knowingly seek personal information from children under 13 through the Service.
15. Changes to This Policy
We may update this Privacy Policy as our products, legal obligations, or data practices change. Material changes will be reflected by an updated effective date and, where appropriate, additional notice.
16. How Our Development Approach Shapes Privacy
Salix Technologies is built and led by an active over-the-road truck driver. Trip Master was created from direct experience with the work it is intended to support, and development continues in that same environment.
Development may happen during off-duty time, at truck stops, terminals, customer facilities, or while team driving when another qualified driver is safely operating the vehicle. Development work is not performed in a way that interferes with safe vehicle operation or the responsibilities of the person driving.
This matters to our privacy philosophy because the people building the product are not separated from the realities of the users who depend on it. Salix Technologies understands firsthand what it feels like to be asked for personal identification, location information, work records, or other sensitive details in the course of a driving job. That perspective is one reason we treat access, accountability, and transparency as core responsibilities rather than marketing language.
Trust has to be earned every day.
My name is Tobias O. Wolf. I am the founder of Salix Technologies, and I am also an active over-the-road truck driver. Trip Master was not something I imagined from a conference room. I started building it because I was living the same problems I wanted the software to solve.
That is still how development works today. I work on Salix Technologies products during downtime, at truck stops, at terminals, and on the road while team driving when another qualified driver is safely operating the truck. Safety comes first; I do not develop while I am responsible for driving the vehicle. But I do build this software in the same environment where it is actually used.
That perspective affects how I think about privacy. I do not even enjoy handing over my driver’s license at a secure facility unless there is a legitimate reason for it. I understand the discomfort that comes with giving another company access to information tied to your identity, your work, or your location.
I do not believe users are a product. I do not want any driver, trainee, fleet, or other Salix Technologies user wondering whether we are quietly selling their information, building an advertising profile, or looking through private records without a legitimate reason. Salix Technologies should be a company people can trust with the information necessary to use our products — and nothing about that trust should be taken casually.
Our standard is to use information only when it is needed to provide, secure, support, administer, or improve the service the user asked for. Administrative access is permission-controlled, supported sensitive actions are backed by audit records, and private user information is not to be accessed out of curiosity or for an unrelated purpose.
Trust is paramount to me. If Salix Technologies ever betrays that value, I believe leadership should have to answer for it. As founder, I personally accept that responsibility. I want users to know who is behind this policy, how this company is actually built, and what standard I expect Salix Technologies to uphold.
— Tobias O. Wolf, Founder, Salix Technologies
17. Contact Us
Salix Technologies
Privacy and support inquiries:
support@salixtechnologies.com
