Platform Risk Disclosure

This page describes operational, technical, and infrastructure risks that arise from using the Matrex platform itself.

It does not describe investment risks of any token, asset, fund, project, or offer administered through Matrex. Those risks are determined by the relevant issuer and disclosed in the issuer's offer documents.

This disclosure is general and is not exhaustive. Issuers and users must still read the Terms and Conditions, the Privacy Policy, and the Regulatory Boundary Statement.

Matrex relies on third-party identity verification, sanctions screening, and AML/CFT providers. Verification outputs may include automated checks, biometric comparisons, document image analysis, watchlist screening, and risk scores.

These checks may produce false negatives (a legitimate user is incorrectly blocked or downgraded) or false positives (a higher-risk user is incorrectly approved). Issuers and users should expect both outcomes to occur from time to time.

Identity verification providers may be temporarily unavailable, return degraded results, change their methodology, or fail to capture a document or selfie. During provider downtime, onboarding, transfers, redemptions, or other workflows may be delayed.

Users must provide accurate information, valid identity documents, and complete any additional checks requested by the issuer or by Matrex.

Tokens administered through Matrex may require wallet allowlisting before subscription, transfer, or redemption can occur. Allowlisting is driven by issuer policy, identity status, jurisdictional eligibility, and sanctions screening.

Allowlisting decisions may be incorrect. A wallet may be mistakenly approved (and later restricted once the error is identified) or mistakenly rejected (delaying a legitimate user).

Users must register the correct wallet address. Tokens sent to an address not on the allowlist may be blocked at the smart-contract level and may not be recoverable through Matrex.

Matrex does not guarantee that any wallet will remain allowlisted. Issuer instructions, sanctions changes, identity expiry, or compliance reviews may result in removal of a previously approved wallet.

Tokens administered through Matrex may be subject to issuer-policy-driven transfer restrictions, including holding periods, jurisdictional gating, investor eligibility checks, sanctions screening, approval queues, and smart-contract restrictions.

Transfer requests may be queued, deferred, rejected, or unwound where required by issuer instructions, applicable law, or platform compliance controls.

Matrex enforces these restrictions on behalf of the issuer. Matrex does not set the underlying transfer policy and does not decide whether any particular transfer should occur. The issuer is responsible for the policy that drives transfer outcomes.

Buyer-seller matching, bulletin-board, and transfer-request workflows are private administration tools only. Matrex does not guarantee that a buyer or seller will be found, that a transfer will be approved, that a price will be achieved, or that any secondary market will exist.

Unless expressly agreed in a separate written custody arrangement, users hold their own wallets, private keys, seed phrases, and signing devices. Matrex does not custody user assets.

Loss of private keys, loss of seed phrases, compromised devices, malware, phishing, social engineering, or unauthorised signing may result in permanent loss of tokens. Matrex cannot recover assets sent or signed from a compromised wallet.

Users are responsible for hardware wallet integrity, operating system security, browser extension hygiene, transaction-signing review, and approval of smart-contract interactions.

Blockchain transactions are typically irreversible. A wallet signing decision cannot be undone after broadcast.

Token issuance, transfer restrictions, allowlisting, and registry administration may be enforced through smart contracts.

Matrex's smart contracts undergo independent security review prior to deployment. No software, however, is bug-free. Latent defects, edge cases, dependency changes, compiler issues, or unexpected interactions with other contracts may produce errors, halted transfers, locked balances, or unintended state.

Smart contracts may be paused, upgraded, replaced, or migrated by the issuer or by Matrex (acting on the issuer's instructions) to address security findings, compliance changes, or operational requirements. Pauses and upgrades may temporarily prevent transfers, redemptions, or other activity.

Audits reduce, but do not eliminate, smart-contract risk.

The Matrex platform relies on public blockchain networks and on RPC providers, indexers, and explorers. These are operated by third parties and may experience outages, degraded performance, latency spikes, or data inconsistency.

Chain reorganisations, finality delays, mempool congestion, gas spikes, fee market volatility, mempool censorship, and failed transactions may delay or block subscription, transfer, or redemption activity.

A blockchain network may fork, undergo a protocol change, deprecate a feature, or change its security assumptions. Matrex does not control these network-level events.

Blockchain data displayed by Matrex (balances, transfers, allowlist status) is sourced from network and indexer providers and may briefly lag on-chain truth.

Matrex integrates with fiat payment processors (including Stripe) and on-chain stablecoin rails (including USDC) for subscription, redemption, and settlement workflows.

Card networks, banks, payment processors, and stablecoin issuers may decline, delay, reverse, freeze, or claw back payments based on their own risk, compliance, sanctions, dispute, or chargeback rules.

Stablecoin issuers may pause transfers, freeze addresses, change redemption terms, or experience peg deviations. These events affect on-chain settlement and may delay or block transactions.

Payment rail outages, network maintenance, or compliance holds may prevent subscriptions, distributions, or redemptions from settling within expected timeframes.

The Matrex platform depends on a number of third-party services, including (without limitation):

Any of these providers may experience outages, degraded service, security incidents, pricing changes, termination of service, or changes to their terms. A third-party incident may interrupt onboarding, document signing, sanctions screening, secure document delivery, payment processing, or platform availability.

Matrex is not responsible for third-party service failures, but will work to route around them where reasonably practicable.

Matrex performs planned maintenance, security patching, infrastructure upgrades, and deployments. Planned maintenance windows are typically announced in advance where reasonably practicable.

Unplanned outages may occur, including incidents caused by infrastructure providers, denial-of-service activity, software defects, configuration errors, or third-party dependencies.

During an outage, users may be unable to log in, complete onboarding, sign documents, submit transfers, or view balances. Issuer-driven actions (such as transfer approvals or distribution runs) may be deferred.

Matrex does not guarantee uninterrupted, error-free, or permanent availability.

Matrex is infrastructure software. Matrex is not the issuer, broker, dealer, exchange, alternative trading system, custodian, transfer agent, fund manager, investment adviser, financial adviser, supervisor, trustee, or underwriter of any token, security, or financial product administered through the platform — unless Matrex is expressly identified as such in the relevant offer documents and supported by applicable authorisation.

Matrex does not endorse, approve, verify, guarantee, or underwrite any issuer, project, asset, token, return, redemption right, liquidity pathway, listing pathway, custody arrangement, valuation, forecast, distribution, yield, risk factor, tax treatment, or exit strategy.

Investment risks are the responsibility of the relevant issuer and are described in the issuer's offer documents.