Country Restrictions Policy
Jurisdiction, sanctions, routing, and geographic eligibility controls for BRidge.
1. Purpose
This Country Restrictions Policy describes how BRidge applies geographic, jurisdictional, sanctions, and cross-border access controls to users, organizations, counterparties, contracts, Bills of Lading, marketplace activity, index access, payment flows, and logistics workflows.
2. Restricted Jurisdictions
BRidge does not permit platform access, transaction activity, payout activity, trade execution, settlement activity, or logistics coordination involving jurisdictions, persons, entities, vessels, carriers, banks, or counterparties subject to applicable sanctions, embargoes, blocked-party designations, or other legal restrictions.
Restricted jurisdictions may include countries or territories subject to comprehensive sanctions, targeted sanctions, export prohibitions, import prohibitions, or heightened compliance controls under United States law or other applicable legal regimes.
3. Sanctions and Denied-Party Screening
BRidge may screen users, organizations, counterparties, carriers, brokers, mills, yards, financial participants, and related parties against sanctions, denied-party, watchlist, politically exposed person, adverse-media, and other risk datasets.
- Access may be denied or suspended during screening.
- Transactions may be paused, cancelled, rejected, or escalated for review.
- BRidge may require supplemental identity, ownership, location, beneficial-owner, carrier, or end-use information.
4. Geographic Eligibility
BRidge may require an organization to provide a valid operating address, principal place of business, tax or registration identifier, facility location, shipping origin, shipping destination, and responsible contact before platform access is granted or transaction activity is enabled.
5. Cross-Border Transaction Controls
Cross-border transactions may require country-of-origin tags, destination-country tags, Harmonized System or commodity classification data, export documentation, import documentation, port information, customs documentation, tax/duty fields, carrier verification, or other compliance evidence.
6. Prohibited Routing and Evasion
Users may not use BRidge to evade sanctions, embargoes, import/export controls, customs requirements, tax duties, carrier controls, identity controls, counterparty screening, or other applicable restrictions. Prohibited conduct includes routing through intermediary entities, alternate ports, aliases, shell companies, or false documentation to disguise a restricted jurisdiction or party.
7. Carrier, Vessel, and Logistics Restrictions
BRidge may restrict or reject logistics activity involving carriers, vessels, brokers, routes, warehouses, yards, mills, or ports that present sanctions, safety, insurance, licensing, customs, reputational, or operational risk.
8. Data, Index, and Market Access Restrictions
Certain BRidge data feeds, indices, benchmarks, pricing references, export files, APIs, analytics, or market surfaces may be restricted by jurisdiction, user type, license type, plan, data rights, or applicable law.
9. User Responsibilities
- Users must provide accurate jurisdiction, location, ownership, tax, shipping, and compliance information.
- Users must not misrepresent origin, destination, counterparty identity, beneficial ownership, shipment purpose, or end use.
- Users must promptly notify BRidge if a transaction, counterparty, route, material, document, or carrier becomes restricted or legally questionable.
10. Enforcement
BRidge may suspend access, block a transaction, freeze a workflow, revoke credentials, cancel a contract, withhold payout processing, restrict document generation, preserve evidence, or notify relevant parties where required or appropriate.
11. No Legal Advice
BRidge provides operational controls and compliance tooling, but users remain responsible for determining and complying with laws applicable to their own transactions, exports, imports, logistics, taxes, duties, and counterparties.