1. Introduction
1.1. Welcome
1.1.1. Welcome to Vektor TMS. This Privacy Policy explains our practices concerning the collection, use, and sharing of your personal information. By using Vektor TMS, you accept and consent to the practices described here.
1.2. Purpose and Scope
1.2.1. This Privacy Policy applies to all products, services, and websites offered by Vektor TMS and its affiliates ("Vektor TMS" or "we"), excluding those with their own Privacy Policy. It aims to provide transparency about our data practices and the choices available to you.
1.3. Our Commitment
1.3.1. At Vektor TMS, we respect your privacy and are committed to maintaining transparency, accountability, and the security of your personal data.
2. Definitions
2.1. Personal Information: Data that identifies an individual, including names, email addresses, postal addresses, phone numbers, IP addresses, or device IDs.
2.2. Processing: Operations on personal data, such as collection, storage, use, or deletion.
2.3. Data Controller: The entity determining the purpose and means of processing personal data (Vektor TMS).
2.4. Data Processor: An entity processing data on behalf of the Data Controller.
2.5. Consent: Freely given agreement to process personal data.
2.6. By using Vektor TMS and agreeing to this Privacy Policy, you consent to the collection and use of your data as outlined.
3. Information Collection
3.1. Types of Information Collected
3.1.1. Personal: Name, email, phone number, etc.
3.1.2. Demographic: Age, gender, location, etc.
3.1.3. Behavioral: Interaction data like browsing patterns.
3.1.4. Technical: IP addresses, cookies, and device IDs.
3.1.5. Documents and Capture Data: Documents, photos, and scans that you or your drivers upload or capture through Vektor TMS, the text and information extracted from them, and related capture information, as described in Section 4.3.
3.2. Methods of Collection
3.2.1. Direct Input: Account creation, forms, or customer support.
3.2.2. Automated Tracking: Cookies, IP addresses, web tracking, and in-app analytics and session replay in our driver mobile apps, as described in Section 4.4.
3.2.3. Third-party Sources: Partners, advertisers, and integrated services.
3.3. Purpose of Collection
3.3.1. Service delivery and personalization.
3.3.2. Communication and marketing.
3.3.3. Security and legal compliance.
3.3.4. Improving our services, including training and evaluating our own machine learning models as described in Section 4.3.
4. Use of Collected Information
4.1. How Information is Used
4.1.1. To register and manage accounts.
4.1.2. To enhance user experience and navigation.
4.1.3. For marketing and promotional purposes. This excludes mobile phone numbers, text messaging opt-in data, and messaging consent, which are never used for marketing or promotional purposes. See Section 7.
4.1.4. For research, analysis, and legal compliance.
4.1.5. To train, evaluate, and improve the machine learning models that power Vektor TMS document features, as described in Section 4.3.
4.2. Legal Bases for Processing
4.2.1. Consent: Promotional emails require explicit consent.
4.2.2. Contractual Necessity: Data used to fulfill service obligations.
4.2.3. Legitimate Interests: For security and service improvement.
4.2.4. Legal Obligation: Compliance with laws and regulations.
4.3. Machine Learning and Model Training
4.3.1. What this covers: Vektor TMS uses machine learning models to find document pages in camera images, improve image quality, read printed text (optical character recognition), and extract information such as load numbers, dates, page counts, and the presence of signatures. We train and evaluate these models, which we own and operate, so that these features become more accurate and reliable for all of our customers.
4.3.2. Information we use: For this purpose we may use: (a) documents, photos, and scans uploaded or captured through Vektor TMS, such as bills of lading, proof-of-delivery documents, lumper receipts, fuel receipts, scale tickets, and compliance documents; (b) the original camera image captured by the Vektor TMS document scanner before the page is cropped and enhanced; (c) the text, fields, and page locations extracted from those documents; (d) capture information, such as the detected page corners and any adjustments made to them, image-quality measurements, device model, camera settings, and capture time; and (e) corrections that you or your team make to extracted information. We do not use precise location data for model training.
4.3.3. Sensitive documents: Driver's licenses and other government-issued identification, medical examiner's certificates and other medical records, drug and alcohol testing records, motor vehicle records, and tax forms such as Form W-9 are used only to improve how Vektor TMS reads those types of documents. They are kept in separately access-controlled training datasets and are never used to make decisions about the individuals they describe. A customer may opt out of the use of these document types separately under Section 4.3.9.
4.3.4. No biometric identifiers: Our models are built to read documents, not to identify people. We do not use document images to create face geometry, face templates, or any other biometric identifier, and we do not train models to recognize individuals.
4.3.5. How training data is protected: We use only the information needed for the model being developed. Training data is stored encrypted in the United States and is accessible only to authorized Vektor personnel and to service providers bound by written confidentiality and data protection obligations. Training runs on cloud computing infrastructure in secured data centers under contract with us. We do not use peer-to-peer or community-hosted computing for this data, and we delete copies of training data from that infrastructure when a training run ends.
4.3.6. Retention: Information is kept in a training dataset only as long as it is needed for model development, and no longer than two years after it is added. Documents deleted from Vektor TMS are excluded from training datasets created after the deletion.
4.3.7. Trained models: Trained models consist of learned numerical parameters, not copies of your documents, and we take reasonable steps to prevent them from reproducing training data. Models may be included in our mobile apps so that document features can run on your device.
4.3.8. No sale and no third-party training: We do not sell your documents or the information extracted from them, and we do not provide them to third parties for the purpose of training those parties' own models.
4.3.9. Your choices: An account administrator may opt the company out of model training at any time by contacting [email protected]. Drivers and other individuals may also contact us to opt out of the use of documents they captured. An opt-out may cover all model training, only the sensitive document types in Section 4.3.3, or only the upload of original camera images. We process opt-out requests within 30 days. An opt-out applies to training datasets created and training runs started after we process it, and it does not affect your use of Vektor TMS.
4.3.10. Effective date and earlier documents: This Section 4.3 takes effect on October 28, 2026, and applies to documents uploaded or captured on or after that date. Before that date, limited internal development of these features relied on our Terms of Service, which permit us to use content to improve the services. We will not add documents uploaded before October 28, 2026 to new training datasets without the customer's express opt-in consent.
4.3.11. Legal basis: Where a legal basis is required, we rely on our legitimate interest in providing accurate and secure document features, balanced against the safeguards and choices described in this Section 4.3, or on your consent where Section 4.3.10 requires it.
4.4. Mobile App Analytics and Session Replay
4.4.1. What this covers: This Section 4.4 applies to the Vektor Driver app and to the company-branded driver apps we provide, on iOS and Android (the "Driver Apps").
4.4.2. Product analytics: The Driver Apps send product analytics events to PostHog, Inc., our analytics service provider. The data is hosted in PostHog's United States cloud. The events describe which screens are opened, which actions are taken and which errors occur. They are linked to your driver ID and your company, and to the name, email address and phone number in your driver profile. They also include the app version, the device model and operating system, the device's IP address, and an approximate location (city and country) derived from that IP address.
4.4.3. Session replay: While a Driver App is open on the screen, it may record what the app displays, such as names, phone numbers, addresses, trip and load details, messages, truck inspection photos and the taps made in it. It does not record while the app is in the background, and it does not record network traffic or app logs. We use these recordings to diagnose errors and improve the Driver Apps.
4.4.4. Masked information: Session replay masks money code values, bank account details, documents and scans, selfies, photos of driver's licenses, and the camera and photo confirmation screens.
4.4.5. Controls: If your company turns off screenshots for your driver type in Vektor TMS, session replay is off for you. We can also turn recording off remotely.
4.4.6. Retention: Session recordings are deleted after 30 days. Analytics events are kept only as long as we need them for the purposes in this Section 4.4, then deleted or anonymized.
4.4.7. Legal basis and your choices: Where a legal basis is required, we rely on our legitimate interest in keeping the Driver Apps reliable and improving them, balanced against the masking and controls described in this Section 4.4. You can object to session replay at any time by emailing [email protected]; we will then stop recording your sessions.
5. Cookies and Tracking Technologies
5.1. Types of Cookies
5.1.1. Essential: Necessary for site operation.
5.1.2. Performance: To monitor usage trends.
5.1.3. Functionality: To remember user preferences.
5.1.4. Advertising: For targeted ads.
5.1.5. Analytics: To improve platform performance. Analytics and session replay in our driver mobile apps are described in Section 4.4.
5.2. Managing Cookie Preferences
5.2.1. Adjust browser settings to accept or refuse cookies.
5.2.2. Use third-party tools for specific tracking preferences.
5.3. Advertising and Campaign Measurement
5.3.1. Subject to the controls in Section 5.4, we may use the Meta Pixel, TikTok Pixel, and Google Ads tag to measure visits and understand whether advertising campaigns lead people to our website.
5.3.2. These technologies may receive the page URL, referring page, browser and device information, IP address, advertising identifiers, and the time of a page visit. Meta, TikTok, and Google process that information under their own privacy terms.
5.3.3. We configure these technologies to record a standard page view. Additional conversion events, if enabled, are limited to actions such as submitting a form, starting a trial, or confirming a demo booking.
5.4. Regional Controls and Opt-Out
5.4.1. For visitors detected in the European Union, European Economic Area, or United Kingdom, advertising pixels do not load unless the visitor accepts them.
5.4.2. For visitors detected in California, advertising pixels may load unless the visitor selects "Do not sell or share." Visitors in other regions receive a notice and may opt out at any time.
5.4.3. The choice is stored in the first-party vk_consent cookie for up to one year. The choice applies to advertising pixels in that browser and does not disable cookies required for site operation.
You can stop Meta, TikTok, and Google advertising pixels on this browser at any time.
6. Data Sharing and Third-Party Involvement
6.1. Third-Party Categories
6.1.1. Service Providers: Payment processors, hosting services, cloud computing providers, and analytics providers (such as PostHog, Inc. for our driver mobile apps under Section 4.4) that process data on our instructions, including for model training under Section 4.3.
6.1.2. Affiliates: For business operations.
6.1.3. Legal Bodies: As required by law.
6.1.4. Potential Buyers: During mergers or acquisitions.
6.1.5. Parties a Carrier Shares a Load With: When a carrier using our services shares a load with a broker, shipper or customer, through a tracking link or a connection between Vektor accounts, that party can see the information about the load and its assigned driver that the carrier chooses to share. This can include the location of the driver's device, truck and trailer while the load is active, the driver's name and profile photo, the driver's phone number where the carrier allows it, and the documents and photos uploaded for the load.
6.2. Safeguards
6.2.1. Data Processing Agreements with third parties.
6.2.2. Encryption and secure data transmission.
6.3. Limits on Sharing Mobile Information
6.3.1. Every category listed in Section 6.1 excludes text messaging originator opt-in data and messaging consent. No mobile information is shared with third parties or affiliates for marketing or promotional purposes, and text messaging opt-in data and consent are not shared with any third parties. Service providers receive a mobile phone number only for the purposes in Section 7.1.1.
6.4. Server-Side Conversion Measurement
6.4.1. We may send limited conversion records directly to Meta and TikTok through their server-side conversion services. These records may describe a form submission, trial start, or confirmed demo booking.
6.4.2. Where an email address or phone number is used for event matching, it is normalized and hashed with SHA-256 before it is sent. Hashing limits exposure of the original value in transit, but a provider may match the hash to information it already holds.
6.4.3. A conversion record may also include an event identifier, event time, page URL, IP address, and browser user agent. The event identifier allows browser and server records of the same action to be recognized as one event.
7. SMS, Text Messaging, and Mobile Information
7.1. No Sharing of Mobile Information
7.1.1. No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Information sharing with subcontractors who provide support services, such as customer support platforms and messaging delivery providers, is permitted solely so that we can deliver the messages you asked for and, in the Driver Apps, provide the product analytics and session replay described in Section 4.4.
7.1.2. All of the categories described elsewhere in this Privacy Policy exclude text messaging originator opt-in data and consent. This information will not be shared with any third parties.
7.1.3. Where any other part of this Privacy Policy could be read to permit the sharing or sale of personal information for marketing or promotional purposes, that language does not apply to your mobile phone number, your text messaging opt-in data, or your messaging consent. This Section 7 controls.
7.2. Messages We Send
7.2.1. Vektor TMS sends account security and verification text messages, including one-time passcodes, to users who have a Vektor TMS account and who have provided their mobile number for that purpose. These messages confirm that it is really you signing in or completing a sensitive action on your account.
7.2.2. Message frequency varies and depends on your own activity. Verification messages are sent only when you or someone using your credentials requests a code.
7.2.3. Message and data rates may apply. Your mobile carrier is not liable for delayed or undelivered messages.
7.3. Consent and Opting Out
7.3.1. You provide your mobile number and consent to receive these messages inside the Vektor TMS application when you enable phone verification on your account. Consent to receive text messages is not a condition of purchase.
7.3.2. You can opt out at any time by replying STOP to any message from us. You will receive one confirmation message and then no further texts. Reply HELP for help, or contact us at the address in Section 15.
7.3.3. Opting out of text messages may prevent us from verifying your identity by phone. You can still use other available account security methods.
7.3.4. Full messaging terms are available at vektortms.com/sms-terms.
8. Data Storage and Security
8.1. Data Storage
8.1.1. Data centers and cloud storage providers like AWS and Google Cloud. Driver app analytics and session recordings are hosted by PostHog, Inc. in the United States (Section 4.4).
8.1.2. Retention policies ensure data is deleted or anonymized when no longer needed.
8.2. Security Measures
8.2.1. Encryption, access control, and regular audits.
8.2.2. Notification procedures in case of data breaches.
9. User Rights and Choices
9.1. Accessing, Correcting, and Deleting Personal Data
9.1.1. Access, correct, or delete personal data.
9.1.2. Opt-out of data collection or sharing.
9.1.3. Exercise rights under GDPR or CCPA.
9.1.4. Opt out of the use of your documents for model training, as described in Section 4.3.9.
9.1.5. Object to session replay in the Driver Apps, as described in Section 4.4.7.
9.2. Exercising Rights
9.2.1. Contact us for data access, updates, or deletion requests.
10. International Data Transfers
10.1. Mechanisms
10.1.1. Standard contractual clauses for EU-US data transfers.
10.1.2. Compliance with GDPR, CBPR, and other international standards.
11. Children's Privacy
11.1. Vektor TMS does not knowingly collect data from individuals under 18. If identified, data is deleted immediately, and parents are notified.
12. Links to Other Websites
12.1. Vektor TMS is not responsible for the privacy practices of external websites. Review their policies when leaving our platform.
13. Changes to the Privacy Policy
13.1. Policy Updates
13.1.1. Changes to this policy will be notified via email and platform announcements.
14. Dispute Resolution
14.1. For complaints or disputes, contact us at [email protected]. If unresolved, arbitration may be pursued.
15. Contact Information
15.1. For privacy inquiries, contact: Email: [email protected]
15.2. Veido LLC, 1221 Brickell Ave, Ste 900, Miami, FL 33131, United States. Phone: +1-877-779-1870
16. Limitation of Liability
16.1. Vektor TMS is not liable for indirect damages or unauthorized access to data due to breaches despite stringent security measures.
17. Governing Law and Jurisdiction
17.1. This Privacy Policy is governed by the laws of Veido LLC's jurisdiction, and disputes are resolved in its courts.