Customs Compliance Export Controls Sample Clauses

Customs Compliance Export Controls 
AutoNDA by SimpleDocs

Related to Customs Compliance Export Controls

  • Export Controls Both Parties will adhere to all applicable laws, regulations and rules relating to the export of technical data and will not export or re-export any technical data, any products received from the other Party or the direct product of such technical data to any proscribed country listed in such applicable laws, regulations and rules unless properly authorized.

  • Export Compliance The Services, Content, other technology We make available, and derivatives thereof may be subject to export laws and regulations of the United States and other jurisdictions. Each party represents that it is not named on any U.S. government denied-party list. You shall not permit Users to access or use any Service or Content in a U.S.-embargoed country (currently Cuba, Iran, North Korea, Sudan or Syria) or in violation of any U.S. export law or regulation.

  • Import and Export Compliance In connection with this Agreement, each party will comply with all applicable import, re-import, export, and re-export control laws and regulations, including the Export Administration Regulations, the International Traffic in Arms Regulations, and country-specific economic sanctions programs implemented by the Office of Foreign Assets Control. For clarity, you are solely responsible for compliance related to the manner in which you choose to use the Service Offerings, including your transfer and processing of Your Content, the provision of Your Content to End Users, and the region in which any of the foregoing occur.

  • Export Control This Agreement is made subject to any restrictions concerning the export of products or technical information from the United States or other countries that may be imposed on the Parties from time to time. Each Party agrees that it will not export, directly or indirectly, any technical information acquired from the other Party under this Agreement or any products using such technical information to a location or in a manner that at the time of export requires an export license or other governmental approval, without first obtaining the written consent to do so from the appropriate agency or other governmental entity in accordance with Applicable Law.

  • Export Control Laws The Company has conducted its export transactions in accordance in all material respects with applicable provisions of United States export control laws and regulations, including but not limited to the Export Administration Act and implementing Export Administration Regulations.

  • Standards Compliance DNS. Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn--ndk061n”).

  • Requirement to Utilize HUB Compliance Reporting System Pursuant to Texas Administrative Code, Title 34, Part 1, Sections 20.285(f) and 20.287(b), TFC administers monthly administration HSP-PAR compliance monitoring through its HUB Compliance Reporting System commonly known as B2G. PSP and PSP’s subcontractors/subconsultants shall submit required PAR information into the B2G system. Any delay in the timely submission of PAR information into the B2G system will be treated as an invoicing error subject to dispute under Texas Government Code Section 2251.042.

Time is Money Join Law Insider Premium to draft better contracts faster.