Privacy Policy and Data Protection Notice

1.1 Scope of Software Architecture. The Company operates strictly as a business-to-business (B2B) enterprise Software-as-a-Service (SaaS) provider specialized in proprietary logistics management, load optimization, supply chain workflow automation, and transportation administration architectures. This Platform acts exclusively as a passive, cloud-based data processor and technical intermediary for industrial supply chain participants.

1.2 Material Scope of Application. This Policy applies directly, universally, and without exception to all personal data, commercial records, non-public financial indicators, and proprietary operational data processed, transmitted, or hosted through our digital interactions, corporate communications, web-based platform infrastructure, mobile applications, browser extensions, desktop applications, application programming interfaces (APIs), onboarding portals, digital data links, and any other proprietary software, tools, cloud-based networks, or digital interfaces we make available, whether accessed via a web browser, a mobile device, an electronic logging device (ELD) integration, or local hardware installation on your device (collectively, together with our primary domain freightsalestms.com and all associated subdomains, underlying databases, and source code, the "Services" or "Platform"). This Policy does not govern the internal operational practices, employment criteria, or commercial service parameters of the independent third-party logistics entities that utilize our infrastructure.

2.1 Scope of Data Subjects and Entities. This Privacy Policy outlines the data handling practices, transparency disclosures, and information management protocols applied by the Company to any corporate entity, business structure, sole proprietorship, partnership, joint venture, or individual accessing, browsing, interacting with, or utilizing the Services. All data subjects, supply chain participants, and external market actors detailed under Section 4 of this Policy are subject to the data processing terms and specific technical categories disclosed herein.

2.2 Data Processing Acknowledgment. By creating a platform account, completing an onboarding packet, clicking or interacting with an automated tracking or onboarding link, integrating third-party server credentials, inputting logistics parameters, or otherwise navigating the Platform, You acknowledge that you have been fully informed of, and understand, the data collection categories, cryptographic encryption protections, international routing, cross-module processing, and specific risk-allocation disclosures detailed throughout this Policy. This Notice operates in conjunction with, but independently from, the Company's master Terms of Service (TOS).

This Policy serves as the definitive disclosure statement regarding the technical architecture, transparency mandates, and safe-harbor standards implemented under United States federal and state data protection frameworks. To ensure clear statutory compliance, this Policy explicitly outlines and regulates the following operational data pillars:

Operational Software Workflow Disclosures: Detailed technical breakdowns of unverified data streams flowing through our core software modules—Customer Relationship Management (CRM), third-party email server integrations requiring user-provided IMAP/SMTP credentials, automated carrier onboarding link delivery integrated with public Federal Motor Carrier Safety Administration (FMCSA) API registries, load execution workflows, and internal team management—including all successor feature extensions or platform add-ons as explicitly categorized and defined under Section 5 and Section 8 of this Policy.

Operational Directives for Data Utilization: Transparent notice regarding the commercial purposes for which data is processed—including internal platform optimization, corporate security audits, and the direct cross-selling of proprietary features, premium updates, or new commercial software solutions as comprehensively disclosed under Section 6 and Section 8 of this Policy.

Zero-Sale Disclosures and Infrastructure Realities: Structural notice outlining that the Company does not sell Broker proprietary lists, alongside the explicit disclosure that the Platform runs on standard commercial third-party cloud infrastructure and utility vendors. The Company does not audit or control the independent security protocols, infrastructure vulnerabilities, or data handling practices of these external infrastructure hosts, and the end-user corporate account holders assume all data routing risks.

SaaS Intermediary Safe Harbor & Third-Party Limitations: Information regarding the technical boundaries of the Platform, specifically the non-verification of Carrier compliance records, the specialized cryptographic encryption of Broker email credentials, and the total administrative detachment of the Company from third-party cargo claims, freight payment collections, or shipping disputes.

Geographic Domicile and Forum Selection Notice: Disclosure that all data processing, regulatory compliance oversight, and legal interpretations are governed by the statutory frameworks of the State of Texas, United States, establishing the state and federal courts of Texas as the exclusive judicial venue for any information security or data privacy litigation, operating strictly without regard to conflict of law principles.

Cross-Border Data Transfer Disclosures: Clear administrative notice concerning international data processing, remote software engineering nodes, and cross-border data flows, defining corporate oversight parameters regardless of the physical processing location.

Fintech & Financial Data Segregation: Notice regarding the systematic partitioning of financial billing data, whereby all subscription processing is entirely managed by independent, PCI-DSS compliant financial technology vendors (Stripe) to isolate financial data risks, preventing the database retention of consumer financial accounts as outlined under Section 5.5 and 5.6.

Data Retention, Spoliation Prevention, and Litigation Holds: Disclosure of the internal protocols governing how long information is stored data lifecycles, the technical archiving of system logs for post-termination legal defense, and the preservation of transactional metadata to assist in the defense against systemic freight fraud, operating under the formal retention and security parameters disclosed under Section 7 of this Policy.

4.1 Categories of Data Subjects and Interacting Entities. This Policy outlines the information management, storage, and processing protocols applied to all data subjects, corporate bodies, and commercial representatives interacting with the Platform. These disclosures universally cover all currently deployed services and any future software extensions, platform add-ons, API links, or successor modules. The categories of monitored or hosted data entities include:

Freight Brokers ("Brokers"): Third-party logistics providers operating under federal property broker authorities, including their administrative personnel, corporate agents, and sub-agents who utilize the Platform to host internal commercial databases and manage operational workflows.

Motor Carriers ("Carriers"): Transport operators, fleet owners, and owner-operators operating under active transit mandates (such as USDOT and MC registries) whose corporate infrastructure, vehicle logging records, and administrative identifiers are hosted on the Services.

Shippers, Consignors, and Consignees ("Shippers"): Industrial cargo owners, manufacturers, and distribution agents whose transactional parameters, delivery addresses, and operational requirements are inputted into the cloud databases.

Third-Party Dispatchers ("Dispatchers"): Independent operational agents or dispatch agencies utilizing administrative access privileges to coordinate vehicle routing and schedule commercial loads on behalf of Carriers or Brokers.

Commercial Drivers ("Drivers"): Individual operators of commercial motor vehicles (including both holders of Commercial Driver's Licenses [CDL] and operators of non-CDL commercial vehicles) whose personal, vehicular, operational, and credentialed data—including, without limitation, driver's licenses, license plates, Vehicle Identification Numbers (VIN #), and truck or trailer registrations—is inputted into the Platform by Brokers, Carriers, or Dispatchers. All such data is hosted strictly as static digital records for administrative cloud storage at the direction of the corporate account holder, under the parameters disclosed in Section 5.3.

The Platform does not collect, request, or store driver medical cards, physical examination reports, or personal health documentation. Furthermore, the Platform applies basic verification protocols linked to public registries to grant portal access and does not perform active biometric scanning, facial recognition, or identity extraction. In the event that advanced verification or mobile device track-and-trace utilities are integrated into the future architecture of the Services, such data flows shall depend entirely on the Driver's physical device and affirmative actions, as outlined in Section 5.7.

FREIGHT SALES TMS LLC disclaims any and all direct, statutory, or informational liability for the storage, transmission, or unauthorized interception of such records. The entire informational risk regarding the upload, validation, corporate clearance, and potential data breach of these documents or the misuse of planned tracking features is assumed exclusively by the Broker, Carrier, or specific entity that authorizes the data input.

Factoring and Financial Entities ("Factoring Companies"): Financial technology providers, asset-based lenders, or factoring institutions whose bank routing data, commercial financing parameters, and Notices of Assignment (NOA) are archived within the transaction histories.

Third-Party Service Providers and Vendors ("Service Providers"): External software platforms, integrations, or operational vendors connected via API or added manually by a User, including tracking services, insurance agencies, Electronic Logging Device (ELD) networks, fuel card utilities, and compliance databases.

Authorized Users ("Users"): Corporate employees, administrative representatives, or independent contractors accessing the Platform under an active enterprise subscription.

4.2 Technical Classification of Processing Roles: Data Processor vs. Data Controller. To establish transparent regulatory compliance under United States federal and state data privacy frameworks, the data processing roles are structurally defined as follows:

The Company as a Data Processor: When FREIGHT SALES TMS LLC hosts, organizes, syncs, or stores Personal Data, Commercial Data, or Operational Data within its infrastructure, the Company acts strictly and exclusively as a Data Processor (or "Service Provider"). The Platform operates as a passive technological intermediary providing neutral cloud tools. The Company exercises no discretionary control over what specific data fields are uploaded, how long logs are maintained, or how information is leveraged in the market.

The Subscriber as the Data Controller: The active purchasing enterprise (e.g., the Freight Broker or primary corporate account holder) acts strictly as the independent Data Controller (or "Business" entity) for all data imported, manually inputted, or generated within their software partition. The Data Controller retains sole responsibility for establishing its own independent privacy notices, commercial disclosures, and internal data security parameters.

4.3 Regulatory Disclosures and Informational Risk Allocation. Because FREIGHT SALES TMS LLC does not audit, curate, or verify the legitimacy of data uploaded by its multi-tenant network, the following transparency rules govern the Services:

Individual Privacy Rights Requests: If any individual (including an employee of a Shipper, a Factoring Company, or a Driver) contacts the Company to exercise statutory privacy rights—such as requests to access, rectify, or delete personal data—the Company will redirect such inquiries directly to the governing corporate account holder (the Data Controller). The Company is technically restricted from altering live transactional databases without the explicit administrative authorization of the supervising Data Controller.

Data Input Declarations: Data Controllers are solely responsible for ensuring they possess all necessary legal permissions, driver consents, and corporate authorizations required under state and federal law to transmit multi-party logistics data to the Platform.

Exclusion of Data Liability for Inter-Module Activity: FREIGHT SALES TMS LLC explicitly discloses that the Platform operates as a passive technological infrastructure, and the Company disclaims any and all regulatory, statutory, informational, or administrative liability arising from a corporate customer's internal mismanagement, unauthorized data entry, unlawful database extraction, or faulty data maintenance. Furthermore, the User acknowledges that cloud-based architectures are subject to systemic platform anomalies, software glitches, API transmission latency, or automated data cross-over caused by software errors or user negligence, operating under the secure data boundaries detailed in Section 5.

If a Broker, Carrier, Dispatcher, or User exposes a Factoring Company's sensitive banking details, violates an independent non-disclosure agreement with a Shipper, mismanages an external Service Provider's API access token, or inputs data that facilitates systemic double-brokering fraud, cargo theft, or transit delays, such User assumes absolute, sole, and independent operational and financial liability for the incident. The Company, its owners, and its technical affiliates maintain zero administrative involvement in these multi-party transactional disputes, and the supervising corporate account holder retains full accountability for any resulting regulatory investigations, cargo claims, or information security liabilities.

To maintain operational transparency, this section outlines the specific categories of personal, commercial, and technical data fields processed across the Platform's infrastructure. The Company collects this data either directly from User inputs, automated public API synchronization, or background technical logging.

5.1 CRM Module (Customer Relationship Management Data). The CRM module acts as an administrative database repository for unverified commercial lead information uploaded manually or via bulk document imports by the Broker. The data fields processed within this environment include, without limitation: Corporate Contact Identifiers — full names of customer representatives, business email addresses, corporate telephone extensions, job titles, and physical corporate brick-and-mortar addresses; and Commercial Lane Profiles — historical freight routing data, origin and destination points, customer freight profiles, equipment type preferences, and interaction notes compiled manually by individual logistics personnel.

5.2 EMAIL Module (Third-Party Server Integration Data). To facilitate centralized inbound and outbound communication tracking within the cloud workspace, the Platform establishes a technical link with the Broker's external third-party email servers. The fields processed under this synchronization include, without limitation: Authentication and Configuration Parameters — user-provided corporate email addresses, alphanumeric user identifiers, network port properties (including Simple Mail Transfer Protocol [SMTP] and Internet Message Access Protocol [IMAP] configurations), and associated server connection credentials. To facilitate centralized tracking, all user-provided integration credentials are automatically isolated and stored using industry-standard, high-grade cryptographic encryption algorithms and secure key management practices within our baseline cloud architecture. Also processed: Communication Metadata and Assets — inbound and outbound message bodies, subject lines, chronological timestamps, routing logs, contact headers, junk/spam folders, and any commercial documentation or load assets attached to integrated email threads.

5.3 MY CARRIERS Module (Automated Onboarding & Fleet Operational Data). The MY CARRIERS module serves as a digital transit pipeline to automate the distribution of onboarding links directly to the communication channels recorded within federal databases, and to organize data fields provided directly by responding Carriers. This inventory includes, without limitation: Public Regulatory Identifiers — Motor Carrier (MC) numbers, United States Department of Transportation (USDOT) registration numbers, and public safety rating metadata retrieved via automated FMCSA API scripts; Asset and Equipment Specifications — commercial vehicle identification profiles, Vehicle Identification Numbers (VIN #), truck and trailer license plate characters, equipment categories (e.g., dry vans, flatbeds, reefers), and active equipment dimensions; Carrier Credential Documentation — static digital copies of driver's licenses (including CDL and non-CDL credentials), corporate driver rosters, Certificates of Insurance (COI) encompassing cargo and auto liability policies, and specialized transit, hazardous materials, or operating permits required for commercial transportation compliance; and Financial and Factoring Parameters — Employer Identification Numbers (EIN/Form W-9), corporate banking details, bank routing figures, and Notices of Assignment (NOA) alongside corporate contact profiles linked to third-party Factoring Companies.

5.4 ORDERS Module (Load Execution & Transactional Workflow Data). The ORDERS module hosts active transactional records necessary to coordinate logistics workflows and document multi-party communication events. The compiled data elements include, without limitation: Transactional Logistics Documentation — digital copies and field extractions of Rate Confirmations (rate cons), Bills of Lading (BOL), Proof of Delivery (POD) receipts, commercial invoices, and lumper fee reports; and Execution Metadata — alphanumeric load identification numbers, load valuation metrics, contracted tariff pricing, pickup and delivery schedules, and specific handling instructions.

5.5 MY TEAM Module (Internal Management & Payment Processing Disclosures). The MY TEAM module monitors administrative software usage and partitions billing protocols to secure commercial interactions. The data subsets processed include, without limitation: Internal Personnel Profiles — corporate names, administrative roles, internal access privilege levels, encrypted password hashes, and chronological user audit trails (system access logs); and FinTech Segregation Parameters — enterprise billing names, billing addresses, and subscription details. The Platform explicitly discloses that all raw credit card fields, bank account numbers, and transaction authorizations are processed directly by Stripe via embedded secure fields. No raw payment instrument variables are hosted, captured, or transmitted through the primary databases of FREIGHT SALES TMS LLC.

5.6 Core Restriction on Consumer and Retail Sensitive Personal Information. FREIGHT SALES TMS LLC explicitly discloses that the Platform does not collect, process, or store protected, retail-grade consumer sensitive personal information. The infrastructure is strictly engineered to reject and exclude retail consumer data datasets, including, without limitation, individual Social Security Numbers (SSN), personal consumer credit scores, or private consumer medical health records. The only data categories processed by the Platform that may be classified as sensitive under applicable statutes are the regulatory, identity, and credentialed identifiers of commercial Drivers (such as Driver's Licenses and CDL records) as explicitly disclosed under Sections 4.1 and 5.3.

By utilizing the MY CARRIERS module, onboarding through the Platform, or completing an operational registration link, the Carrier explicitly represents, warrants, and guarantees that it has obtained prior, express, and lawful consent from its Drivers to upload, host, and transmit such data to the Platform. Furthermore, the Carrier and Driver acknowledge that the Platform is intentionally designed to disclose and share this commercial driver documentation directly with the participating Freight Brokers with whom they operate or coordinate transit loads. All such transmission operates under an automated data routing environment explicitly directed and authorized by the participating Users. FREIGHT SALES TMS LLC acts solely as a passive technological processor for these B2B interactions, and the downstream Freight Broker assumes independent Data Controller responsibilities for the data received within their respective software partition.

5.7 Future Successor Modules, Telematics, and Driver-Dependent Track-and-Trace Disclosures. In anticipation of platform scalability, software extensions, and the release of subsequent functional tools, the Platform's technical architecture is engineered to support prospective operational datasets. The Company discloses that advanced cargo track-and-trace geolocation utilities, mobile-based driver tracking features, and Electronic Logging Device (ELD) telematics data synchronizations are structurally planned for short-to-medium-term integration but may not be fully deployed within the current software iteration. To the extent that these tracking tools or other third-party integrations—including digital load boards, Hours of Service (HOS) data streams, and automated spot-market quoting engines—are deployed, the Platform will process the respective API payloads, geolocation telemetry, technical datasets, and operational logs under the following strict safe-harbor constraints:

Driver-Controlled Telemetry Streams: Any future geolocation tracking features or telematics data syncs will process data derived strictly from the active integrations and hardware configurations enabled by the Driver. The Platform does not execute background location tracking independent of the permissions granted through the Driver's physical device or linked ELD provider.

Technical Limits of Location Data: The Platform records geolocation datasets solely to provide automated transit updates to the governing Freight Broker during active shipment parameters. The Company does not process, store, or monitor location telemetry outside of active commercial logistics workflows, and data processing ceases upon the termination or manual deactivation of the tracking link by the Driver or Carrier.

Integration Passivity Disclosures: Telematics and Hours of Service (HOS) payloads are processed as raw, unedited data streams. The Company does not perform data validation, compliance monitoring, or safety enforcement auditing on these tracking streams, and all such data is managed under the same passive data processor rules established throughout this Policy.

To ensure regulatory compliance under United States federal and state data protection frameworks, this section details the exclusive business purposes for which the Platform processes data, alongside the strict administrative boundaries governing how information is shared within our multi-tenant SaaS architecture.

6.1 Permitted Business Purposes for Data Utilization. FREIGHT SALES TMS LLC utilizes Personal Data, Commercial Data, and Operational Data strictly to execute core administrative functionalities, including, without limitation: Platform Execution and Technical Maintenance — delivering, operating, syncing, and updating the current five (5) core operational modules (CRM, EMAIL, MY CARRIERS, ORDERS, MY TEAM) and all planned successor integrations; Operational Automation — executing the automated delivery of onboarding links via the FMCSA API, syncing communication folders, and rendering static transaction histories; Systemic Optimization — monitoring system metrics, diagnosing server glitches, auditing API data latency, and conducting cloud database evaluations to enhance platform performance; and FinTech Transaction Security — validating subscription processing and corporate data records to protect the software infrastructure against systematic corporate security risks.

6.2 Internal Marketing, Commercial Scaling, and Cross-Selling Notice. The Company explicitly discloses that it reserves the right to leverage the corporate contact profiles, business email addresses, and interaction history of both Freight Brokers and Motor Carriers gathered through the Services for internal commercial scaling. Direct Cross-Selling: the Company may use this data to market, promote, distribute, and sell proprietary successor software solutions, premium software features, financial administration updates, or additional digital logistics utilities directly to existing Users. Opt-Out Mechanisms: all internal marketing communications distributed under this provision will contain standardized, automated opt-out (unsubscribe) mechanisms to ensure strict compliance with federal electronic communication standards.

6.3 Third-Party Disclosures and Commercial Zero-Sale Mandates. To maximize the commercial security of our enterprise clients, FREIGHT SALES TMS LLC operates under a strict, non-negotiable data segregation policy: Absolute Zero-Sale of Broker Data — the Company DOES NOT sell, rent, license, trade, or lease proprietary commercial lists, customer directories, shipper leads, or email records uploaded by Freight Brokers into the CRM or EMAIL modules to any third-party marketing companies, external lead brokers, or independent software competitors. Standard Infrastructure Disclosures — the Platform shares data exclusively with essential commercial third-party infrastructure and utility vendors necessary to support cloud deployment (e.g., standard hosting infrastructure, Cloudflare security routing, and the Stripe financial payment gateway); all such routing is performed strictly under standard commercial data processing agreements, and external vendors are technically restricted from accessing or utilizing the unencrypted databases for independent marketing purposes. Consented Cross-Module Sharing — by design, the information uploaded by a Carrier into the MY CARRIERS workspace is intentionally disclosed and made accessible to the specific Freight Broker that initiated the automated onboarding link, establishing an automated data routing environment explicitly directed and authorized by the participating Users.

To satisfy statutory transparency mandates under applicable federal and state privacy frameworks, this section outlines the current information security practices, operational data lifecycles, and standard encryption methods implemented across the Platform.

7.1 Data Retention Lifecycles and Operational Necessity. FREIGHT SALES TMS LLC retains Personal Data, Commercial Data, and Operational Data exclusively for the duration necessary to fulfill the legitimate business purposes outlined throughout this Policy. This processing includes supporting active corporate software subscriptions, executing automated FMCSA API onboarding workflows, and archiving load transaction histories. End-user databases, CRM leads, and communication arrays remain active within the cloud infrastructure until: the primary corporate account holder initiates an administrative platform cancellation or deletion request; or the data is determined by the Company to no longer possess commercial or administrative utility for the execution of the Services.

7.2 Litigation Holds, Spoliation Prevention, and Fraud Mitigation Audits. Notwithstanding any account termination or deletion requests, the Company explicitly discloses that it reserves the right to maintain historical transaction metadata, system access trails, encrypted communication parameters, and verified regulatory logs in an archived state. This historical retention is executed strictly to: comply with Statutory Mandates (adhere to federal, state, or Department of Transportation (DOT) logistical record-keeping frameworks); prevent Information Spoliation (preserve critical system metadata and interaction trails required to defend FREIGHT SALES TMS LLC, its owners, and its infrastructure partners against potential future civil lawsuits, cargo damage claims, or contractual breaches); and Mitigate Freight Fraud (maintain an unalterable audit trail (system logs) capable of assisting federal regulatory authorities, law enforcement, or insurance investigation boards in tracking identity theft, double-brokering schemes, and systemic supply chain scams).

7.3 Commercially Reasonable Security and Standard Encryption Disclosures. The Company deploys standard, commercially reasonable administrative, logical, and technical infrastructure safeguards designed to protect B2B logistics databases against unauthorized access, loss, or alteration. These systemic protections are tailored for early-to-mid-stage commercial applications and include: Advanced Credential Protection — securing external mail server integration credentials and sensitive access assets disclosed under Section 5.2 through advanced, multi-tenant database partitioning and commercial-grade encryption-at-rest protocols, restricting system-level access exclusively to authorized automated execution workflows; Infrastructure Edge Protection — utilizing standard commercial web-defense networks and basic proxy routing utilities (such as Cloudflare or equivalent infrastructure vendors) to mitigate baseline external script injections and automated indexing; and FinTech Segregation Parameters — partitioning corporate billing functions through embedded secure fields to ensure that zero raw payment variables are compiled, transmitted, or hosted on the core computing nodes of FREIGHT SALES TMS LLC, as disclosed under Section 5.5.

7.4 Technical Inherent Risk Disclosures and Absolute Waiver of Security Guarantees. The User explicitly acknowledges that while the Company deploys industry-standard administrative, technical, and logical safeguards, no digital architecture or cloud-based data transmission over the internet can be guaranteed as completely absolute or impenetrable. FREIGHT SALES TMS LLC provides no warranty, absolute guarantee, or statutory covenant that hosted data, encrypted credentials, or operational logs will remain entirely immune to highly sophisticated cyber-espionage, zero-day infrastructure exploits, hardware failures, targeted third-party exfiltration, or force majeure events. The Platform operates strictly as a neutral technological conduit. By interacting with the Services, integrating external email servers, or submitting driver documentation, the User explicitly acknowledges these technical boundaries and assumes the residual cybersecurity and operational risks inherently associated with third-party digital cloud environments.

8.1 Scope of Data Sharing and Automated Disclosure. This Section outlines the transparency parameters applied to data streams managed through the "MY CARRIERS" module. By interacting with an automated carrier onboarding link or uploading documentation into the Platform, Motor Carriers and associated third-party participants acknowledge that the Platform is technically engineered to transmit and disclose all submitted compliance records and operational assets directly to the specific Freight Broker that initiated the software interaction link.

8.2 Representation of Lawful Driver Consent. When a Motor Carrier or independent dispatch agency inputs individual driver personal identifiers into the Platform—including driver's licenses, CDL indicators, and vehicular data—the transmitting entity acts as the primary data compiler and represents that it has obtained all necessary prior permissions and lawful consents from its Drivers to upload and host such data within the Platform's cloud databases under the processing parameters disclosed in Section 5.6.

8.3 Limitations of Platform Data Auditing. FREIGHT SALES TMS LLC operates strictly as a passive data processor regarding multi-party logistics information. The Company does not independently verify, audit, or monitor the accuracy, active status, or regulatory validity of public FMCSA registries, safety profiles, or insurance credentials hosted within individual customer software partitions.

8.4 Inter-Platform Service Provider Data Transfers. For external applications, Electronic Logging Device (ELD) networks, or compliance databases linked via API to the Platform, data processing is governed strictly by the respective interoperability tokens. The Platform processes these external payloads solely to execute requested system syncs and is not responsible for the independent data handling practices, security protocols, or processing vulnerabilities of those external third-party hosts.

To maintain compliance with evolving regional statutes across the United States, this section outlines how state-level data privacy legislation interacts with the Platform's operations, establishes data erasure protocols, and defines the formal pathways for corporate inquiries.

9.1 United States Federal and Multi-State Privacy Frameworks Compliance. The Company provides its Services exclusively to commercial enterprises, logistics corporations, and business professionals. It does not actively market to, engage with, or intentionally collect consumer-grade information from individual retail consumers. This Policy is designed to comply with all applicable federal laws of the United States and the specific data protection frameworks established across all individual U.S. states and territories (including the 48 contiguous states, Alaska, and Hawaii). To the extent that regional state-level data privacy statutes—including, without limitation, the Texas Data Privacy and Security Act (TDPSA), the California Consumer Privacy Act as amended by the California Privacy Rights Act (CCPA/CPRA), the Virginia Consumer Data Protection Act (VCDPA), the Colorado Privacy Act (CPA), and all equivalent or successor comprehensive state privacy laws—apply to professional identifiers or commercial variables processed herein, the Company operates in strict compliance with the statutory provisions governing Business-to-Business (B2B) data processing. All personal data, commercial indicators, and logistics metrics routed through the Platform are processed solely within this professional, commercial context. Accordingly, data subject rights (such as the right to access, rectify, delete, or opt-out) shall be governed, limited, and executed strictly in accordance with the regulatory parameters and B2B exemptions established for commercial data streams under applicable federal and state laws.

9.2 Commercial Data Deletion and Erasure Request Protocols. While the Services operate under business-to-business frameworks, the Company provides formal pathways for Users and entities to request the removal or deletion of their specific professional identifiers and corporate data profiles. All deletion requests must be submitted formally to the dedicated email address specified in Section 9.4. Upon receipt of a valid commercial data erasure request, the Company will evaluate the database variables under the following technical and legal constraints:

The Processor Restraint: If the data deletion request is submitted by an individual whose data was uploaded by a primary subscriber (e.g., a Driver whose license photo was uploaded by a Carrier, or a Shipper contact added by a Broker), the Company will decline to execute the deletion directly and will forward the request to the respective Data Controller. The Company cannot modify or purge data partitions without the explicit administrative authorization of the managing subscriber.

Statutory and Regulatory Retention Overrides: The Company will permanently purge active files, email synchronization logs, and profile records from the live production servers within a commercially reasonable timeframe. However, the Company will NOT delete, and is legally permitted to retain, any data subsets, metadata, or historical transaction logs that are required to: comply with federal or state record-keeping mandates, including Department of Transportation (DOT) or Federal Motor Carrier Safety Administration (FMCSA) operational rules; maintain financial transaction records linked to subscription processing for corporate taxation audits; and fulfill the Litigation Hold and Spoliation Prevention requirements detailed under Section 7.2 to support corporate defense against potential civil claims, contract breaches, double-brokering fraud, or cargo theft.

9.3 Exercise of Commercial Administrative Controls. To the extent that any applicable state statute grants rights to corporate representatives regarding their professional identifiers hosted on the Platform, such inquiries must follow these guidelines: Requests From Corporate Personnel — if an employee of a Broker or a Carrier wishes to access or update their specific corporate profile parameters, they must execute those changes directly through the administrative controls provided in the MY TEAM module, or contact their respective corporate account administrator. Redirecting Third-Party Inquiries — as disclosed under Section 4.2, the Company acts strictly as a passive Data Processor; any data rights requests submitted by external drivers, factoring company representatives, or shippers will be redirected to the specific primary subscriber (the Data Controller) who retains administrative authority over that data partition.

9.4 Formal Communication and Corporate Inquiries. For any regulatory transparency questions, technical inquiries regarding the data erasure protocols, or state-specific disclosure requests, Users may contact the Company's dedicated policy administration office through either of the following official communication channels: Dedicated Legal & Privacy Email — [email protected]. Official Corporate Postal Address — FREIGHT SALES TMS LLC, Attn: Privacy & Compliance Department, 5900 Balcones Dr Ste 100, Austin, TX 78731, United States.

Communications sent to unmonitored administrative support queues, live chat windows, or separate customer service channels will not be recognized as formal regulatory or privacy notices under this Policy. The Company will review and respond to valid commercial inquiries within the statutory timeframes mandated by the governing state of Texas or applicable United States federal rules.