INQTEL Technology & Administration Disclosure

INQTEL Pty Ltd operates strictly and exclusively as a Software-as-a-Service (SaaS) and technology administration provider.

INQTEL does not take possession, custody, or technical control of digital assets or cryptographic private keys. All security policies, transaction limits, and velocity guardrails are programmatically executed layered on top of infrastructures entirely owned and controlled by our clients.

To view our complete institutional framework, please read the formal Technology Services Agreement below.

INQTEL TECHNOLOGY SERVICES AGREEMENT

Administrative Management & Wallet Policy Configuration Layer (Non-Custodial)
PUBLIC DISCLOSURE & SAAS DECLARATION
This document serves as a binding legal framework and public disclosure. INQTEL Pty Ltd operates strictly and exclusively as a Software-as-a-Service (SaaS) and Technology Administration Provider.

The Company does not provide financial services, does not act as a deposit-taking institution, and does not take possession, custody, or title of any digital assets, cryptographic keys, or private key shards. Absolute operational control of all funds remains continuously with the Client.

This Technology Services Agreement (the "Agreement") is entered into as of the effective date of execution of the accompanying electronic signing transaction, digital acceptance protocol, or platform onboarding workflow (the "Effective Date"), by and between INQTEL PTY LTD (the "Company") and the legal entity or individual identifying themselves as the user or client (the "Client").

WHEREAS, Company has engineered a proprietary administrative, rule-enforcement, and velocity-management software layer compatible with multi-signature cryptographic network architectures; and

WHEREAS, Client desires to retain Company to configure, test, implement, and monitor specific operational guardrails, transaction limits, and automated business policy layers upon wallets where the Client holds the ultimate controlling cryptographic keys;

NOW, THEREFORE, the parties agree to the following terms and conditions:

1.0 DEFINITIONS

- "Client-Retained Cryptographic Keys" means the primary operational private key pairs and off-line emergency disaster recovery backup key shards generated during wallet initialization, of which the Client maintains exclusive physical or software possession and complete sovereign ownership. - "Company Administrative Platform" means the software management dashboard, API endpoints, webhook listeners, and policy enforcement tools provided by the Company to track and govern transaction velocities based on Client mandates. - "Non-Custodial Administration" means the technical reality wherein the Company configures programmatic spending rules but completely lacks the technical capability, backdoor access, or signature weight required to unilaterally sign transactions, move assets, or freeze asset ledgers independent of the Client's keys. - "Supported Digital Assets" means Bitcoin (BTC), Ethereum (ETH), Tether (USDT), and any digital token layers explicitly supported by the programmatic rule engine. - "Velocity Filter" means an automated, code-enforced spending policy parameter restricting individual transaction sizing, daily volumes, cumulative destination weightings, or sign-off thresholds over rolling timeframes.

2.0 NON-CUSTODIAL SCOPE OF SERVICES & KEY SEPARATION

2.1 SaaS Infrastructure Provisioning
The Company shall integrate its technical management interface with the Client's underlying multi-signature nodes. The Company's scope of work is limited strictly to injecting corporate policy controls, establishing spending filters, managing automated webhook alerts, and maintaining transaction data monitoring layers. The Client remains the physical manager of the wallet infrastructure.

2.2 Complete Isolation from Key Custody
The Client explicitly acknowledges and warrants that the Client holds, protects, and controls the primary cryptographic private keys and the backup key shards. The underlying infrastructure utilizes a multi-signature configuration where an institutional custodian holds one key shard for signature matching against company rules, but the Client retains the definitive majority weight or controlling recovery shares. The Company's infrastructure acts solely as a programmatic rule validator. At no point shall the Company, its executives, or its automated scripts solicit, store, or accept exposure to the Client's raw seed phrases or unencrypted private keys.

2.3 Client Autonomy and Independent Asset Recovery
Because this is a pure Software-as-a-Service deployment, the Client maintains absolute transaction authorization authority. In the event that the Company's servers, website, or interfaces experience an unexpected operational outage, the Client retains full, unimpeded capacity to bypass the Company's policy layer entirely and recover, transfer, or sign for all digital assets natively on-chain using their independently stored backup key shards.

3.0 POLICY ARCHITECTURE, GUARDRAILS & CIRCUIT BREAKERS

3.1 Custom Rule Injector Engine
The Company shall program the operational parameters chosen by the Client directly into the transaction processing logic. These parameters are optimized for specific asset characteristics to prevent operational compromises:

- Bitcoin (BTC) Velocity Controls: Rules must strictly enforce programmatic minFeeRate and maxFeeRate caps to insulate the Client from fee-manipulation exploits, alongside rolling hourly caps.

- Ethereum (ETH) Destination Checking: Smart contract interactions are programmatically restricted to audited addresses, mitigating address poisoning and lookalike contract vulnerabilities.

- Tether (USDT) Volume Limits: Multi-tiered rolling velocity windows are applied to regulate corporate stablecoin expenditures, matching active enterprise liquidity profiles.

3.2 Hard Blocks and Verification Flows
If a transaction request initiated within the Client's system violates an active Velocity Filter or attempts to transfer an amount exceeding the maximum spending ceiling allocated under their commercial profile, the platform will automatically execute a Hard Block. The transaction will be rejected at the software layer and will not be forwarded for cryptographic signing. Releasing a Hard Block requires the Client to re-authenticate via secondary out-of-band video identity protocols or modify their active policy guidelines through verified organizational workflows.

4.0 FEES, ADJUSTMENTS, AND PUBLIC PRICING TRANSPARENCY

4.1 True SaaS Fee Structures
Client agrees to pay the Company the up-front integration fees, monthly platform subscription fees, software licensing metrics, and payload validation costs set forth in their private corporate Addendum or Schedule A Fee Matrix. All fees are reflective of dedicated infrastructure provisioning, custom webhook pipelines, and prioritized operational monitoring queues.

4.2 Blockchain Network Fee Disclaimer
MANDATORY NETWORK TRANSPARENCY NOTICE: All transactions executed on public blockchain networks natively require the payment of protocol consumption fees ("Gas Fees" on Ethereum/USDT or "Miner Fees" on Bitcoin). The Client acknowledges that these fees are native network costs determined entirely by open-source protocol consensus and network congestion. They are passed through natively, paid directly from the Client's wallet balances, and are completely independent of and separate from the Company's technology service fees.

4.3 Website Disclosure and Fee Modification
This document may be displayed publicly on the Company's website as an operational disclosure. The Company reserves the absolute right to amend this Agreement and the baseline Schedule A Fee Matrix upon thirty (30) days' prominent public posting or direct digital notification. Continued utilization of the Company's administrative software layer after the notice period expires constitutes definitive legal acceptance of the revised terms or fee structures.

5.0 DEFINITIVE ALLOCATION OF RISK & COMPLETE LIABILITY RELEASE

The Client explicitly accepts full, unmitigated responsibility for the physical and digital safety of their cryptographic private keys, seed phrases, and backup key shards. Since the Company operates strictly as a software provider without key custody, the Company shall have zero liability for any asset loss, theft, wallet drain, or hacking event resulting from:

1. Client negligence regarding password safety or API key exposure;
2. Physical loss, misplacement, or destruction of the Client's backup key shards;
3. Malicious transaction signing by the Client's authorized personnel or compromised internal credentials; or
4. Flaws, exploits, code bugs, or structural failures inherent to the Bitcoin, Ethereum, or Tether smart contract protocols.

The Company's absolute financial liability under any circumstances is strictly limited to the platform subscription fees paid by the Client to the Company over the immediate six (6) months prior to a formal dispute.

Corporate Registry Info: INQTEL PTY LTD | ABN 17 631 457 228 | DUNS 745354067 Web: https://inqtel.net.au | Contact: admin (at) inqtel.net.au