Sanctions compliance.

Last updated: September 19, 2026

Restricted jurisdictions

Prime Freight Logistics Inc. does not provide freight forwarding, customs brokerage, warehousing, quoting, booking or payment services to, from or within the following jurisdictions:

• Cuba
• Iran
• North Korea (Democratic People's Republic of Korea)
• Syria
• The Crimea, Donetsk and Luhansk regions of Ukraine, including Sevastopol

This applies regardless of the nationality or location of the party requesting the service, and regardless of whether the jurisdiction appears as an origin, a destination, a transit point or a place of payment.

How the restriction is enforced

The restriction is implemented in our systems, not only stated in this policy. The following controls operate independently of one another, so that no single failure removes the restriction:

• Network-level access controls. Requests originating in a restricted jurisdiction are refused before any page or application route is reached. This is enforced both by our hosting provider's firewall and, independently, by access-control code held in our own version-controlled repositories.
• Application-level controls. Every endpoint that accepts information from the public — contact and quote requests, account registration, rate enquiries and shipment tracking — repeats the check for itself rather than relying on the layer in front of it.
• Route and location controls. Ports and airports in restricted jurisdictions are excluded from the location data our platform is built from. They cannot be selected as an origin or destination in any quote, booking or enquiry. This control does not depend on where a request originates, and so is not affected by the use of a proxy or VPN.
• Country selection controls. Restricted jurisdictions are not offered in any country selection field anywhere in our platform, including address, customs and registration forms.
• Payment controls. No payment request, card authorisation or bank payment record is created for a request originating in a restricted jurisdiction. Billing addresses are collected and screened. Payments are refused before they are created rather than reversed afterwards.

Each refusal is recorded in an auditable log identifying the control that acted and the jurisdiction concerned. Access denied on these grounds is served with HTTP status 451 (Unavailable For Legal Reasons) and an explanation, rather than a generic error.

Editorial content

Our market intelligence and blog pages report on global trade conditions, including events affecting shipping lanes near restricted jurisdictions — for example transits of the Strait of Hormuz or disruption in the Red Sea. This coverage is editorial and does not constitute an offer of service. Where an article refers to a restricted jurisdiction, it is reporting on conditions affecting international trade generally, and must not be read as an indication that Prime Freight provides services to, from or within that jurisdiction.

Screening and due diligence

In addition to the automated controls above, shipments are subject to our standard trade compliance review, including restricted and denied party screening, end-use review and verification of the parties to a transaction, before cargo is accepted.

Reporting a concern

If you believe you have encountered a listing, quotation or service option on this website that is inconsistent with this policy, or if you have been refused access in error, contact us at compliance@primefreight.com. Reports are reviewed by our compliance team.

Changes

This policy is updated as sanctions programmes change. The controls described above resolve their jurisdiction list from a single source in our codebase, so an addition takes effect across every control at once.