Your freight data is your business. Here's how it's protected, in plain terms.
Or email it to security@ortely.com
Every organization's data is isolated at the database layer — the boundary is enforced by the database itself, not only by application code. One customer's shipments, parties, rates, and documents are never reachable from another customer's workspace. Each workspace lives behind its own authenticated subdomain.
Data is encrypted in transit with Transport Layer Security (TLS) on every connection — to the app, to the API, and between our services. Data at rest is encrypted with the Advanced Encryption Standard (AES). There is no unencrypted path between you and your data.
Customer data is stored and processed in the United States. Enterprise customers with a specific regional requirement can request it as part of their contract — talk to us before you sign.
Your shipments, emails, documents, and voice are never used to train a model — ours or our vendors' — and are not shared beyond processing the action you asked for. Every AI action is metered per organization and stays within your plan's quota. The model and speech vendors behind these features are named on our Sub-processors page, along with the contractual no-training commitment each one is held to. The full breakdown of what the AI does and doesn't do is on the What our AI does page.
Every state-changing action — who did what, when — is recorded in an audit log scoped to your organization. Admins can review it in Settings. It's there for your own accountability and incident review, not just ours.
Billing runs through Stripe. We never see or store your card number — card entry and stored payment methods are handled entirely by Stripe's PCI-compliant components. We hold a Stripe customer reference, nothing sensitive.
We publish every third party that processes customer data on our behalf — what they do and where they run — and we notify customers before a new one goes live. The current list is on the Sub-processors page.
Found something? Our Responsible Disclosure Policy covers scope, safe harbor, and what to expect. Email security@ortely.com — we acknowledge reports within three business days and keep you updated through resolution. A machine-readable contact is also served at /.well-known/security.txt. We don't pursue researchers acting in good faith.
Every organization's data is isolated at the database layer — the boundary is enforced by the database itself, not only by application code. One customer's shipments, parties, rates, and documents are never reachable from another customer's workspace. Each workspace lives behind its own authenticated subdomain.
Data is encrypted in transit with Transport Layer Security (TLS) on every connection — to the app, to the API, and between our services. Data at rest is encrypted with the Advanced Encryption Standard (AES). There is no unencrypted path between you and your data.
Customer data is stored and processed in the United States. Enterprise customers with a specific regional requirement can request it as part of their contract — talk to us before you sign.
Your shipments, emails, documents, and voice are never used to train a model — ours or our vendors' — and are not shared beyond processing the action you asked for. Every AI action is metered per organization and stays within your plan's quota. The model and speech vendors behind these features are named on our Sub-processors page, along with the contractual no-training commitment each one is held to. The full breakdown of what the AI does and doesn't do is on the What our AI does page.
Every state-changing action — who did what, when — is recorded in an audit log scoped to your organization. Admins can review it in Settings. It's there for your own accountability and incident review, not just ours.
Billing runs through Stripe. We never see or store your card number — card entry and stored payment methods are handled entirely by Stripe's PCI-compliant components. We hold a Stripe customer reference, nothing sensitive.
We publish every third party that processes customer data on our behalf — what they do and where they run — and we notify customers before a new one goes live. The current list is on the Sub-processors page.
Found something? Our Responsible Disclosure Policy covers scope, safe harbor, and what to expect. Email security@ortely.com — we acknowledge reports within three business days and keep you updated through resolution. A machine-readable contact is also served at /.well-known/security.txt. We don't pursue researchers acting in good faith.