1. GENERAL PROVISIONS
1.1 Purpose of the Document
This policy defines the principles and measures applied by Bazonix.com ("Platform") to prevent financial crimes, protect users, and maintain the integrity of the cryptocurrency ecosystem.
1.2 Platform Commitments
Bazonix.com strives to comply with advanced international standards and recommendations in the field of anti-money laundering and countering the financing of terrorism (AML/CFT), including the recommendations of the FATF (Financial Action Task Force).
1.3 Policy Implementation Principles
The Platform applies a risk-based approach that balances operational security with the convenience of service for bona fide users.
2. RISK MANAGEMENT SYSTEM
2.1 Automatic Transaction Screening
Bazonix.com uses advanced technological solutions to monitor and assess risks associated with each cryptocurrency transaction. All incoming and outgoing transfers are analyzed in real-time.
2.2 Multi-factor Risk Assessment
The system is based on a comprehensive analysis that takes into account the following parameters:
- History of cryptocurrency asset movements
- Connection to known high-risk addresses
- User behavioral patterns
- Volume and frequency of operations
- Geographical factors
2.3 Risk Categories
Each transaction is assigned a risk level on a scale from 0% to 100%:
- Low risk (0-15%): operation is conducted in standard mode
- High risk (16-100%): operation is suspended until KYC procedure is completed
3. IDENTIFICATION AND VERIFICATION PROCEDURES
3.1 KYC Procedure Activation Triggers
The customer identification procedure (KYC) is automatically initiated under the following circumstances:
- Transaction risk level exceeds 15%
- Signs of transaction structuring are detected
- Connection with suspicious addresses or tags is discovered
- A request is received from competent authorities
3.2 High Risk Markers
Detection of any of the following tags in the history of crypto assets leads to immediate transaction blocking:
- DARKNET (connection to shadow markets)
- FRAUD (fraudulent schemes)
- RANSOMWARE (ransomware programs)
- SANCTIONS (sanction lists)
- MIXER (mixing services)
- THEFT (stolen funds)
- ILLEGAL_SERVICES (illegal services)
- TERRORISM (terrorism financing)
3.3 Verification Levels
3.3.1 Basic Verification
- Email address
- IP address
3.3.2 Standard Verification
- Personal data (full name, date of birth)
- Identity document (passport/ID card)
- Selfie with document
3.3.3 Enhanced Verification
- Information about the source of funds
- Additional evidence of transaction legitimacy
4. VERIFICATION PROCEDURE
4.1 Suspension of Operation
When signs of increased risk are detected, the operation is automatically suspended.
4.2 Data Provision
The user must:
- Contact Bazonix.com support, indicating the transaction ID
- Provide requested documents and information through a secure communication channel
- Provide necessary explanations regarding the nature and purpose of the operation
4.3 Analysis and Decision Making
The Bazonix.com security team:
- Verifies the authenticity of the provided documents through partners who have all legal rights to store and process personal data
- Compares the received information with transaction data
- Conducts additional checks if necessary
- Makes a reasoned decision to unblock, return, or reject the operation
5. Cooperation with Authorities
Bazonix.com interacts with authorized bodies within the framework of AML/CFT legislation and can transfer information upon official request.
6. FINAL PROVISIONS
6.1 Changes to the Policy
Bazonix.com regularly updates this policy in accordance with changes in legislation and best practices in the industry. Updates are published on the official website and come into effect 14 days after publication.
6.2 User Notification
The Platform notifies registered users about policy changes via email, official blog, and other communication channels.
6.3 Security Priority
Bazonix.com strives to provide a secure environment for all users and reserves the right to apply any reasonable measures to prevent illegal activities, even if such measures are not explicitly described in this policy.
Last update date: April 10, 2025