Fair Use Policy
Version 2.0 · Last updated 22 September 2026
The short version
There is no fee per shipment and no per-seat charge. A few things do carry a baseline, because they cost us money per use: AI document reading, routing lookups and document storage. If your usage runs past one of them we come to you and agree what to do, before anything is charged. You can always export your own data.
1. Purpose and scope
This Fair Use Policy defines what Orin Technologies B.V. ("Orin", "we") considers reasonable use of the Orin Transport Planner and all related applications, APIs and AI features (the "Service"). It forms an integral and binding part of the Orin Terms and Conditions and applies to every plan, trial, account and user.
It exists because a flat per-vehicle price has to cover a normal operation, and a few features cost us money each time they are used. Rather than metering everything, we state where the edges are and talk to anyone who reaches one.
Changes follow the same clock as the Terms and Conditions: a change that reduces included usage is announced to account administrators at least 30 days before it takes effect, and a Customer who does not accept it may cancel before that date without penalty. Clarifications that do not reduce anything take effect when published.
2. Subscription model and what "included" means
Orin is priced as a base amount plus an amount per active vehicle. "Included" means included for the normal day-to-day operations of the business on the account. It does not mean technically unmetered.
Vehicle count is how we price, not how we define normal use. A forwarder with no fleet of its own has few or no active vehicles and a real order volume, and that is an ordinary Orin account rather than an edge case: for an account like that, normal use is judged on the size of the operation rather than on a vehicle number. If your shape does not fit the baselines below, that is a conversation about the right plan, not a breach.
3. Fair-use baselines
These are the baselines we consider proportionate to a subscription. They are guidelines rather than hard caps: nothing stops working the moment you pass one, and we come to you first.
| What | Included | Measured | If you go past it |
|---|---|---|---|
| AI document reading | 150 documents per active vehicle per calendar month, and not materially above 10 per vehicle per day sustained | Per calendar month, per account | We contact you and agree a usage-based add-on or a different plan. |
| Shipments and orders | Proportionate to the plan and the fleet on the account. No fixed cap, and no fee per shipment. | Rolling three months | Sustained volumes far above the norm for the subscription are re-tiered, after a conversation. |
| Routing and map lookups | Planning your own operational trips. Bulk, automated or stored-for-reuse lookups are not covered. | Continuous | Rate limiting, or your own provider key. |
| Document storage | 2 GB per active vehicle, pooled across the account rather than per vehicle | Total held | We agree archiving of older documents, or charge for the excess. |
| Users and drivers | No limit and no per-seat charge, for the people who work for the Customer or drive for it. | Continuous | None. |
| API and EDI | Within the published rate limits, for your own integrations. | Per minute, per key | 429 responses. Exporting your own data is always allowed; see below. |
One AI document is one file or one e-mail body read once. An e-mail with three attachments is four documents; a re-read of the same file after you correct the mapping is not counted again. Page count does not matter.
You will know before we do anything. Usage against these baselines is visible in your own account, and we contact the account administrator when an account passes roughly eighty percent of one. Nobody gets a surprise invoice for a threshold they could not see.
Exporting your own data is not bulk use. Downloading your shipments, invoices, documents or master data, through the interface or the API, is something you are entitled to do and is never treated as abuse. What the restriction above is about is mirroring, caching or reselling routing, map and AI output, which we buy per call.
4. AI features
AI features assist the people doing the work and rely on third-party providers we pay per call. Use them to process your own transport documents for your own operation. Processing third-party, bulk, synthetic or scraped data, or using the output to build or train a competing service, is not permitted.
Where an account needs more AI reading than the baseline, we agree it in writing first: either a usage-based add-on at a stated rate per document, or a plan that includes the volume. We do not meter you quietly and invoice afterwards.
5. Third-party services and costs
The Service uses third-party routing, mapping and AI providers, and some of that is billed to us per call. Routing and distance calculation run on our own infrastructure by default, so ordinary planning costs you nothing extra whatever the volume.
Where usage causes disproportionate third-party cost, we will tell you what it is, what is driving it and what the options are, and agree one with you before anything is charged on. Those options are normally rate limiting, a usage-based add-on, or supplying your own provider key. No third-party cost is passed through without the Customer agreeing to it in advance.
6. Prohibited use
You may not:
- Share, resell or sublicense access to the Service, or run an unrelated third party's operation through your account. Running several legal entities that belong to the same group is normal and supported: that is what the multi-entity structure on Enterprise is for, and each entity counts for pricing;
- Split, structure or distribute usage across accounts to circumvent pricing, limits or this policy;
- Access the Service through automated means other than the official API, or scrape its data or interfaces;
- Resell, redistribute or cache routing, map, distance or AI output;
- Upload malware or unlawful, infringing or harmful content, or use the Service for unlawful purposes;
- Overload, disrupt, probe or circumvent the Service, its limits or its security;
- Reverse engineer, decompile or attempt to extract the source code or models, or benchmark the Service for a competing product.
7. Excessive or abnormal use, and our remedies
For ordinary overage, meaning an account that outgrew its plan, the order is fixed and it always starts with a conversation:
- We contact the account administrator with what we are seeing and what is driving it.
- We agree a fix together: a usage-based add-on, a different plan, or a change on your side.
- The agreed change takes effect from a date we both know, never retroactively.
Nothing in step one to three happens without notice, and no charge is applied for usage in a period that has already passed.
Separately, and only for abuse, a security or legal risk, or usage that threatens the stability of the Service for other customers, we may act immediately: rate limiting, feature caps, or suspension. That is a different situation from an account that got bigger, and we will say which one we think we are in.
A failure to enforce any part of this policy is not a waiver of the right to do so later.
8. Trial period
Where a trial is offered, its length and conditions are stated in writing at the time, as set out in section 6 of the Terms and Conditions. A trial is for genuine evaluation and is subject to this policy. We may limit or end trial access where usage is disproportionate or abusive.
9. Changes
This policy carries a version number and a date, both at the top. A change that reduces included usage is announced to account administrators at least 30 days before it takes effect, on the same clock as the Terms, and a Customer who does not accept it may cancel before that date without penalty. Clarifications that reduce nothing take effect when published.
10. Contact
If you are about to do something that might not fit, ask before rather than after. A planned peak, a new large customer, a bulk import: tell us and we will say plainly whether it is a problem and what it would cost.
Email: support@orin.software, or legal@orin.software for the contractual side.