Export Control Policy

Export, import, customs, software, API, data, and end-use controls for BRidge.

Version 1.0 Effective April 25, 2026 Atlas IP Holdings / BRidge

Export-control obligations apply to users, counterparties, commodities, documents, routes, software, data, APIs, and any cross-border movement or access enabled through BRidge.

1. Purpose

This Export Control Policy governs the use of BRidge for transactions, logistics workflows, document generation, data access, software access, API access, and market activity that may involve export-control, import-control, customs, sanctions, end-use, end-user, or country-of-origin requirements.

2. Scope

This policy applies to all BRidge users, organizations, yards, buyers, sellers, brokers, traders, mills, carriers, administrators, API users, data-license users, and any party using BRidge to create, view, manage, settle, export, or transmit transaction records.

3. Controlled Activity

BRidge may treat the following as controlled activity requiring additional information, review, or restriction:

Cross-border shipments or transactions.
Materials subject to import/export classification, customs, environmental, safety, or end-use restrictions.
Transactions involving restricted countries, territories, parties, carriers, ports, vessels, or financial institutions.
Access to software, APIs, indices, benchmark data, pricing feeds, operational records, or technical information by users in restricted jurisdictions.

4. Required Export Data

Where applicable, BRidge may require users to provide or validate export-related fields including:

Field	Purpose
Country of origin	Identifies where material originated for customs, sanctions, and supply-chain controls.
Destination country	Determines whether routing, import, export, or sanctions restrictions apply.
HS code / commodity classification	Supports customs, duty, and commodity classification requirements.
Port code / routing data	Supports shipment routing, customs review, and logistics verification.
End use / end user	Supports restricted-use and denied-party review where applicable.

5. User Certifications

By using BRidge, users represent that they will not use the platform to violate export-control, import-control, customs, sanctions, anti-boycott, tax, anti-money-laundering, or anti-corruption laws.

6. Prohibited Uses

Shipping, selling, buying, brokering, financing, or settling restricted materials, services, data, or software in violation of applicable law.
Transacting with sanctioned, blocked, denied, or otherwise restricted parties.
Concealing origin, destination, beneficial ownership, end user, end use, port, carrier, or route.
Using aliases, intermediaries, shell entities, or false documents to avoid export-control review.

7. Platform Controls

BRidge may apply automated or manual controls including screening, transaction holds, document holds, payout holds, routing restrictions, audit logging, evidence preservation, review queues, identity verification, and administrative escalation.

8. Documentation

Users are responsible for obtaining and retaining all export, import, tax, customs, carrier, environmental, material, and shipping documentation required for their transactions. BRidge-generated documents support operational recordkeeping but do not replace required government filings or legal determinations.

9. Data and Software Access

BRidge software, APIs, data feeds, indices, analytics, and documentation may be subject to export-control restrictions. BRidge may restrict access by user identity, organization, IP address, location, jurisdiction, license type, plan, or compliance status.

10. Review and Enforcement

BRidge may reject, suspend, cancel, or escalate any activity that presents export-control risk. BRidge may also preserve logs, documents, communications, and evidence for compliance review.

11. No Legal Advice

BRidge provides operational controls and compliance tooling. Users remain responsible for obtaining legal, customs, tax, export, and import advice for their own activities.