- Introduction
- Overview of Terms
- Eligibility and User Account Requirements
- Restrictions on Platform Use
- Registration Process on BC.Game
- Making Deposits and Understanding Fees
- Withdrawal Process and Rules
- Payment Providers and Security Measures
- System Errors and Bet Cancellations
- General Rules for Betting and Play
- Force Majeure
- Liability Limitations
- Anti-Fraud Measures
- Intellectual Property Rights
- Governing Law and Dispute Resolution
- Contact and Customer Support
- Self-Exclusion Option
BC.Game’s Terms of Use define binding rules for casino gaming and sports betting. The agreement governs account creation, deposits, withdrawals, responsible play, and dispute handling. The operator enforces KYC, AML, and age controls. Philippine users must follow local gambling laws and age restrictions.
By accessing the website or app, users accept the Terms and related policies. The document incorporates Privacy Policy, Responsible Gambling standards, and KYC verification. Rules cover restricted territories, single-account use, and x1 turnover on deposits before cashout. Updates appear in the official Terms and Help resources.
Introduction
The Terms of Use are a legally binding contract between the user and the operator, Twocent Technology Ltd (also referred to as Twocent Tech Ltd). The Terms reference the Privacy Policy, Responsible Gambling guidelines, and KYC rules.
| Item | Details |
| Full legal entity | Twocent Technology Ltd |
| License jurisdiction | Anjouan (AOFA) |
| License No. | ALSI-202410011-FI1 |
| Latest public license verification | Noted by independent registry update on 2025-06-23 |
| Compliance updates referenced | Terms page revision 2024-10-03; AML x1 turnover in Help Center |
| Compliance contacts | Live chat in app; support email commonly listed as [email protected] |
Verification dates: License presence and operator attribution reported 2024–2025; Terms mirrors show last update 2024-10-03.
Last used 6 minutes ago
Overview of Terms
These Terms govern all use of casino, sportsbook, and ancillary services. Accessing the platform implies acceptance and ongoing compliance. Users must review revisions periodically.
Key points:
- Applicable to casino games and sports betting.
- Legally binding upon access and continued use.
- Operator may amend Terms; users should check for notices.
Change-log table
| Item | Value |
| Most recent Terms timestamp | 2024-10-03 |
| Change notifications used | Email messaging, platform banners/announcements |
| Archive/reference | Help/Terms mirrors and forum/announcement feeds |
Eligibility and User Account Requirements
Users must be of legal age, reside in a non-restricted territory, and provide accurate information. Accounts require truthful data and adherence to local laws. Philippine users must meet national age rules and verification standards.
Account requirements for Filipino players:
- Minimum age aligned with PH rules (21 for PAGCOR-licensed venues).
- One personal account; accurate identity data.
- KYC documents on request; no use from prohibited jurisdictions.
- Acceptance of AML x1 turnover before withdrawals.
Eligibility comparison table
| Jurisdiction | Legal age | PH-specific notes | Restricted territories |
| Philippines | 21 for licensed local venues; follow higher threshold for online compliance | Students barred from land-based venues; responsible gaming code applies | Check platform list; avoid prohibited states |
| UK (local site) | 18 | Separate domain (bcgame.uk); no crypto | N/A |
| USA | 21+ typical, varies by state | Access restricted | Restricted |
Age rule for PH and exclusion of students reflected in PAGCOR’s RG Code; restricted territories summarized from current lists.
Technical note: Recent lists cite restrictions including US, France, Netherlands, Australia, Ontario, and others; users should confirm availability.
Age Verification and Legal Requirements
The operator enforces age checks and identity verification. The legal casino age in the Philippines is 21 for locally licensed venues; online users should observe the stricter threshold. Acceptable documents include government ID and proof of address.
Verification steps (numbered):
- Upload government-issued ID and a selfie.
- Submit address proof if requested.
- Wait for review and approval; resubmit if clarity is insufficient.
Acceptable IDs and processing table
| ID type | Example | Typical review time |
| Government ID | Passport, PhilID, Driver’s License | ~1–24 hours |
| Address proof | Bank/utility statement | ~1–48 hours |
| Liveness check | Selfie/short video | Real-time to a few hours |
Processing times reflect current KYC guidance sources.
Last used 6 minutes ago
One Account Rule
A single-account policy prevents abuse, chargebacks, and multi-account fraud. Linked devices, IP patterns, and duplicate KYC signals trigger reviews. Violations lead to sanctions.
Consequences:
- Temporary suspension pending review.
- Confiscation of bonus funds from abuse.
- Permanent ban for repeated or intentional evasion.
- Reporting of suspected fraud under AML rules.
Technical controls include device fingerprinting and proxy checks in line with industry practice.
Restrictions on Platform Use
Prohibited actions include underage access, identity misrepresentation, bonus abuse, collusion, chargebacks, botting/scripts, VPN use to evade blocks, and multi-accounting.
Forbidden activities:
- Creating more than one account.
- Using automation or scraping tools.
- Attempting to bypass geo-blocks or KYC.
- Funding from illicit sources or sanctioned wallets.
- Harassment, cheating, or data tampering.
Violations and penalties table
| Violation | Example | Penalty / enforcement |
| Underage use | Submitting false DOB | Account closure |
| Multi-accounting | Same device/IP clusters | Ban + fund seizure on abuse |
| Bonus abuse | Risk-free cycles | Bonus void, wagering reset |
| AML breaches | No x1 turnover, STR triggers | Hold, report, or closure |
| Scripted play | Botting | Immediate suspension |
Enforcement aligns with AML policy and Terms mirrors; x1 turnover applies before cashout..
Registration Process on BC.Game
Sign-up includes acceptance of Terms, email confirmation, optional 2FA, and readiness for KYC. Multiple accounts are disallowed.
Steps:
- Open the registration page and enter email or phone.
- Confirm email/SMS; set strong password and 2FA.
- Accept Terms and Privacy Policy.
- Complete profile; be ready to submit KYC on request.
- Log in and review cashier options.
Desktop vs mobile registration
| Aspect | Desktop | Mobile app / web |
| Form layout | Multi-field panel | Condensed, step-by-step |
| 2FA prompt | Settings → Security | Inline prompt after signup |
| KYC upload | Drag-and-drop files | Camera upload, live capture |
| Approval ETA (PH) | Same-day in routine cases | Same-day in routine cases |
Mobile flows are optimized for direct camera capture; routine KYC approvals are typically within hours based on review guides.
Making Deposits and Understanding Fees
Deposits support crypto and selected local rails via third-party processors. Limits and fees vary by method, network, and compliance tier. Exchange rates apply at posting. Chargebacks breach the Terms.
Philippines—accepted payment methods:
- Cryptocurrency (BTC, ETH, USDT, etc.).
- GCash / Maya via connected providers (availability varies by account).
- Bank transfer through supported processors where offered.
Deposit comparison table (indicative)
| Method | Typical min | Fees | Posting time |
| Crypto | ₱600–₱1,200 eq. | Network fee only | Minutes after confirmations |
| GCash/Maya | ₱50–₱100 | 0–2% by provider | ~1–10 minutes |
| Bank transfer | ₱100–₱50,000 | Bank/processor fees | ~10–60 minutes |
Availability, mins, and times reported by current PH-focused guides; check cashier for live figures.
Last used 6 minutes ago
Withdrawal Process and Rules
Withdrawals require eligible balance, completion of any bonus conditions, and x1 turnover on deposits under AML rules. Extra verification may be requested for larger cashouts.
Withdrawal steps:
- Open Wallet → Withdraw and select method.
- Enter amount; confirm destination address or bank details.
- Pass KYC re-check if flagged.
- Submit; monitor status in transactions.
- Receive funds when approved.
Limits and verification table
| Tier / cap | Example cap | PHP estimate | Verification requirement |
| Per transaction | ~€5,000 | ~₱360,000–₱380,000* | Standard KYC |
| Daily | ~€10,000 | ~₱720,000–₱760,000* | Enhanced KYC |
| Alternative reports | ~€2,000/day; ~€15,000/week | ~₱144,000/day; ~₱1,080,000/week* | Method-specific |
*PHP equivalents vary with FX at payout. Figures reflect third-party reviews and mirrors; confirm live limits in cashier.
Processing notes for PH accounts: Crypto withdrawals are usually fast after on-chain confirmations; manual reviews can extend timelines. Daily caps and method availability vary by verification level and jurisdiction.
Payment Providers and Security Measures
BC.Game processes payments through integrated third-party processors and on-chain networks. The operator enforces AML controls, requires truthful KYC data, and applies a mandatory x1 wagering turnover before any withdrawal request. Chargeback liability sits with the account holder where on-chain finality or processor rules apply.
Security protocols
- HTTPS/TLS transport encryption; wallets and account pages run over secure sessions.
- Two-factor authentication via Google Authenticator for account access.
- Transaction monitoring for abnormal behavior; KYC/AML reviews on triggers.
- Provably fair RNG schemes using HMAC-SHA256/HMAC-SHA512 for in-house games.
Provider & compliance overview
| Channel / provider class | Security features | AML procedures | Certifications / notes |
| On-chain crypto rails | HTTPS wallet UI; signed tx; address whitelisting at user side | x1 turnover; source-of-funds/KYC on risk flags | Subject to Curacao AML framework via operator policy |
| Fiat on-ramp partners (where available) | Encrypted checkout; 3-D Secure where supported | KYC at processor level; chargeback review | Compliance handled by the processor in its jurisdiction |
| Internal game engines (bc game crypto casino) | HMAC-SHA256/512 provably fair verification | Auditability of bet outcomes; dispute logs | Public verification tooling referenced in help docs |
Latest published technical specifics: provably fair hashing and seed-reveal model; AML policy anchored to Curaçao legislation; 2FA support documented. Public pages do not list named third-party security audits or Philippine gateway certifications; AML/KYC controls apply to Filipino users under the operator’s policy.
System Errors and Bet Cancellations
BC.Game voids or corrects bets when a wager or payout was accepted in error, when software fails, or when force-majeure conditions distort pricing or settlement. Miscarried games trigger stake refunds or crediting of accrued value to the account.
Cancellation scenarios and balance correction
- Server malfunction during a round → automatic refund of the wagered amount.
- Incorrect odds or misprint accepted by mistake → wager voided; stake returned.
- Bets taken during technical outages or data feed faults → void and rebook if applicable.
Error handling matrix
| Error type | Typical action | Balance treatment | Resolution target |
| System crash / game miscarriage | Round canceled | Stake credited; any accrued credit paid | As soon as incident is verified |
| Palpable error / wrong odds | Bet void | Stake returned | After market audit |
| Feed/result error | Settlement corrected | Difference adjusted to true result | Post-review window (see 72-hour rule) |
General Rules for Betting and Play
Bets are accepted subject to posted rules. Settlements may be corrected for human, system, or reference-source errors. Sportsbook markets become final after the dispute window elapses. Refunds apply for canceled events per market rules.
Key points
- Bet acceptance is valid only when confirmed by the system.
- Disputes must be raised within the settlement window; settled markets are final after 72 hours.
- Refunds for canceled or void events are processed to the original balance.
Wagering rules by product (bc.game casino / sports / live)
| Product | Settlement method | Limits & notes |
| Casino RNG & Originals | Provably fair verification; round-by-round settlement | House edge published in help; malfunction voids all pays and plays. |
| Sports betting | Official or primary data source; 72-hour correction window | Voids on palpable error, feed faults, or canceled fixtures. |
| Live games | Provider feed result; interrupted rounds re-settled per provider logs | Disconnections handled per system-error policy. |
Last used 6 minutes ago
Force Majeure
Liability is limited where events outside operational control affect offers, pricing, or settlement, including natural disasters, provider outages, or network failures. Where a force-majeure error leads to incorrect acceptance, wagers may be voided.
Recognized scenarios
- Natural catastrophes disrupting providers or networks.
- Internet backbone or CDN outages affecting availability.
- Governmental restrictions or emergency directives impacting services.
Event impact overview
| Event type | Possible disruption | Platform obligation |
| Data-feed blackout | Market suspension; delayed settlement | Void or correct affected bets; notify users in-product |
| Power / hosting failure | Temporary downtime | Restore service; apply refund rules for miscarried games |
| Regulatory order | Market or geo restriction | Enforce compliance; communicate status on site banners |
Liability Limitations
The Terms exclude liability for indirect or consequential damages and confirm service is provided “as is.” Monetary caps are not specified in the public Terms; practical redress on wagers normally equals the stake or corrected payout per product rules under Curaçao law.
Scope
- Responsible for correct settlement per posted rules.
- Not responsible for indirect losses, business loss, or data loss.
- Death or personal injury liability not excluded where due to negligence.
Illustrative caps by scenario
| Scenario | Example exposure (PHP) | Typical cap logic |
| Voided sports ticket | ₱2,500 stake | Stake returned (no damages) |
| Miscarried casino round | ₱500 spin | Stake credited; accrued credit paid |
| Mispriced odds corrected | ₱1,000 single | Correct to true odds or void; no consequential loss |
Anti-Fraud Measures
The operator prohibits fraudulent conduct, multiple accounts, device-assisted play, and advantage play. Suspected manipulation triggers investigations, withheld payments, void bets, and account closure; users must reimburse losses caused by fraud.
Prohibited behaviors
- Bonus abuse, hedging to clear wagering, or low-margin bet loops (advantage play).
- Identity theft or fake KYC; third-party payment methods.
- Chargeback abuse or transactional obfuscation.
Detection & penalties
| Fraud type | Monitoring methods | Penalties |
| Multi-accounting | Device, IP, and behavioral checks | Closure; fund confiscation; ban |
| Bonus abuse / irregular play | Pattern analysis; turnover review | Withhold withdrawals; seize winnings; close account |
| Payment fraud | KYC triggers; fee sufficiency checks on-chain | Block payouts; void wins; report to authorities |
Intellectual Property Rights
All site code, marks, and content remain the operator’s property. Users gain no IP rights and must not copy, reverse engineer, or republish content or software without written consent.
What counts as infringement
- Using BC.Game trademarks without permission.
- Replicating site code, game logic, or art assets.
- Republishing help-center content as original.
Protected materials & usage
| Material | Allowed use | Prohibited use |
| Trademarks / logos | Referencing the brand in reviews | Commercial use without consent |
| Game UIs, assets | Personal gameplay and screenshots with attribution | Redistribution or resale |
| Website code | Normal user access | Reverse engineering or derivative works |
Last used 6 minutes ago
Governing Law and Dispute Resolution
The Terms designate Curaçao law and courts for disputes. Users should first contact support; unresolved matters may proceed under the governing-law clause.
Process
- File a complaint via support channels with evidence.
- Await internal review and settlement correction if due.
- Escalate under Curaçao jurisdiction if unresolved.
Jurisdiction comparison (reference)
| Jurisdiction named | Procedure note | Typical timeline |
| Curaçao (current ToS) | Civil claim in local courts; English text governs | Varies by filing; internal review first |
Contact and Customer Support
Official channels include 24/7 live chat via the Help Center and the published support email for formal complaints.
Channels
- Help Center live chat: help.bc.game (Support collection).
- Email: [email protected] for dispute filings.
- Knowledge base articles for Terms, AML, and Responsible Gambling.
Service profile
| Method | Average response | Hours | Use case |
| Live chat | Near-real-time | 24/7 | Account help, settlement checks |
| Same-day to 48h | 24/7 intake | Formal complaints, evidence attachments |
Self-Exclusion Option
Self-exclusion is available for users who need a break from gambling. Responsible-gaming guidance is documented, and support agents can action account-level restrictions on request.
How to activate
- Open account Help Center or profile settings and request self-exclusion.
- Choose a duration (temporary block or permanent closure).
- Confirm identity; await confirmation from support.
- Do not attempt to bypass restrictions during the exclusion period.
Options and timing
| Option | Duration | Reversibility | Processing note |
| Cooling-off | 24 hours–30 days | Auto-reopen after period | Request via chat; immediate effect |
| Time-out | 1–6 months | Reopen by written request after expiry | ID check may apply |
| Self-exclusion | 6–12 months | Irreversible until term ends | Support-confirmed; blocks deposits/bets |
| Permanent closure | Indefinite | Not reversible | Final account lock |
BC.Game also instructs users to notify the platform if they self-exclude elsewhere, ensuring cross-provider awareness for safer play.