Reference

What Our Privacy Policy Covers

One page, plain wording: this policy sets out what account and payment data ducmc keeps, why we keep it, and how you ask us to correct or remove it.

Account detailsWallet recordsCookie settingsChange requests
ducmc What Our Privacy Policy Covers
HOW WE KEEP DATA

Security, Cookies And Retention

Your session is tied to the device you sign in from. Logging in sends an OTP to the mobile number on your account, and a phone we have not seen before asks for that code again before it reaches the wallet. Cookies do the small jobs: keeping you signed in, remembering your language, and showing us which screens crawl on mobile data. Clearing them in your browser settings signs you out everywhere.

One-time codes

Every sign-in triggers an OTP to your registered mobile number. If a code arrives when you are not logging in, change your password and tell support the same day.

Cookie control

We use cookies for sign-in, language and basic page measurement. You can block them in your browser, though the wallet needs the sign-in cookie to stay open between screens.

Record retention

Payment references are held while a transfer can still be disputed, then trimmed. Ask us to delete records we no longer need and we will confirm what goes.

Who handles it

Payment checks sit with the wallet team and account data with support. Both read the same account record, so a correction made once shows up on every screen.

REACH OUR TEAM

How To Contact Us About Data

You should not have to explain yourself twice. Message our desk from the chat button inside your account wallet and the agent already has your account ID, wallet number and last payment reference on screen. For anything touching your data, say plainly what you want changed — a phone number, a wallet, or the account itself — and we will tell you what we need to confirm it is really you.

Support chat Open chat from the wallet page and an agent can see your account ID, wallet number and last payment reference without you searching for them.
Email the team Write to the support email shown on our contact page and put 'data request' in the subject line so it routes to the desk that handles it.
Inside your account If chat is unavailable, the same request can be raised from account settings, where every change is logged against your profile for easy follow-up later.

Privacy Questions We Get Asked

Most of what reaches us is practical rather than legal: can I see my data, who else sees my wallet number, what happens if I close the account. The answers below are the short versions we give on chat every day. If yours is not here, send it down the support paths above and a person will reply.

Yes. Ask from inside your account wallet and we will send you what we hold: profile details, the wallet numbers you have used, and your payment history with us.

Only the teams that process payments and answer your messages. It is not shown anywhere in the lobby, and it is not passed to the studios whose games you open.

Send the request through support chat. We verify the old number with a one-time code, register the new one, and confirm it again before your next withdrawal goes out.

A few. They keep you signed in, remember your language choice, and show us which screens load slowly. You can clear them in your browser, though the wallet will ask for a fresh code.

We close the wallet and stop messages. Payment references stay a while longer because a transfer can still be disputed, and local law decides how long that period runs.

No. What we may collect, and how long we keep it, depends on local law and eligible regions, so some requests are handled differently depending on where you are.
Reference

Privacy Policy

Service availability depends on eligible regions and local law. Users should check local rules before opening an account.

Access may be available only where local law permits.