1. Operating Entity and Legal Notice
The Platform is owned and operated by 3-102-965671 Sociedad de Responsabilidad Limitada, a limited liability entity organized under the laws of the Republic of Costa Rica, registered at San Jose, Canton 09 Santa Ana, Pozos, Centro Corporativo Forum Uno, Edificio E, Primer Piso, Oficinas REB Abogados, Costa Rica (the "Operator", "LuckyHash", "we", "us", or "our").
LuckyHash is a crypto-only, non-custodial, software-driven gaming platform. The Platform does not operate as a bank, financial institution, deposit-taking institution, custodian, exchange, broker, money transmitter, or stored-value wallet provider.
2. Eligibility
You may use the Platform only if all of the following are true:
- You are at least 18 years old and at least the legal age of majority in your jurisdiction.
- You have full legal capacity to enter into these Terms.
- You are not located in, resident in, ordinarily resident in, or acting on behalf of a person located in or resident in a prohibited jurisdiction.
- Your use of crypto-based gaming is lawful in your jurisdiction and does not require an authorisation, licence, registration, or approval that LuckyHash does not hold.
- You are using a wallet that you lawfully control.
- You are not subject to sanctions, embargoes, asset freezes, or other legal restrictions that prohibit us from providing services to you.
We may refuse, suspend, block, limit, void, review, or reverse access, sessions, settlements, recoveries, or other Platform activity where we believe these requirements are not met.
3. Prohibited and Restricted Jurisdictions
You must not use the Platform if you are located in, resident in, ordinarily resident in, or acting on behalf of a person in:
- The Republic of Costa Rica, unless and until the Operator separately confirms that Costa Rican resident participation is legally, tax, and operationally cleared.
- Any jurisdiction subject to comprehensive sanctions, embargoes, or similar restrictions.
- Any jurisdiction where online gambling, crypto gambling, chance-based digital games, or the relevant blockchain payment activity is prohibited.
- Any jurisdiction or market that LuckyHash designates as restricted based on legal, payment, abuse, risk, or operational considerations.
We may use geolocation, country/IP controls, IP reputation signals, device/session signals, wallet activity signals, blockchain records, manual review, third-party tools, and user-provided information to help apply these restrictions. These controls are risk-based and may not be exhaustive. We do not publish our full control logic, thresholds, or review criteria because doing so would weaken platform integrity.
Using VPNs, proxies, remote desktop tools, relays, false account information, wallet routing, third-party wallets, or any other method to bypass restrictions is a material breach of these Terms and may result in denied play, voided sessions, withheld or reviewed settlements, account or wallet blocking, and any other remedy available to us.
4. Wallet-Based, Non-Custodial Model
LuckyHash does not maintain persistent spendable player wagering balances. Each purchase, wager, finite game session, or gift purchase is funded by a blockchain transaction from a player-controlled wallet to an Operator-controlled payment wallet. The Platform records the payment, validates the corresponding game or gift intent, and creates or finalises the related session or artefact.
Wallet connection and session data are used for authentication, payment matching, support, fraud prevention, recovery, dispute handling, and compliance. This does not create a custodial account balance.
Operational records may still exist for pending settlements, recovery items, refunds, affiliate/referral obligations, support claims, audit logs, tax/accounting records, abuse prevention, or compliance review. These records are not ordinary player deposit balances and are not freely withdrawable by users.
5. Supported Payment Rails
The Platform may support payments through one or more public blockchain networks, including the XRP Ledger ("XRPL") and Solana.
XRPL payments are validated using on-ledger transaction data and LuckyHash payment references, such as invoice-style identifiers, destination addresses, destination tags where applicable, memos, token/currency data, amount data, and sender/destination information.
Solana payments are validated using submitted transaction signatures and on-chain transaction data, including signer or fee-payer information, destination wallet, token mint or native SOL transfer data, amount, memo or payment intent where applicable, and duplicate-use controls.
Supported chains, tokens, mints, amounts, games, and payment methods may change over time. A token symbol, wallet UI label, screenshot, or user-provided transaction description is not sufficient proof of payment. We rely on supported chain records and our internal payment/session records.
You are responsible for using the correct chain, token, destination wallet, payment reference, memo, amount, and wallet. Payments sent to an unsupported chain, wrong address, wrong token mint, missing reference, wrong amount, or unrelated third-party address may be unrecoverable or may require manual review.
6. Market, Swaps, and Liquidity Pools
The Market is a non-custodial interface for viewing, preparing, signing, and verifying transactions that interact with public blockchain liquidity systems, including XRPL AMM pools, order books, pathfinding, and related ledger-native functionality.
LuckyHash is not an exchange, broker, dealer, financial institution, custodian, market maker, investment adviser, or liquidity provider. LuckyHash does not hold user assets for Market activity, does not operate the underlying XRPL DEX or AMM pools, does not guarantee execution, and does not control prices, pool reserves, liquidity, slippage, route availability, ledger settlement, wallet behaviour, or third-party infrastructure.
All Market transactions are initiated and signed by the user through a third-party wallet. You are solely responsible for reviewing the transaction, token, issuer, amount, route, slippage, fees, destination, LP position, and any wallet prompt before signing. Once submitted and confirmed on-chain, blockchain transactions are generally final and cannot be reversed by LuckyHash.
Quotes, estimated output amounts, minimum received amounts, price impact, pool values, balances, fees, routes, and similar Market information are estimates based on data available at the time shown. Actual execution may differ because of ledger timing, liquidity changes, slippage, fees, path changes, competing transactions, wallet behaviour, RPC/provider latency, or blockchain conditions.
Providing liquidity involves risk. LP token value, pool composition, token prices, fee income, and withdrawal value can change over time. You may experience impermanent loss or other losses, and LP fee income or promotional rewards are not guaranteed.
Liquidity Game rewards and Market promotions are promotional only. A swap or LP deposit may qualify only if the active campaign configuration, thresholds, caps, lookback windows, no-sell/no-withdraw rules, and other eligibility checks pass after ledger settlement. LuckyHash may modify, pause, end, or review promotions according to these Terms and applicable campaign rules.
Market information is provided for interface and operational purposes only and is not financial, investment, trading, tax, legal, or professional advice. You are solely responsible for determining whether any swap, token purchase, sale, LP deposit, LP withdrawal, or related transaction is appropriate and lawful for you.
7. XRPL Fairness Beacon and Game Outcomes
The XRP Ledger generates LuckyHash game outcomes in combination with the platform's backend game engine, using recorded payment/session data and provably fair randomness inputs. Smart contracts do not perform live on-chain game reveals.
The XRP Ledger is the Platform's fairness beacon. Unless a specific game page or published fairness method says otherwise, LuckyHash uses a future XRPL ledger close and XRPL ledger hash as the public randomness source for game outcomes, regardless of whether the payment rail used for the session was XRPL, Solana, or another supported payment rail.
In general terms, the Platform commits to or records a payment/session identifier, waits for the relevant future XRPL ledger data, and combines those inputs with game-specific indexes or rules to derive the outcome. The exact method may vary by game type and version and should be read together with the applicable published fairness explanation for that game.
The purpose of the XRPL fairness beacon is to use public ledger data that neither the player nor the Operator can know or choose when the relevant commitment is made. The Operator may not retroactively change the agreed rules for an accepted and recorded game session.
Where there is a conflict between marketing summaries and the detailed published fairness method or backend audit records for a specific game/session, the detailed game/session records and published method control, subject to applicable law and review.
8. Session Finalization, Recoveries, and Missing Play Support
Validated payments may only be consumed once. LuckyHash uses duplicate detection, idempotency controls, payment-intent matching, and session records to reduce the risk of duplicate plays, duplicate recoveries, or duplicate payouts.
Network congestion, wallet failures, RPC/provider latency, browser interruption, ledger delays, backend errors, or other technical issues may temporarily prevent a paid session from displaying or completing immediately.
If a payment can be matched to supported on-chain data and internal LuckyHash records, LuckyHash may finalise the original session, restore access to the playable session, issue a recovery gift, issue a refund, mark the matter as handled, or route it to manual review.
Missing Play self-support and automated recovery may differ by chain, token, game, and payment flow. XRPL and Solana recovery support may use different verification paths. If an automated tool cannot safely verify a payment, wallet ownership, game intent, amount, token, signer, memo, or duplicate-use status, we may deny the claim or escalate it to manual review.
Submitting a public transaction hash or Solana signature alone does not prove entitlement. We may require wallet connection, wallet ownership proof, a matching signer or sender, a matching destination, a matching token/mint, a matching amount, a matching payment intent, internal session records, and other evidence before recovering or settling a session.
9. Payouts, Settlements, and Refunds
Because LuckyHash does not maintain persistent player wagering balances, conventional account withdrawals do not exist.
Outbound transfers from the Platform are limited to valid game settlements, winnings, system recovery payouts, refunds for unserved or failed sessions, affiliate/referral payments where applicable, and other operational payments recognised by LuckyHash records.
We normally send winning payouts to the relevant player-controlled wallet associated with the session, payment, or redemption. We may reject or review requests to send winnings, refunds, recoveries, or settlements to unrelated third-party wallets.
Users pay inbound blockchain network fees required to submit their own transactions. LuckyHash normally covers outbound network fees for platform-originated settlements, recoveries, or refunds, unless otherwise stated.
Purchases and wagers are final once validated and accepted for play, except where a backend or payment-matching issue prevents a valid paid session from being served or where LuckyHash determines that a refund, recovery, or manual correction is appropriate.
10. Risk Controls, Abuse Prevention, AML, and Review Rights
LuckyHash uses risk-based operational controls to protect the Platform, players, payment flows, and the Operator. These controls may include duplicate transaction detection, payout idempotency, payment-intent verification, wallet ownership checks, session integrity checks, browser/session/device signals, IP and geolocation information, Cloudflare country/IP controls, blockchain evidence, manual review, and other internal or third-party risk tools.
LuckyHash may pause, defer, limit, reject, void, or manually review any payment, play session, gift, recovery, refund, or payout where we identify or suspect:
- restricted-jurisdiction access;
- sanctions, AML, fraud, abuse, or wallet-risk concerns;
- VPN, proxy, relay, remote access, or circumvention activity;
- duplicate, copied, replayed, stale, mismatched, or suspicious blockchain transactions;
- payment from or payout to an unrelated wallet;
- software manipulation, automation, scraping, bots, exploit attempts, or unauthorised API use;
- abnormal volume, velocity, patterning, clustering, arbitrage, or collusion;
- technical inconsistency between blockchain records and internal session records;
- regulatory, legal, tax, accounting, or operational concerns.
We may require identity verification, wallet ownership proof, source-of-funds/source-of-wealth information, additional transaction details, jurisdiction information, or other information before accepting a payment, serving a session, releasing a settlement, processing a recovery, or resolving a dispute.
We do not guarantee that risk controls will detect every issue. We also do not disclose exact thresholds, scoring rules, fraud signals, review triggers, or internal procedures.
11. Responsible Gaming and Self-Exclusion
LuckyHash is intended for lawful adult entertainment only. You should not use the Platform if gambling, crypto wagering, losses, frequency of play, or attempts to recover losses are causing stress, financial harm, relationship issues, work issues, loss of control, or any other personal risk.
If you believe you are at risk, are losing control, or need help limiting or stopping your use of the Platform, contact us at [email protected]. We may provide account, wallet, device, session, or access-limitation support and may direct you to appropriate external support resources.
LuckyHash offers self-exclusion. A user may request temporary or unlimited self-exclusion from real-value play. An unlimited self-exclusion request is permanent and not reversible. If you request unlimited self-exclusion, we will treat it as a final instruction not to permit you to return to real-value play. Please contact us via [email protected].
We will implement self-exclusion technically to the extent reasonably possible, including by applying blocks or restrictions to known wallets, sessions, identifiers, contact details, device/session signals, and other available risk-control signals. Because LuckyHash is non-custodial and wallet-based, and because users may attempt to use new wallets, devices, networks, or identities, we cannot guarantee that any technical self-exclusion control will prevent every possible future access attempt. Attempting to bypass a self-exclusion materially breaches these Terms.
We may also restrict, suspend, or refuse access where we identify signs of risky play, self-exclusion circumvention, abuse of recovery/support flows, or other conduct inconsistent with responsible use of the Platform.
12. User Conduct
You must not:
- use the Platform from a prohibited or restricted jurisdiction;
- bypass or attempt to bypass geolocation, Cloudflare, wallet, device, or other controls;
- use another person's wallet or transaction without authorisation;
- submit copied, bought, stale, reused, unrelated, or third-party transaction hashes or signatures as your own;
- manipulate, attack, reverse engineer, overload, scrape, automate, or interfere with the Platform;
- exploit bugs, timing issues, UI mismatches, rounding differences, RPC inconsistencies, or recovery flows;
- submit false, misleading, incomplete, or manipulated support or compliance information;
- use the Platform for money laundering, sanctions evasion, fraud, market abuse, illegal gambling, or any unlawful purpose.
Violation of this section may result in session denial, voided play, payout hold, recovery denial, wallet blocking, data retention for compliance purposes, and any other remedy available to the Operator.
13. Blockchain and Wallet Risks
Blockchain transactions are generally irreversible. You are responsible for your wallet, private keys, seed phrases, wallet software, network selection, token selection, transaction review, fees, memos, destination tags, and destination addresses.
LuckyHash is not responsible for losses caused by:
- user wallet compromise or user signing mistakes;
- wrong-chain, wrong-token, wrong-mint, wrong-address, missing-memo, or missing-tag transfers;
- wallet software bugs or incompatibility;
- RPC/provider outages or latency;
- blockchain congestion, reorgs, forks, halted networks, failed transactions, dropped transactions, or delayed finality;
- phishing, spoofed websites, malware, social engineering, or fake LuckyHash support;
- third-party wallet, infrastructure, explorer, analytics, or blockchain service failures.
14. Game Availability, Limits, and Changes
LuckyHash may add, remove, disable, modify, pause, or limit games, tokens, chains, wallets, cards, sessions, promotions, payouts, recovery paths, and platform features at any time.
Maximum wagers, maximum payouts, card prices, supported tokens, game parameters, volatility, odds, multipliers, recovery rules, and settlement behaviour may change for future sessions. Accepted and recorded sessions will not be retroactively changed except where required to correct an error, comply with law, resolve abuse, or enforce these Terms.
Promotions, gifts, free plays, referral rewards, and special campaigns may have separate rules. If campaign-specific rules conflict with these Terms, the more restrictive rule applies unless expressly stated otherwise.
15. Intellectual Property
The Operator or its licensors own all software, game mechanics, visual interfaces, designs, graphics, logos, trademarks, audio, written content, backend logic, fairness methods, and other Platform materials.
You receive only a limited, revocable, non-exclusive, non-transferable right to access and use the Platform for lawful personal entertainment in accordance with these Terms.
You may not copy, reproduce, modify, redistribute, resell, scrape, frame, mirror, reverse engineer, exploit, or create derivative works from the Platform except where expressly permitted by law or by written permission from the Operator.
16. Disputes and Evidence
In any dispute involving payment validation, game outcome, recovery, refund, or payout, relevant evidence may include:
- XRPL transaction hashes and ledger data;
- Solana signatures and on-chain transaction data;
- payment references, memos, destination tags, token/mint data, sender/signer/destination data, and amounts;
- internal payment, session, game, gift, recovery, support, payout, and audit logs;
- published fairness method and game-version data;
- wallet connection, session, IP/geolocation, device, abuse-prevention, and compliance records.
Public blockchain records are necessary but may not be sufficient on their own. LuckyHash uses internal records to determine whether a blockchain transaction corresponds to a valid accepted session, recovery, gift, refund, or payout.
17. Disclaimer of Warranties
The Platform is provided on an "as is" and "as available" basis. To the maximum extent permitted by applicable law, the Operator disclaims all warranties, express or implied, including warranties of merchantability, fitness for a particular purpose, uninterrupted availability, non-infringement, accuracy, profitability, regulatory availability in your jurisdiction, or error-free operation.
We do not guarantee that:
- the Platform will always be available;
- every wallet or network will work without delay;
- every payment can be recovered;
- every payout will be instant;
- your jurisdiction permits your use of the Platform;
- third-party blockchain, wallet, RPC, Cloudflare, analytics, or infrastructure services will operate without interruption.
18. Limitation of Liability
To the maximum extent permitted by applicable law, the Operator, its directors, officers, owners, employees, contractors, service providers, and affiliates will not be liable for indirect, incidental, consequential, special, punitive, exemplary, or lost-profit damages arising from or related to the Platform.
For any claim arising out of a specific validated play session, the Operator's maximum aggregate liability will not exceed the amount the user paid for that specific session, unless applicable law requires a higher amount.
Nothing in these Terms excludes liability that cannot lawfully be excluded.
19. Privacy and Data
LuckyHash may process wallet addresses, blockchain transaction data, session records, support communications, IP/geolocation data, device/session signals, compliance information, and other information necessary to operate the Platform, prevent abuse, resolve disputes, meet legal obligations, and protect users and the Operator.
We may retain records where necessary for legal, compliance, AML, tax, accounting, security, abuse-prevention, dispute-resolution, and audit purposes.
Do not submit sensitive identity or financial documents unless requested through an official LuckyHash support or compliance channel.
20. Changes to These Terms
We may update these Terms from time to time. We will post updated Terms with a revised "Last Updated" date. Continued use of the Platform after updated Terms are posted constitutes acceptance of the updated Terms.
Material changes apply prospectively unless required by law, necessary for security, necessary to prevent abuse, or necessary to correct an error.
21. Governing Law and Forum
These Terms and any dispute arising out of or relating to the Platform are governed by the laws of the Republic of Costa Rica, without regard to conflict-of-law rules.
Subject to any mandatory law that cannot be waived, you agree to submit to the competent courts of San Jose, Costa Rica for disputes arising under or related to these Terms or the Platform.
22. Contact
For support, compliance, technical issues, legal notices, or dispute investigations:
- Email: [email protected]
- Legal Entity: 3-102-965671 Sociedad de Responsabilidad Limitada
- Address: San Jose, Canton 09 Santa Ana, Pozos, Centro Corporativo Forum Uno, Edificio E, Primer Piso, Oficinas REB Abogados, Costa Rica