Most people don't even read a casino's terms of service when creating an account; they create an account, make a deposit, and start playing. So this whole "No-KYC" thing becomes a huge trap, not a blessing. This is because many people deposit large sums of money consecutively, play, and when they withdraw, the amount is very high And casinos don't like paying out large sums to people who win consistently, so they'll look for something to use as a way to retain the person's funds.
Hello,
Thank you for taking the time to review our website in detail and raising this point. Your concern is completely valid, and we appreciate the scrutiny—it helps us keep our service clear, transparent, and accountable.
Here is the explanation regarding what happened and the steps we have taken:
1. Conflicting AML / ToS Template (Now Fixed)The clause you highlighted in our Anti-Money Laundering (AML) / Terms policy was carried over from an initial generic compliance template that conflicted directly with our platform's intended operating model. We recognize how this created confusion and appeared contradictory to our "No-KYC" announcement.
We have reviewed and revised our policies on the website to reflect our actual operations:
DEBET77 does not require identity documents (ID, passport, utility bills, or SoF) for standard crypto deposits, gameplay, and withdrawals.2. Our Stance on Withdrawals and Big WinsWe completely understand the community's frustration with platforms that promise privacy only to spring KYC requirements once a player attempts to withdraw winnings. We want to state clearly:
- We do not use KYC as a retention tactic or arbitrary barrier against winning players.
- Crypto withdrawals are handled via automated on-chain batching without surprise document requests.
- To combat abuse and illicit wash trading without invading player identity, we rely strictly on standard gameplay/wager requirements (e.g., standard 1x deposit turnover) rather than identity confiscation traps.
3. Licensing UpdateFor full transparency, our official gaming licensing application is currently a work in progress. We are finalizing regulatory steps and will update the community and this thread as soon as the verifiable license information is active.
Thank you again for pointing out this discrepancy so we could resolve it immediately. We welcome any further feedback or questions from the community.
Best regards,
No way a casino named 'DEBET77.SPACE' turns out to be legit
the .space domain extension is also one of the cheapest, it's like $1 on namecheap where they got it from.
broke ass "casino" that can't even afford a proper .com domain
https://talkimg.com/images/2026/09/08/UeKIto.pngthey are 100% gonna be able to afford paying wins /s
They put 'LICENSED' in their footer but forgot to display the license itself. Probably weren't aware that this is a prerequisite for being licensed.
same for the "provably fair" part, they don't even have any originals in the first place.
this is most likely a scam casino, so i'll advise everyone to stay away from them.
Hello,
Thank you for your feedback. We appreciate the community’s vigilance in reviewing new platforms, and we want to address each of the points you raised directly:
1. Regarding the Domain Extension (.space) and Migration PlanOur plan has always been to operate on our primary `.com` domain. However, because that specific `.com` domain was previously owned and used by another brand, we are currently waiting on full domain history clearance, security checks, and DNS reputation propagation to ensure there is zero baggage, past abuse, or residual issues from the previous owner before we migrate our live user traffic to it. Using `.space` is a temporary staging setup to launch the platform while that due diligence process is finalized.
2. Licensing Status (Footer Correction)You are right to call this out. Our official gaming license application and regulatory compliance are currently a work in progress. Displaying "Licensed" in the footer prior to the public issuance of the verification badge was a development template oversight. We have removed that placeholder to avoid misleading players, and we will restore it only once the official validator link and registration credentials are fully active and publicly verifiable.
We understand that skepticism is normal and necessary on Bitcointalk for newly launched projects. We appreciate you pointing out these oversights so we can address them transparently and focus on earning community trust.
Best regards,
just took one look at the casino and decided not to sign up, i usually do Google as they are safe from password leakage so i went ahead and tried to sign up and the first thing i checked was the developer tools to make sure i am connecting to the right emails and guess what, it’s your personal email with over 20 leaks from your acc and i don’t connect with my OAuth with those. well, on the good side it’s basically full OSINT as there is a whole history of names and Google reviews so in case any scam happens we know who to go after. i wouldn’t say having breaches on the email is bad, but using a personal email as the Google OAuth for users is bad
https://ibb.co/F4GFj248Hello,
Thank you for bringing this to our attention. You made a completely valid technical observation, and we appreciate you pointing it out directly.
1. Google OAuth Staging Credentials (Now Updated)During initial setup and local staging testing of the Google OAuth integration, one of our frontend developers used an internal personal Google Cloud project console to generate the test `client_id` credentials. We overlooked switching these test keys over to our dedicated, isolated organization console (`@debet77.space`) prior to going live.
We have now generated fresh OAuth 2.0 credentials directly under our official verified domain workspace, and the client-side configuration has been updated.
2. Privacy & Architecture ClarificationFor players concerned about data security: standard Google OAuth client requests only transmit Google's token payload between the user and Google's auth servers to verify account ownership. However, we completely agree that using a developer's private console account looks unprofessional and raises valid questions about separation of duties.
Thank you again for the thorough technical check and for helping us catch this staging oversight early.
Best regards,
