FreightAxiom

Privacy

Contact
Privacy Policy

Privacy built around freight operations.

FreightAxiom is designed to support brokers, carriers, and shippers through role-based visibility, assigned-load workflows, tracking controls, document management, and human-controlled AI.

Effective date: June 8, 2026. This page is intended for beta-stage informational purposes and may be updated as FreightAxiom evolves.

Privacy principles

Right data. Right role. Right workflow.

FreightAxiom is designed to keep operational information aligned with broker control, carrier assignment, shipper visibility, and document workflows.

Broker-controlled access
Role-based visibility
Assigned-load tracking
Human-controlled AI

Operational data

Tracking data

Document workflows

01

Information We May Collect

FreightAxiom may collect information needed to provide freight operations workflows during private beta.

Account and invite information

Broker, carrier, and shipper profile details

Load, shipment, pickup, delivery, and status information

Carrier document and compliance workflow data

Uploaded operational documents such as BOLs, PODs, invoices, insurance, W-9s, and carrier agreements

Tracking and location-related information for assigned loads when tracking is enabled

Notifications, operational events, and product feedback

02

How Information Is Used

Information is used to support broker operations, carrier workflows, shipper visibility, platform performance, and beta feedback.

Create and manage freight loads

Support carrier and shipper onboarding

Enable live tracking and shipment visibility

Manage document requests and uploads

Provide notifications and operational alerts

Improve FreightAxiom features and workflows

Support beta testing, troubleshooting, and user feedback

03

Role-Based Visibility

FreightAxiom is designed around broker control and role-based visibility.

Brokers manage their organization, loads, partners, documents, and operational data

Carriers should only see assigned loads and related workflows

Shippers should only see assigned shipment visibility and relevant updates

Access may vary depending on account role, assignment, and beta configuration

04

Tracking and Location Data

FreightAxiom may use location-related data to support live tracking, ETA awareness, shipment health, and broker visibility.

Tracking is intended to apply to assigned loads

Carriers may have start and stop tracking controls

Tracking data may be visible to authorized brokers and relevant shipment participants

Tracking information may be used to generate alerts, status awareness, and operational intelligence

05

Documents and Files

FreightAxiom supports operational document workflows for brokers, carriers, and shippers.

Uploaded documents may include freight, compliance, and delivery materials

Documents may be linked to loads, carriers, shippers, or users

Document access is intended to follow role-based permissions

Do not upload documents you are not authorized to share

06

Beta-Stage Notice

FreightAxiom is currently in private beta, and the product, policies, workflows, and security documentation may continue to evolve.

Features may change during beta

Access rules and workflows may be refined

Beta participants may be asked for feedback

This privacy page may be updated as FreightAxiom matures

Your choices and questions.

If you have questions about FreightAxiom privacy, beta participation, document workflows, tracking, or account access, contact FreightAxiom directly at jfarmer@freightaxiom.ai.

Contact for privacy

Email jfarmer@freightaxiom.ai for privacy-related questions during private beta.

Important beta-stage note

This privacy page is intended to describe FreightAxiom’s current beta-stage privacy approach in plain language. It is not a substitute for formal legal advice. As FreightAxiom prepares for broader launch, legal policies, data practices, and platform documentation may be reviewed and updated.

Less Chaos. More Freight.

Questions about privacy or beta access?

Contact FreightAxiom directly with privacy, security, beta, or platform questions.