1. Scope
LuckyHash is a wallet-based gaming platform. We do not operate conventional player deposit balances, but the Platform still processes blockchain payments, game sessions, gift redemptions, recoveries, refunds, settlements, and support requests that may require AML, sanctions, fraud, or abuse review.
This policy applies to luckyhash.win, LuckyHash game pages, gift-code flows, migration-reward flows, referral or partner campaigns, support flows, recovery tools, payout flows, and related services operated by LuckyHash.
2. Compliance Position
LuckyHash may use risk-based controls intended to reduce the use of the Platform for money laundering, terrorist financing, proliferation financing, sanctions evasion, fraud, stolen funds, abuse, illegal gambling, or other unlawful activity.
Any AML/CFT/FPADM registration, filing, or review statement about the Operator should be read only within that limited compliance scope. It is not a gambling licence, game approval, player-fund guarantee, solvency approval, or endorsement of game outcomes.
3. Risk Controls
LuckyHash may use internal records, public blockchain records, third-party providers, manual review, and infrastructure controls to review activity. Depending on the circumstances, controls may include:
- wallet control checks and wallet-session matching;
- blockchain transaction and payment-reference review;
- duplicate, mismatched, stale, replayed, or suspicious payment-reference checks;
- IP address, location or country, device, browser, and session signals;
- sanctions, AML, fraud, and abuse-prevention screening where relevant and available;
- manual support, recovery, refund, settlement, and payout review where needed.
We do not publish exact thresholds, scoring rules, fraud signals, review triggers, vendor lists, or internal procedures because doing so would weaken Platform integrity.
4. User Responsibilities
You must not use the Platform for money laundering, sanctions evasion, fraud, stolen funds, market abuse, illegal gambling, tax evasion, source-of-funds concealment, or any unlawful purpose.
You must not submit copied, bought, stale, reused, unrelated, or third-party transaction references, signatures, screenshots, wallet proofs, identity documents, source-of-funds explanations, or support evidence as your own.
Any information you provide for support, recovery, compliance, refund, settlement, or dispute purposes must be genuine, complete, accurate, and not misleading.
5. Verification and Source-of-Funds Review
LuckyHash may request additional information before accepting a payment, serving a session, completing a gift redemption, processing a recovery, issuing a refund, releasing a settlement, or resolving a dispute.
Requested information may include wallet control proof, transaction details, jurisdiction information, identity information, source-of-funds or source-of-wealth information where relevant, screenshots, explanations, or other evidence needed to resolve the review.
Forged, altered, incomplete, misleading, or third-party documents or evidence may result in denied access, voided sessions, blocked wallets, denied recoveries, withheld settlements, account or wallet restrictions, and reports to relevant authorities where appropriate.
6. Restricted Activity
LuckyHash may pause, reject, limit, void, hold, review, or block activity where we identify or reasonably suspect:
- restricted-jurisdiction access or attempted circumvention of access controls;
- sanctions, AML, fraud, wallet-risk, stolen-funds, or source-of-funds concerns;
- payments from or payouts to unrelated wallets;
- duplicate, copied, replayed, stale, mismatched, or suspicious blockchain transactions;
- abuse of gift codes, partner rewards, migration rewards, referrals, recoveries, or promotions;
- software manipulation, automation, scraping, bots, exploit attempts, or unauthorized API use;
- abnormal volume, velocity, clustering, patterning, collusion, or other suspicious behavior;
- legal, regulatory, tax, accounting, security, or operational concerns.
7. Outcomes of Review
Depending on the facts, LuckyHash may allow the activity, request additional information, deny the activity, void a session, deny a recovery, block a wallet, restrict future access, refund a qualifying unserved payment, hold or reject a settlement, retain relevant records, or report activity where required or appropriate.
Submitting a public blockchain transaction alone does not guarantee entitlement to play, recovery, refund, gift redemption, or payout. The transaction must match supported chain data, LuckyHash payment intent, internal session records, eligibility rules, and risk controls.
8. Recordkeeping and Privacy
LuckyHash may retain AML, sanctions, fraud-prevention, support, recovery, transaction, wallet, session, audit, tax, accounting, and compliance records for as long as reasonably necessary or legally required.
More information about data categories, retention, sharing, cookies, and user requests is available in the LuckyHash Privacy Policy.
9. Contact
For AML, compliance, support, recovery, refund, settlement, or dispute requests, contact [email protected].