Orion TransportationOrionOS
This notice covers the OrionOS subscription platform, Orion Transportation portal features delivered through OrionOS, public onboarding, TrackLink, scheduling links, support, and related customer-facing services. It is effective September 2, 2026.
The exact categories depend on the products, portals, integrations, and devices a customer enables.
Names, business contact details, organization, role, login and MFA state, permissions, acceptance receipts, license records, and account-security events.
Used for: authentication, tenant access, administration, licensing, fraud prevention, audit, and support.
Loads, stops, appointments, facilities, parties, messages, documents, inventory, quotes, rates, invoices, claims, equipment, maintenance, and workflow history.
Used for: transportation, warehouse, dock, billing, evidence, reporting, collaboration, and customer-directed integrations.
Driver and employee records, qualification and training data, licenses, safety and maintenance records, assignments, and customer-entered personnel documents.
Used for: customer-directed employment administration, safety, training, compliance workflows, and access control. Customers must limit collection to lawful, necessary data.
Precise or approximate location, timestamps, routes, geofences, device identifiers, sensor readings, ELD/telematics events, and proof-of-delivery signals when enabled.
Used for: live visibility, ETA, route and weather risk, arrival/departure, safety, cargo security, maintenance, and customer communication.
Email and message content, support tickets, notification preferences, call or delivery receipts, feedback, and attachments.
Used for: requested communications, case handling, service delivery, audit, suppression, and dispute resolution.
IP-derived security hashes, browser/device data, logs, usage and cost counters, incident evidence, order and subscription identifiers, and provider payment status. OrionOS does not need full card numbers from its payment provider.
Used for: security, reliability, metering, billing reconciliation, abuse prevention, and service improvement.
Sources include the individual, the subscribing customer and its authorized users, carriers/brokers/shippers and other shipment participants, enabled devices and integrations, service providers, and public or licensed sources selected for a product. OrionOS does not state that it sells personal information. It does not use personal information for cross-context behavioral advertising in the current service. Submit an opt-out request below if you want this position reviewed for your relationship and jurisdiction.
Access is limited by customer configuration, purpose, role, relationship, and provider availability.
Netlify hosts the site, functions, and Blob-backed application stores. Security, monitoring, and recovery vendors may process limited technical or encrypted data when configured.
Stripe may process checkout and subscription events. Postmark, Google/Gmail, Twilio, or another configured provider may process the contact and message data needed to deliver email, voice, or SMS.
Configured map, weather, carrier identity, ELD/telematics, load-board, accounting, and transportation providers receive the minimum request fields needed for the enabled workflow. Provider availability and terms vary.
Authorized users and shipment participants may receive records through portals, scheduling links, TrackLink, documents, notifications, exports, or customer-directed sharing. Public or token links are limited to the data and life cycle of that link.
Browser or device permission is required before direct location capture. Customers must provide legally required notices and obtain consent or another valid authority before tracking people or equipment. Turning off permission stops new browser capture but does not erase previously retained evidence.
Customer administrators choose users, roles, integrations, retention inputs, tracking links, devices, and operational sharing. Users should contact their organization first for customer-controlled records; Orion will route verified requests to the appropriate customer when necessary.
Documents may contain sensitive personal, financial, safety, or regulated data. Upload only authorized, necessary records. Scan, quarantine, legal-hold, authorization, retention, and safe-download controls can delay or block availability.
Freight, billing, support, personnel, compliance, device, license, and audit records are retained while needed for the service and then reviewed under the customer contract, configured policy, applicable legal requirements, disputes, and legal holds. OrionOS does not promise automatic deletion where the workflow has not produced a verified disposition receipt.
Deletion may be denied, limited, anonymized, or delayed where identity cannot be verified, a customer controls the record, security or legal evidence must be preserved, or law and contract require retention. Backups age out under their own retention schedule after any hold or recovery need ends.
Depending on your location and relationship, you may be able to request access, correction, deletion, portability, an opt-out review, withdrawal of consent, or an appeal. Submitting a request does not guarantee a particular result; Orion first verifies identity, scope, the controlling organization, and applicable exceptions.
You can also email operations@oriontransportation.us. Do not send government IDs, passwords, medical files, or full financial numbers by ordinary email or in this form.
OrionOS uses role and relationship checks, tenant scoping, encryption for defined sensitive stores and recovery artifacts, access/session controls, evidence hashes, and provider-delivery receipts. No system can eliminate all risk. Data may be processed in the United States and in provider regions used by enabled services, subject to the customer agreement and provider terms.
Material incidents are investigated and notices are provided as required by applicable law and agreement. Security reports should use the contact in security.txt.
Use one request for one person. Orion will not disclose personal data through this public form.
Effective September 2, 2026 · Notice version orionos-privacy-2026-09-02-v2. Orion may update this notice as products, providers, or law change and will identify the current version and effective date. This product notice should be reviewed with qualified counsel for the jurisdictions and customer use cases that apply.