Disclosure · September 22, 2026

Provider roles without implied connections.

This page describes provider categories that may process data when enabled. A catalog entry or adapter does not mean a provider is connected for every customer. The authenticated integration workspace is the source of truth for tenant-specific status.

Hosting and delivery

Netlify — web hosting, content delivery, edge and serverless execution, deployment evidence, and related platform logging. Core service provider.

Payments

Stripe — checkout, subscription, payment, invoice, and webhook processing when paid billing is enabled. Payment-card data is handled under Stripe's configured flow, not represented as stored by OrionOS.

Customer-configured providers

Email, telematics, mapping, weather, safety, market-data, accounting, identity, AI, banking, and other connectors are optional. They process data only after an authorized administrator configures the integration and OrionOS records provider validation evidence.

Tenant-specific confirmation

Provider name, purpose, enabled state, validation receipt, relevant data fields, and administrator must be reviewed inside the tenant's integration and evidence workspace. OrionOS does not treat a saved credential, placeholder, or environment variable name as proof of an active connection.

Change and objection requests

Customers seeking advance notice, a named provider inventory, an objection period, or transfer terms must include those requirements in the executed order form and DPA. Contact operations@oriontransportation.us for the customer-specific disclosure.

Disclosure version orionos-subprocessors-2026-09-22-v1. This page does not replace the executed DPA or provider terms.