Anti-Money Laundering Policy
This Policy describes how xHunter checks deposits and withdrawals, reviews potential risks and communicates with users. It aims to prevent the service from being used for proceeds of crime, fraud or other unlawful transactions while limiting disruption to legitimate users.
Checks focus on transactions and the origin of funds. The process does not include a mandatory passport or selfie verification procedure.
xHunter assesses both incoming deposits and outgoing withdrawals using its own solution and external tools. The assessment may consider blockchain addresses, transaction history, the source and destination of assets, related risk signals and information supplied during review.
We do not publish tool names, exact thresholds, detection methods or protected sources of risk information. The Privacy Policy explains data handling. Keeping technical controls confidential does not remove the user's ability to ask about their transaction or request a review.
An automated flag is not a finding that you committed an offence or that your funds are unlawful. A responsible team member reviews flagged transactions. We consider the context and relevant supporting information before making a final service decision.
xHunter may suspend a transaction, restrict an account's financial functions or discontinue service in the following circumstances:
- Indicators link funds, an address or a transaction to fraud, theft, money laundering, terrorist financing or other unlawful activity.
- Information indicates disputed origins of funds, an unauthorized transfer or a lack of authority for the user to dispose of the relevant assets.
- Material inconsistencies are identified between transactions, the user's explanations and the evidence supplied about the origin of funds.
- The user supplies inaccurate materials or does not provide information relevant to the transaction that is necessary to complete the review.
- There are indicators of attempts to circumvent checks, restrictions or an earlier decision, including through related accounts.
- There are indicators of account takeover, unauthorized access or use of the account by a third party.
- A binding requirement is received from a competent authority, or a restriction is needed to meet applicable requirements.
- An internal assessment identifies other circumstances giving xHunter reasonable grounds to consider a restriction necessary to prevent unlawful transactions, protect users or maintain service security. This list of grounds is not exhaustive.
The nature of the identified risk determines the scope of restrictions.
The normal response is to restrict the specific transaction under review:
- A deposit can remain pending and unavailable for allocation or trading until the review is completed and the deposit is accepted.
- A withdrawal can be held while the transfer or destination address is assessed.
- Broader financial restrictions can apply where the circumstances concern the account as a whole or a binding requirement applies.
We record the reason and scope of restrictions internally. Account viewing, transaction history and support remain accessible. A separate security incident, such as suspected account takeover, can require separate access restrictions.
We inform you about the restricted action, the information needed, the contact route and the next review update, to the extent disclosure is permitted and does not undermine the checks.
We start with information relevant to the transaction, such as:
- A brief explanation of where the assets came from and the transfer's purpose.
- The transaction hash and relevant sending or receiving address.
- A record of withdrawal from an exchange or another service.
- Wallet history showing the relevant transfers.
- Other suitable evidence of the assets' origin.
We may request additional information if the initial evidence does not resolve the specific concern. We explain what remains to be clarified and consider suitable alternatives. You may obscure unrelated information if the remaining material is sufficient to assess the transaction.
Do not provide a seed phrase, private key, password, authenticator code or access to an external account. These are not required evidence of funds' origin. Send truthful and relevant information through the support channel.
Contact support@xhunter.ai from the account email and include your username and the transaction ID or hash. We review the information, request clarification where needed, and communicate the result or the next update. If review takes longer, we provide an update rather than treating silence as a final decision, where communication is permitted.
xHunter decides whether to impose, maintain or lift restrictions following an internal assessment.
xHunter may withhold the specific reasons for a decision, sources of information, internal criteria, assessment methods and individual circumstances of a review where disclosure is prohibited by applicable requirements or could enable circumvention of controls, breach confidentiality or threaten the security of users or the service. This provision does not remove any obligation to provide information that must be disclosed.
Withholding particular information does not prevent the user from contacting support and requesting reconsideration. A restriction does not itself mean confiscation of funds or cancellation of obligations relating to existing allocations.
Depending on the findings, we may release the transaction, lift restrictions, request relevant clarification, decline the transaction, refuse further service, or maintain restrictions where the circumstances or a binding requirement require them.
If service cannot continue, we consider whether funds can be returned. A return is not automatic where release is prohibited. Before any return, we must check the recipient and destination. The original sending address is not automatically suitable: it can be an exchange's technical address.
An AML flag does not itself authorize a penalty, confiscation by xHunter, or a percentage charge for unblocking funds. Ordinary transaction conditions remain described in the Pool Rules; AML review is not a separate paid unblocking service.
An AML review does not change the original end date of an existing allocation. Accruals continue to be accounted for. If technical posting is paused, all missed accruals are restored after restrictions are lifted.
The original amount remains due for return on its scheduled date. A financial restriction can still prevent an external withdrawal until release is permitted. A deposit not accepted into the pool does not earn allocation accruals.
If you disagree, request reconsideration through support and explain why, with any additional evidence. We review the decision again in light of your arguments. Where possible, a different team member performs the review; otherwise, we carry out a repeat documented review. We communicate the outcome to the extent disclosure is permitted.
Review records and supporting information are handled under the Privacy Policy. Send only relevant information. Changes to this Policy are identified by its version and date.