Effective date: October 14, 2026 · Last updated: October 14, 2026
This Privacy Policy explains how Track Fleet Pro 1 LLC ("Track Fleet Pro 1," "we," "us") collects, uses, shares, and protects personal information when you use our website trackfleetpro1.com, our web application, our mobile apps (when available on Google Play and the Apple App Store), and tracking links (the "Service"). It applies to users in the United States (including Puerto Rico), the Dominican Republic, and Honduras.
1. Summary
- Track Fleet Pro 1 is a real-time GPS tracking service for trucking fleets. Drivers' location is collected only during a shift the driver starts, and stops when the driver ends the shift.
- We do not sell personal information, do not use it for advertising, and do not use analytics, advertising pixels, or tracking cookies.
- Shippers who use a tracking link never see the driver's name, phone, photo, or route history.
- All data is stored in the United States (Northern Virginia).
- You can ask to access, correct, or delete your data, or delete your account, by writing to admin@trackfleetpro1.com (see Sections 9 and 10).
2. Who is responsible for your information
2.1. Track Fleet Pro 1 LLC, 300 Delaware Ave, Suite 210, Wilmington, DE 19801, USA, is responsible for the personal information of company users (carrier and broker administrators, dispatchers, broker users), website visitors, and waitlist sign-ups, and for information we use to secure and run the Service.
2.2. Carriers and brokers (our "Customers") are responsible for the information about their drivers and their shippers/customers that they enter into the Service or that is generated when their drivers use it (for example, driver records, documents, location history, trips, and end-customer contact details). For that information, we act as a service provider / processor on the Customer's behalf: we process it to provide the Service under the Customer's instructions and our contract, and not for our own purposes, except for security, legal compliance, and the limited purposes described in this policy.
2.3. If you are a driver or a shipper and want to know how your carrier or broker uses your information, please also contact that company. We will help them respond to your requests.
3. Information we collect
3.1 Carrier and broker users (administrators, dispatchers, broker users)
- Account: email, password (stored only as a secure hash by our authentication provider), language, and the date and time you accepted our Terms and Privacy Policy.
- Profile: full name, phone number, role, and language.
- Company information: company name, account type (carrier or broker), country, USDOT/MC number (U.S. companies), phone, address, tax ID (EIN or equivalent), primary contact (name, title, phone, email), plan, and approval status.
- Company documents: certificate of insurance (COI) and its expiration and coverage, MC operating authority, and IRS Form W-9 (U.S. only), plus file name, type, size, uploader, and upload time.
- Operational data: vehicles (unit number, plate, VIN, make, model, year); trips (reference, tracking number, BOL #, origin and destination addresses and coordinates, dates, notes, and the end customer's name, email, and phone); partners (name, contact, email, phone, country, DOT/MC).
- Load chat messages: message text, sender, sender type, display name, and time, exchanged among carrier, broker, and driver.
- Ratings and reviews: star ratings, reasons, comments, and responses between carriers and brokers. The author is not shown to the rated company.
- Broker Check lookups: who searched, the MC/DOT number searched, the result, legal name, and date.
- In-app notifications and administrative audit logs (for example, approvals, rejections, review moderation, and configuration changes).
3.2 Drivers
Most driver information is entered by the driver's carrier, not by the driver.
- Driver record: name, phone, email, driver's license number, and active status.
- Driver details: license state/region, country, class, and expiration; DOT medical certificate expiration; date of birth; emergency contact (name, relationship, phone); hire date; and company notes.
- Driver documents: a photo of the driver's license and, optionally, a photo of the DOT medical certificate. For U.S. carriers only the medical certificate's expiration date is required. The photo may contain health information, so it is uploaded only if the driver has given the carrier express written consent: the carrier must confirm this each time it uploads the photo (we record who confirmed it and when), and the driver can also confirm or withdraw this consent in the app.
- Compliance status and expiration alerts (30 days, 7 days, and on expiration). An expired document may pause the driver so they cannot start a shift.
- Verification selfies: if the driver's latest selfie is more than 30 days old, the app requires a new selfie taken live with the front camera (gallery photos are not accepted), together with the date and the shift it unlocked. The most recent selfie is the driver's profile photo. We do not create face templates or use facial recognition; the selfie is viewed by people, not matched by software.
- Shifts: start and end time, vehicle, and whether our administrator stopped tracking.
- Location data during shifts (see Section 4) and location alerts (type and reason, such as permission denied or no signal, and start and resolution time).
- Access codes: we store only a hash of the one-time code; for sign-in attempts we store a hashed IP address and a key derived from the phone number to prevent abuse.
- Driver acceptance: the date, time, and version of the Terms and location consent the driver accepted in the app.
3.3 Shippers and end customers (no account)
- Contact details that the carrier or broker enters in a trip: name, email, and phone.
- Shipment lookup: the BOL # and tracking number you enter.
- View log: the date and time of each view, the BOL # used, a hash of the session token, and a salted SHA-256 hash of your IP address (we do not store your actual IP address). Visible only to the broker on the load and our administrator.
- Failed lookups: hashed IP and the tracking number tried, deleted after 24 hours.
3.4 Website visitors and waitlist
- We do not use analytics, advertising pixels, or tracking cookies.
- If you join the "Notify me" waitlist for a country we do not yet serve, we store your email, country, and language. We currently do not send emails to the waitlist.
- Our hosting provider may keep standard server logs (such as IP address and browser type) for security and operations.
3.5 Public FMCSA data (U.S. companies)
- For Broker Check, we retrieve public data from FMCSA (QCMobile) and U.S. DOT open data: legal and DBA name, USDOT and MC numbers, operating status, broker authority, BMC-84/85 bond or trust information (provider, amount, policy, dates), address, and phone.
- For each U.S. company account, at registration, when the profile is saved, and then monthly, we retrieve public data such as operating status and authority, out-of-service orders, insurance and BMC filings, safety rating, 24-month inspections and out-of-service rates, crashes, violations, public BASIC alerts, and authority age. We use it to calculate an informational Safety Data Indicator, stored as a monthly snapshot. For a company's own account it is visible to that company and our administrator; through Company Check (Section 3.7) it is also shown publicly for any U.S. company searched. It is calculated by Track Fleet Pro 1, not by FMCSA, and it is not an official FMCSA rating.
3.6 Device data
We do not store your device model, device ID, or browser user-agent in our database. From the GPS we store accuracy, speed, and heading (Section 4).
3.7 Company Check lookups and reviews (no account needed)
Lookups. When anyone uses Company Check to look up a U.S. carrier or broker by USDOT or MC number, we record: the number and type of search; the date and time; the result (found or not; carrier or broker; whether it came from our cache); whether the search came from the website or the app; your country (a two-letter code provided by our hosting provider); a random browser ID (tf-visitor, stored in your browser's local storage, see Section 7); and a one-way hash of your IP address made with a secret key and the current date, so it changes every day. We do not store your IP address itself. If you are signed in to Track Fleet Pro 1, we also link the lookup to your account.
Why. To prevent abuse (lookup limits), keep the service secure, cache the public FMCSA record of the company searched, and measure how the feature is used in aggregate.
How we treat these identifiers. The browser ID and IP hash do not reveal your name, but they can recognize the same browser or connection over time, so we treat them as personal information (pseudonymized). We do not use them to identify you, combine them with other data to identify you, track you on other sites, or for advertising, and we do not attempt to re-identify them. You can delete the browser ID at any time by clearing your browser's site data.
Retention. The browser ID and IP hash are deleted from lookup records after 30 days. The rest of the lookup record (number searched, date, country, result) is kept for up to 12 months. Cached public FMCSA records are kept for up to 30 days, and the monthly history of the Safety Data Indicator for each company searched for up to 24 months. Only Track Fleet Pro 1 administrators can see lookup records.
What the results show. Results show public FMCSA data about the company (for example, legal name, USDOT/MC number, city and state, authority, insurance or bond, safety rating), our Safety Data Indicator and its monthly history, whether the company uses Track Fleet Pro 1, aggregate ratings, and the text of approved Reviews. They never show private account, driver, or shipper information. Because some carriers are individuals (for example, owner-operators), this information may relate to a person. It comes from FMCSA public records and from reviewers. If you believe information about you is wrong, see Section 9 or the Review Guidelines.
Reviews. If you submit a Review, we collect: the company reviewed; your star rating, good/bad choice, and text; your relationship with the company; your full name and email or phone number; the date, time, and version of the rules you accepted; your language; whether you were signed in (and, if so, your account); and, for anti-spam purposes, the browser ID and IP hash described above.
- Published: after moderation, the rating, text, date, your stated relationship, and a label ("Visitor" or "Signed-in Track Fleet Pro 1 user") are public to anyone using Company Check. A company with an approved Track Fleet Pro 1 account matching the USDOT/MC can also see its Reviews in its dashboard and report them.
- Never published: your name, email, phone, browser ID, and IP hash. Only Track Fleet Pro 1 administrators can see your name and contact. We use them only to prevent fake or duplicate Reviews, to contact you about your Review, to handle reports, and to respond to legal claims. We disclose them only if required by law or to protect safety, and we will try to notify you first (Terms, Section 10A.10).
- Legal basis and consent: you give us this information voluntarily when you check the box on the review form, which also records your consent to processing in the United States (Section 13).
- Retention: the browser ID and IP hash are deleted 30 days after you submit. If your Review is declined, we delete it and your name and contact within 30 days (we keep only a one-way hash of your contact for 12 months to prevent repeated spam). If your Review is published, we keep your name and contact for up to 36 months after publication, then delete them and keep the Review without them. If a published Review is removed (by you, by us, or after a report), we delete it and keep your name and contact for 24 months after removal (never more than 36 months after publication) in case of a legal claim about the period it was public. If we receive a legal claim or legal process about a Review, we keep the related information until the matter is closed.
- Your choices: you can ask us to remove your Review at any time (Terms, Section 10A.11) and exercise your rights under Section 9. In the Dominican Republic, this includes the rights of access, rectification, cancellation, and opposition under Law 172-13 (Section 15.3).
4. Location data: how driver tracking works
- When: only during a shift the driver starts by pressing START. Our database rejects positions outside an open shift and prevents carriers, dispatchers, and brokers from starting, extending, reopening, or changing a driver's shift. There is no pause: to stop being tracked, the driver ends the shift. Off shift, no live position is shown; past shift history remains available to the carrier.
- What: latitude, longitude, speed, heading, accuracy, and time, linked to the shift, driver, vehicle, and trip.
- How often: at most every 15 seconds when the device has moved at least 40 meters, and at least once per minute even when stopped, using high-accuracy GPS. Platform limits (15–60 seconds) can only be changed by our administrator.
- Signal loss: if location is turned off or unavailable, the app retries every 10 seconds; after 10 minutes without positions, an alert opens for the carrier and, if email alerts are on, an email may be sent to the carrier and the end customer about 2 minutes later. The end customer sees "location temporarily unavailable."
- Administrator stop: in exceptional situations our administrator can stop tracking and close the shift; this is logged and the driver is notified.
- Web vs. mobile: the web app sends location only while it is open and active. Our future mobile apps may collect location in the background — even when the app is closed or not in use — but only during an active shift the driver started, to provide real-time fleet tracking, ETAs, and route history. Before requesting that permission, the app will show a clear notice, and the driver can decline or revoke it in the device settings at any time (but tracking, and therefore the shift, will not work without it).
- Visible notice: the driver app and the carrier dashboard show "Driver privacy: you are only tracked during your shift."
- Who sees it: the driver's carrier (administrators and dispatchers); a broker only for loads the carrier shared with it; shippers only the last known position of their shipment while the shift is open (no history); and our administrator for support and security.
- Location data is never sold and never used for advertising.
5. How we use information
We use personal information to:
- Provide the Service: create and manage accounts, approve companies, show live location, ETAs, route history, and tracking pages, enable load sharing and chat, and send service emails (account confirmation, approval, GPS alerts, document expiration alerts, shared-load notices, FMCSA changes).
- Verify and protect: verify companies (DOT/MC, documents), verify that the person starting a shift is the assigned driver (selfie), prevent fraud and abuse (rate limits, hashed IPs, access-code limits), and keep audit logs.
- Provide FMCSA information: Broker Check, Company Check, and the informational Safety Data Indicator.
- Support and communicate with you, including about changes to the Service, these policies, or future pricing.
- Comply with law and enforce our Terms, and establish or defend legal claims.
- Improve the Service using de-identified or aggregated information.
Legal grounds (where required, such as in the Dominican Republic): we process information to perform our contract with you or your company (including steps before signing up), with your consent (for example, the driver's location consent and selfies), to comply with legal obligations, and using public sources (FMCSA data). You may withdraw consent at any time, which will not affect prior processing but may prevent use of features that depend on it.
We do not use personal information for automated decisions that produce legal or similarly significant effects on individuals. The Safety Data Indicator concerns companies, is calculated by Track Fleet Pro 1 (not by FMCSA), and is informational.
6. How we share information
We do not sell personal information and do not share it for cross-context behavioral advertising. We share it only as follows:
| Recipient | What | Why |
|---|---|---|
| Your company (carrier or broker administrators; dispatchers with limits) | Driver records, documents, location, trips, chat | To manage the fleet. Dispatchers cannot see selfies. |
| Brokers on a shared load | Load status, live location and ETA during the shift, BOL #, load chat, the driver's most recent selfie, and the shipper view log | When the carrier shares the load. The carrier never sees the broker's shipper. |
| Shippers / end customers via tracking link or BOL lookup | Shipment status, origin, destination, dates, ETA, last position during the shift | To track their shipment. Never the driver's name, phone, photo, or history. If a broker is on the load, the carrier's name and phone are hidden. |
| Rated companies | Ratings and comments (not the author's name or contact) | Marketplace trust and reporting. |
| The public (Company Check) | Public FMCSA data, the Safety Data Indicator and its history, aggregate ratings, and approved Reviews (rating, text, date, relationship, label) — never the reviewer's name or contact | To help carriers, brokers, and shippers check companies. |
| Service providers (processors) | As needed for their service | See the list below. |
| Authorities and others when required | As legally required | To comply with law, a valid legal order, or to protect rights, safety, and security. |
| Successor in a business transfer | As part of the transferred assets | Merger, acquisition, or sale, subject to this policy. |
Our service providers:
- Supabase (database, authentication, file storage, server functions, scheduled tasks), in its us-east-1 region (Northern Virginia, USA) — all Service data.
- Hosting provider for the web app (planned: Vercel) — HTTP request logs (such as IP address and user-agent).
- Google Maps Platform — maps in the dashboard, driver app, and tracking pages. Your browser connects directly to Google, which receives your IP address and the map area displayed. Google's use is governed by the Google Privacy Policy.
- SiteGround (email delivery via SMTP) — email address, name, and the content of service emails.
- FMCSA and U.S. DOT public services — we send only USDOT/MC numbers and receive public data.
We do not currently use analytics, push notification, SMS, or payment providers. If that changes, we will update this policy.
7. Cookies and browser storage
We use only strictly necessary and functional storage, not advertising or analytics cookies, so we do not show a cookie consent banner.
| Name | Type | Purpose |
|---|---|---|
sb-<ref>-auth-token (may be split) | Cookie | Keeps you signed in (strictly necessary) |
tf-locale | Local storage | Remembers your language |
tf-start-role | Local storage | Remembers the last role chosen on the start screen |
tf-stop-ack | Local storage | Records that the driver saw the "tracking stopped" notice |
tf-shipper-last | Local storage | Last BOL # and tracking number used on that device |
tf-shipper-view | Session storage | Shipper tracking session token (12 hours) |
tf-visitor | Local storage | Random browser ID used for Company Check lookup and review limits (abuse prevention). It is renewed automatically every 30 days; you can clear it in your browser settings. |
You can clear these in your browser settings; you will be signed out and preferences will be reset.
8. How long we keep information
We keep information only as long as needed for the purposes above, then delete or de-identify it.
| Information | Retention |
|---|---|
| Unconfirmed registrations | Deleted after 7 days |
| Detailed GPS points and location alerts | 12 months after the shift ends, then deleted |
| Shift summaries (start/end, vehicle, without GPS points) | 3 years after the shift |
| Trips, BOL #, end-customer contact details, load chat | 3 years after delivery |
| Driver verification selfies | Previous selfies deleted 90 days after being replaced; all selfies deleted within 30 days after the driver is deactivated or deleted |
| Driver documents and details (license, medical certificate, date of birth, emergency contact) | While the driver is active, then deleted 90 days after deactivation (the carrier should download any records it must keep by law first) |
| Company documents (COI, MC authority, W-9) and company profile | While the account is active, then deleted 90 days after account closure |
| Ratings and responses | While the rated company's account is active, up to 3 years |
| Shipper view log (hashed IP) | 12 months |
| Failed shipper lookups | 24 hours |
| Driver access-code attempts | 30 days |
| Shipper tracking session / tracking link | Expires after 12 hours / 7 days; the related record follows the trip retention |
| Broker Check cache / lookup history | 2 days / 2 years |
| Company Check lookups | Browser ID and IP hash deleted after 30 days; the rest of the record after 12 months |
| Company Check cache / monthly indicator history | 30 days / 24 months |
| Company Check reviews — declined | Deleted with the reviewer's name and contact within 30 days (contact hash kept 12 months) |
| Company Check reviews — published | Reviewer's name and contact deleted 36 months after publication; the Review stays while published |
| Company Check reviews — removed | Review deleted; reviewer's name and contact kept 24 months after removal (max. 36 months after publication) |
| Review reports | 24 months after the report is resolved |
| Monthly FMCSA snapshots | 24 months |
| Outgoing email queue | 90 days |
| Country waitlist | Until we launch in that country or 24 months, whichever is first, or earlier on request |
| Administrative audit logs | 5 years |
| Backups | Our current hosting plan has no automatic backups: data deleted from the live system is gone and cannot be restored. Manual exports, if we make any (for example, before a system migration), are stored securely and deleted within 30 days |
We may keep information longer if required by law, to resolve disputes, or to enforce our agreements, and only for that purpose. Carriers are responsible for keeping their own records required by transportation laws (for example, driver qualification files) outside the Service.
9. Your rights and choices
Depending on where you live, you may have the right to:
- Know and access the personal information we have about you, and get a copy in a portable format;
- Correct inaccurate information;
- Delete your information or your account;
- Withdraw consent (for example, location consent) and object to certain processing;
- Limit the use of sensitive information (we already use it only to provide the Service);
- Opt out of sale, sharing for targeted advertising, or profiling (we do not do these); and
- Appeal our decision on your request.
How to make a request: email admin@trackfleetpro1.com with the subject "Privacy request," your name, the email or phone linked to your account, your company, and what you are requesting. You can also use our web form at trackfleetpro1.com/delete-account, and delete your account yourself in the app (Section 10).
- We will verify your identity using information we already have (for example, a code sent to your account email or phone). An authorized agent may make a request on your behalf with your signed permission, where the law allows.
- We will acknowledge your request and respond within 10 business days. If we need more time where the law allows it, we will tell you why and respond within a maximum of 45 days in total.
- Drivers and shippers: because your carrier or broker controls most of your information, we may forward your request to that company and help it respond. Some information may need to be kept by the company or by us for legal reasons; we will tell you if so. If the company does not respond within 10 business days, we will act on your request for information the company is not required to keep.
- Appeals: if we deny your request, you can appeal by replying to our answer with the subject "Appeal." We will respond within 45 days. If you are not satisfied, you may contact the authority in your jurisdiction (for example, your state attorney general).
- We will not discriminate against you for exercising your rights.
10. How to delete your account
Track Fleet Pro 1 (developer: Track Fleet Pro 1 LLC)
- In the app: company owners go to Company profile → Account & privacy → Delete account; drivers go to Driver app → Account & privacy → Delete account. You tell us briefly why you are leaving and the request goes to our team for review; you can see its status and cancel it while it is pending. Once approved, the account is deleted right away (if a shift is in progress, as soon as it ends). We cannot keep or refuse a deletion request: if it has not been approved within 10 business days, it is carried out automatically.
- On the web (no app or account needed): trackfleetpro1.com/delete-account. We first verify that the request comes from the account holder (for example, with a code sent to the account's email or phone); the same 10-business-day limit applies from the day we receive it.
- By email (available now): write to admin@trackfleetpro1.com with the subject "Delete my account" from the email linked to your account (or include your phone number if you are a driver). You do not need to reinstall the app.
- What is deleted: your account and the personal information linked to it, within 10 business days of the request at the latest, with no automatic backup copies kept (see the retention table). If you are a company administrator, deleting the company account deletes the company's data, including its drivers, vehicles, trips, documents, location history, and chat, so please export what you need first. If you are a driver, your carrier will be notified, and your selfies, documents, and location history will be deleted unless the carrier must keep certain records by law.
- What we may keep: limited information we must keep for legal obligations, security, fraud prevention, or dispute resolution (for example, the administrative audit log), only for the periods in Section 8. Reviews you wrote may be kept in anonymized form.
11. Sensitive information
Some information we process is considered sensitive under certain laws, including precise geolocation, driver's license numbers and images, medical certificate information (only if a photo is provided with the driver's express written consent), tax IDs, and photos. We use it only to provide the Service as described in this policy, limit who can see it (for example, dispatchers and shippers cannot see selfies), and do not use it to infer characteristics about you. Drivers give explicit consent in the app before location is collected.
12. Security
We use reasonable administrative, technical, and physical measures to protect information, including encryption in transit (HTTPS), private storage buckets for documents and selfies, role-based access controls enforced in the database, hashed passwords, access codes, and IP addresses, rate limits, and audit logs of administrative actions. No system is 100% secure. If we learn of a security incident affecting your personal information, we will notify you and our Customers as required by law.
13. International data transfers
We are based in the United States and store all data in the United States (Northern Virginia). If you use the Service from the Dominican Republic, Honduras, or elsewhere outside the U.S., your information will be transferred to, stored, and processed in the United States, where data protection laws may differ from those in your country. We transfer it because it is necessary to provide the Service you or your company requested under our contract and, for drivers, with the consent given in the app. We protect it as described in this policy wherever it is processed.
14. Children
The Service is for businesses and is not intended for anyone under 18. We do not knowingly collect information from children. If you believe a minor has provided information, contact us and we will delete it.
15. Additional information by region
15.1 United States (including California and other states)
- Several U.S. states have consumer privacy laws (for example, California's CCPA/CPRA, and laws in Virginia, Colorado, Connecticut, Texas, Delaware, and others). Their applicability depends on thresholds such as revenue or the number of residents whose data is processed. We may not currently meet those thresholds, but we apply the principles in this policy to all users.
- Categories collected in the past 12 months: identifiers (name, email, phone, hashed IP; pseudonymous identifiers such as a random browser ID and a daily IP hash); customer records (address, tax ID, driver's license number); professional or employment information (role, company, hire date, license class, documents); commercial information (trips, BOL); geolocation (precise, during shifts); sensory information (selfies, document photos); internet activity limited to strictly necessary storage; and inferences or opinions about companies, which may relate to individual owner-operators, contained in public reviews. Sources include FMCSA public records and reviewers. Sensitive personal information: precise geolocation, driver's license, and, if provided, health-related information on medical certificates. Sources, purposes, recipients, and retention are described above.
- No sale or sharing: we have not sold or shared (for targeted advertising) personal information, including of consumers under 16.
- Where we are a service provider/processor, we will process personal information only under our Customer's instructions and contract, and we will help the Customer respond to requests.
- Employee monitoring notices (for example, in New York, Connecticut, and Delaware) are the responsibility of the employer or contracting carrier.
15.2 Puerto Rico and U.S. territories
The U.S. sections of this policy apply. We will also comply with any applicable local law.
15.3 Dominican Republic
We process personal data in accordance with Law No. 172-13 on the protection of personal data. You have the rights of access, rectification, cancellation (deletion), and opposition and may also bring a habeas data action before the competent courts. We request your free, express, and informed consent where the law requires it (for example, for drivers' location data), and your data will be transferred to the United States as explained in Section 13. We will respond to access requests within 5 business days and to rectification or deletion requests within 10 business days, as provided in Law 172-13. Health-related information (for example, on a medical certificate) is processed only with express written consent.
15.4 Honduras
As of the date of this policy, Honduras does not yet have a comprehensive personal data protection law in force. The Constitution of Honduras recognizes the guarantee of habeas data (Article 182), which allows you to access, update, rectify, or delete information about you held in public or private records. We honor these rights through the process in Section 9 and will update this policy if new legislation is adopted.
16. Changes to this policy
We may update this policy. If we make material changes, we will notify Customers by email and/or in the app before they take effect, and drivers will be asked to review them in the app. If a change affects how we use location data, we will ask for consent again where required.
17. Contact us
Track Fleet Pro 1 LLC — Privacy 300 Delaware Ave, Suite 210, Wilmington, DE 19801, USA Privacy and legal requests: admin@trackfleetpro1.com Customer support: Customerservice@trackfleetpro1.com Phone: +1 855-813-5338