Coinductor — Anti-Money Laundering (AML), Counter-Terrorist Financing (CTF) & Sanctions Compliance Policy
Effective Date: June 2026
Techwhirl Information Technology CO LLC (hereinafter referred to as "Coinductor", "the Company", "we", "us", or "our"), a company incorporated and operating under the laws of mainland United Arab Emirates (UAE), establishes this Anti-Money Laundering (AML), Counter-Terrorist Financing (CTF), and Sanctions Compliance Policy (hereinafter referred to as "the Compliance Policy").
This document defines the high-level control frameworks, technical restrictions, and risk mitigation methodologies implemented across our mobile application container, desktop Web Interface, and automated transaction operating systems (collectively, "the Services") to prevent the misuse of our software interfaces for financial crime.
1. Regulatory Context & The Non-Custodial Compliance Boundary
UAE Federal Legal Framework
This Policy is designed to align with the core regulatory objectives of the UAE federal compliance architecture, including UAE Federal Decree-Law No. 20 of 2018 on Anti-Money Laundering and Combating the Financing of Terrorism and Financing of Illegal Organisations, and its subsequent executive regulations.
The Decoupled Enforcement Paradigm
Because Coinductor is engineered as a strictly non-custodial decentralized software client, our structural capability to enforce compliance differs fundamentally from traditional centralized custodians or exchanges.
⚠️ EXPLICIT CONTROL NOTICE
Techwhirl Information Technology CO LLC does not have custody, possession, or control over your digital tokens, private keys, or on-chain transaction paths. We cannot freeze your funds, reverse your ledger actions, or block addresses directly on the public blockchain.
Therefore, compliance enforcement under this Policy occurs exclusively at the software access layer. The Company reserves the absolute right to unilaterally terminate backend API support, block validation handshakes, and restrict access to our automated orchestration utilities (Smart Send routing, OTO Pass discovery scripts, and the Dapp Pass registry) for any user flagged for compliance violations.
2. Strict Prohibited Demographics & Sanctions Criteria
To prevent exposure to international financial crime and adhere to UAE national security protocols, Coinductor enforces absolute onboarding barriers. The following categories of natural persons or corporate entities are strictly designated as Excluded Persons and are entirely banned from accessing our software interfaces:
Underage Prohibitions: Any natural person under the age of 16.
United States Jurisdiction Exclusion: Any natural person or corporate entity located within, operating from, holding citizenship in, or residing within the United States of America (USA) or any of its designated sovereign territories.
Sanctioned Entities and Jurisdictions: Any individual or entity listed on the UAE Local Terrorist List (issued by the UAE Cabinet), the United Nations Security Council Sanctions Committees List, the US Office of Foreign Assets Control (OFAC) SDN list, or any equivalent list maintained by international compliance bodies.
Geographic Trade Embargoes: Any user attempting to establish a connection or request an API handshake from within a country or territory subject to global trade restrictions, comprehensive embargoes, or localized sanctions enforced by the UAE or international governing panels.
3. Technical Enforcement & Automated Risk Mitigation Matrix
To actively monitor system parameters and prevent Excluded Persons from interacting with our software infrastructure, Coinductor deploys automated background defensive scripts:
A. Automated Geofencing & IP Telemetry Monitoring
Our backend microservices run continuous telemetry tracking loops that analyze incoming connection parameters and network source routing.
If a user attempts to synchronize a wallet, request a Smart Send optimization path, or purchase an OTO Pass SaaS credit from an IP address mapped to a prohibited or sanctioned jurisdiction, the system will instantly terminate the API handshake.
The application client container will trigger an automated interface block, preventing further software utility access.
B. Mobile Billing Gateway Fraud Vetting
To mitigate the risks of credit structuring, card fraud, and smurfing layers within traditional payment rails, our Billing Service implements automated validation scripts. All single-use OTO Pass purchases executed through mobile marketplace channels (Apple App Store, Google Play, or carrier billing) are subject to automated verification checks before the SaaS resource discovery script is authorized to run on the public ledger.
C. Open API Registry Vetting (Dapp Pass Firewall)
The Dapp Pass interface features no native subscription models and does not process open-text web text URL inputs.
To prevent users from navigating to unregulated or high-risk mixing protocols via our platform, the app container restricts options to an established, structured registry list of third-party resource providers.
Third-party providers who utilize our open API infrastructure must undergo systematic integrity screening before being displayed within the registry panel. Any provider found routing traffic to illicit address clusters or sanctioned endpoints will be immediately scrubbed from our list.
4. Transaction Orchestration Abuse & Anti-Structuring Controls
Because our Blockchain Transaction Operating System (BTOS) automates resource discovery and cost optimization, we implement specific checks to prevent the software from being weaponized by bad actors:
A. OTO Pass SaaS Abuse Protection
The OTO Pass discovery script crawls public ledger data matrices to identify excessive amounts of unnecessary or unclaimed resources left underutilized across the blockchain network.
Our system places strict rate limits on the frequency of OTO Pass software executions tied to individual device serial numbers or public wallet keys.
We actively block high-frequency automated bots or custom script wrappers designed to manipulate our resource discovery engine for industrial-scale high-volume layering or structuring operations.
B. Smart Send Optimization Filters
The Smart Send engine dynamically batches cost variables via third-party resource pools. Our backend data tracking networks analyze transaction frequency anomalies to identify suspicious behavior or potential network exploitation schemes. If an address is flagged by our risk engines, the software will refuse to generate optimization routes (Route 1) and will default to informing the user of native network fees via the preflight confirmation screen.
5. Reporting & Cooperation with Competent Authorities
Techwhirl Information Technology CO LLC maintains a policy of active cooperation with authorized law enforcement and regulatory bodies inside mainland UAE, subject to the technical constraints of our non-custodial design.
Administrative Production Demands
Valid Judicial Compulsion: If presented with an official, legally binding judicial order or decree issued by a competent court or federal authority in mainland Dubai, United Arab Emirates, Coinductor will comply with the specific mandate.
Data Scope Limits: Because we maintain a strict zero-custody data architecture, the data elements available for administrative production are limited to basic client indicators, logged network telemetry strings, and historical public wallet address paths tracked by our backend validation systems. We cannot produce private keys or seed phrases under any circumstances, as they remain completely isolated on the user's physical hardware device.
Reporting Anomaly Detection: The Company reserves the right to compile and report technical findings regarding mass bot usage or systemic evasion of our geofences directly to relevant compliance networks if we detect structured cyber attacks against our open API backend nodes.
6. Policy Governance, Review Cycles, and Enforcement Indemnity
Unilateral Enforcement Authority: Techwhirl Information Technology CO LLC retains absolute authority to determine if a user’s interaction with the platform violates any clause of this Compliance Policy. If our automated risk scoring tools or administrative teams flag a user account, we will sever backend API connections immediately and without prior notice.
Complete Loss Indemnity: The company is fully indemnified and holds zero liability for any operational downtime, failed transaction paths, or lost commercial opportunities resulting from our enforcement of compliance blocks or geofence restrictions.
Jurisdiction & Amendments: This Policy is governed exclusively by the federal laws of mainland United Arab Emirates (UAE). Any administrative disputes or challenges regarding compliance blocks shall be brought exclusively before the courts of mainland Dubai, UAE. We reserve the right to amend this text at any time to adapt to changing regulatory demands, and updates become effective immediately upon their publication.