Fair Play & Anti-Abuse Policy
This policy explains how LINBEI RICH handles automation abuse, multi-account evasion, exploits, replay, promotion farming and other conduct that undermines game or accounting fairness.
Version 0.1 · 2026-09-30
이 페이지의 일부 내용은 다른 언어로만 제공됩니다. 이 문서는 아직 정책 초안이며 실제 운영 지역에 맞는 법률 검토가 필요합니다.
1. Fair-use principle
Users should participate through normal product flows and must not use fabricated activity, technical bypasses or coordinated conduct to create false results, duplicate benefits or unfair advantages over other users or the platform.
2. Prohibited technical abuse
Unauthorized bots, scripts, macros, auto-clickers, packet replay, API abuse, request duplication, rate-limit bypass, account or device disguise, and exploitation of race conditions, stale state, duplicate requests or other defects to obtain improper benefits are prohibited. Ordinary accessibility tools and automation expressly permitted by the platform are not prohibited merely because they are automated.
3. Multi-account and program abuse
Users must not use multiple or linked accounts, proxy operation, self-referrals, circular activity, fabricated participation or other arrangements to evade per-person limits, duplicate rewards, manipulate eligibility or create false engagement. Account, device, payment, wallet, behavioral and other reasonable evidence may be considered, but no single signal by itself establishes a violation.
4. Known errors and exploit abuse
If an obviously abnormal balance, payout, round result, PaymentOrder, reward, eligibility state or transaction status appears, a user must not knowingly repeat, automate, scale or coordinate actions to expand the benefit. Stop the affected action and preserve the round id, PaymentOrder, transaction hash, timestamp and visible state for investigation.
5. Good-faith reporting and security research
Good-faith reporting of a suspected defect or vulnerability is different from exploiting it for gain. Researchers must not access data they do not own, disrupt service, expand financial impact or continue high-risk testing without authorization. Reproducible reports should be submitted through the published security-reporting channel.
6. Review and temporary controls
When there is reasonable suspicion of abuse, account takeover, replay, duplicate claiming, accounting error or a security incident, LINBEI may preserve records, pause affected claim / wager / top-up functions, request additional verification or conduct manual review. A temporary risk control is not itself a final finding of wrongdoing.
7. Erroneous benefits and records
Benefits clearly shown by authoritative server records, Wallet / Ledger, PaymentOrder data or other reliable evidence to be duplicated, erroneous or improperly obtained may be corrected under published rules. Properly completed historical results should not be rewritten merely because they later became economically inconvenient to the platform.