xHunterAI

Hati hii inapatikana kwa Kiingereza na Kirusi.

Privacy Policy

v1.2

Pakua .md

1. Scope and contact

This Policy explains how xHunter handles information when you use xhunter.ai, the account, analytics, trader pool, partner program and linked Telegram bot. “We” means the team providing xHunter. For privacy questions and requests, contact support@xhunter.ai.

The Cookies and Browser Storage supplement describes information stored on your device. The AML Policy describes transaction reviews and information requested about the origin of funds.

2. Account and security information

We process your email address, username, password hash, account ID, registration date, email-confirmation status, chosen language and account settings. If you provide a first name or surname, we record them in the profile. We can use the first name to address you in messages.

We store passwords as hashes rather than readable passwords. When two-factor authentication is enabled, the service stores the information needed to check authenticator codes. Email confirmation, password recovery and Telegram linking also require confirmation records and codes or code hashes.

Security and request records can include IP addresses, browser and operating-system information, time, requested function, route, method and technical metadata. These records support account access, security, troubleshooting and transaction handling. Login notifications sent to a linked Telegram account can include the login IP and browser.

3. Analytics information

We process the tokens you check, network and address, report data, scores and check times. We also store wallet addresses you choose to track, your labels, alert settings, alert events and delivery status. Labels are free text: do not include unnecessary information about other people.

The analytics service uses a user ID. It does not keep a separate copy of your email or name. The analytics service obtains information about access level and email confirmation from the account service to provide the appropriate features and limits.

We use IP-based counters for free-tier request limits. Technical request counters help prevent excessive use.

4. Funds, transactions and AML records

Financial records include deposit addresses assigned to the account, sending addresses, withdrawal addresses, blockchain hashes, assets, networks, amounts, timestamps, fees, exchange rates, internal USDT balances, USDT allocations, USDT accruals, USDT partner rewards and transaction statuses.

A blockchain address and transaction history can become associated with your account when you deposit or withdraw. Blockchain transfers are publicly recorded; removing an account record from a service does not remove a transaction from a blockchain.

During an AML review, we may process your explanation of a transfer, exchange withdrawal records, wallet history, transaction hashes and other relevant evidence of origin. We also keep review correspondence and decisions. The service uses its own tools and external tools for transaction assessment. We do not publish technical methods or exact risk thresholds.

5. Partner relationships and visibility

We record your referral ID, referrer, place in the referral structure, level, allocation-related turnover and partner rewards.

Authorized upline partners can view available information in their accessible structure up to five lines: username, masked email, personal and branch turnover, team size and position. Missing registration dates are not inferred. Available list search does not expose an unsupported global search or export. Linked Telegram notifications can tell an upline partner that a new partner has joined and include their name and line.

Your referrer's referral ID is shown in the profile. Administrative functions can move a user or a team within the structure.

6. Service providers and other recipients

To deliver the service, the following categories of recipients handle information:

  • Hosting, database, backup and technical infrastructure providers: information stored or processed within the hosted services.
  • Email delivery providers: recipient email, name if used, and the relevant email content and confirmation or recovery link.
  • Telegram: chat ID and message content, including selected alerts, login notifications, transaction notifications and partner notifications.
  • Token-data and security-data providers: token or tracked wallet addresses, networks and the service's API credentials used for server-to-server requests. These analytics requests do not include the user's account ID, email or client IP.
  • Blockchain infrastructure providers: addresses and network information needed to detect transfers and operate the payment service.
  • AML assessment tools: addresses, transaction information and associated review information needed for the relevant assessment.
  • Upline partners: the limited information described in section 5.

The browser also makes direct requests to Google Fonts and the hosts of token-logo images. Those recipients can see the connection IP address and technical request information. This differs from analytics requests made by our server.

Opening an external link takes you to a third-party service. That service's own data practices apply to your interaction there.

7. Team access and purposes

Support, administrative and finance functions have access to information needed for their work. This can include locating account and transaction records, handling access recovery, reviewing transfers, processing withdrawals, updating financial statuses and managing the referral structure.

We use information to create and operate accounts; provide analytics and notifications; apply access limits; account for funds and rewards; process deposits and withdrawals; handle security incidents and AML reviews; and respond to requests and complaints.

8. Retention and device storage

Some technical information has short retention periods: analytics IP counters are retained for two days, daily token-limit records for seven days, and technical rate-limit records for one day. Alert events are retained for 30 days. Tracked wallets and alert rules remain until the user deletes them. Check history is retained rather than cleared when an access level changes.

We hold account information, transaction history, security logs and backup records within the respective service systems. Contact support about retention or removal of particular information. A support request does not itself erase public blockchain records.

On-device storage has separate lifetimes and logout behavior, explained in the Cookies and Browser Storage supplement.

9. Requests and account changes

Contact support to ask about your information, request correction, receive available account or transaction information, or request deletion. Explain which account and information the request concerns. Self-service account deletion is not available. Disabling an account and deleting its data are different actions.

We may need to confirm that a request comes from the account holder before disclosing or changing account information. Never send a password, authenticator code, seed phrase or private key as evidence.

10. Security and updates

Security measures include password hashing, encrypted connections, access roles, optional user two-factor authentication and server-side handling of provider credentials. These measures do not make online storage or communications risk-free.

This Policy may be updated when the service changes how it handles information. The version and date are shown above.