Reference

What Our Privacy Policy Covers

One page, plain wording: what we collect when you open a 45a account, why we keep it, and how you ask us to change or delete it.

Account details we holdWhy we keep themYour request rightsCookie controlsLocal wallet data

Explore the Lobby Read FAQ

SECURITY AND RETENTION

Cookies, Login Security and Retention

Login security starts with the phone in your hand. Every new device answers an OTP before it reaches your wallet, and a shared handset can be cleared from your profile so the next person needs that code too. Cookies do a narrower job: they keep your session alive and remember basic display settings. Blocking them still lets you log in, but you will re-enter the OTP more often. Records tied to a bKash, Nagad or Rocket payment sit on file for the period local rules require, and we delete what has no purpose left.

Cookie Controls

Browser settings let you clear or block cookies for this site. Session cookies keep you signed in; clearing them logs you out on that device only, and the next login asks for an OTP.

OTP on New Devices

A code goes to your registered mobile number before any unfamiliar handset reaches the account. That single step is the main thing standing between your wallet balance and someone else.

Retention Periods

Transaction records stay as long as payment disputes and local tax rules need them. Marketing preferences and display cookies are cleared sooner, and you can wipe those yourself at any time.

Requesting Changes

Want a copy of what we hold, or a correction to your name or wallet number? Send the request from your account email and the desk will confirm what local law lets us change.

How We Handle Your Account Data

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

We collect the details you type in when you open an account, plus the trail your activity leaves afterwards. That means your name, mobile number, email, and the wallet number you use for bKash, Nagad, Rocket or Upay. Our payment partners return a transaction reference so

1
a deposit can be matched to your account wallet; your wallet PIN stays with your wallet provider, never with us. Device data such as handset model, browser and IP helps us catch a login that does not look like you, which is why an OTP lands
2
on your phone before a new device gets in. Retention is not one flat number. Transaction records stay longer than a marketing preference, because payment disputes and tax rules need them. Cookies expire on their own schedule; clear them from your browser settings any time and
3
you can still log in, you will simply answer the OTP again. Some of this is a legal duty and some is our own choice to keep the service usable. Which rules apply to you depends on local law and your eligible region, and where two
4
sets conflict we follow the stricter one. If you are in Bangladesh and want to know what we hold, the support desk will walk you through the categories before you file a request.

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

POLICY CONTACT

Where to Ask About Your Data

Ask us anything about your data and a person answers, not a form that swallows the message. Privacy requests run through the same support desk that handles wallet verification, so the agent already sees your account context: the wallet you registered with, your last login, and which records sit on file. Write from the email on your account and say what you want — a copy, a correction, or deletion where the law allows it. Anything touching a bKash, Nagad or Rocket transaction may need the matching reference before we move.

Privacy Questions You Might Have

Most of what lands in our inbox about this page comes down to four things: what we store, who sees it, how long it sits there, and how to get it changed. Short answers below, with the longer version in the sections above. If your case is not here, the support desk takes it from there. We keep the wording short on purpose, because a policy nobody finishes reading protects nobody.

Your name, mobile number and email, plus the wallet number you used for bKash, Nagad or Rocket, your login history, and transaction references attached to deposits and cashouts. Nothing beyond what running the account needs.

No. You approve the payment inside your own wallet app, so our side sees a confirmation and a transaction reference only. Your PIN never reaches us, and no agent will ask for it on chat.

Email the support desk from the address registered on your account and ask for a copy. We confirm what we hold and what local law lets us hand over, then send it in a readable format.

Most of them, yes. Session data and display preferences go quickly. Transaction records tied to a bKash, Nagad or Rocket payment stay for the period local rules set, because disputes can surface later.

You can, and login still works. You will answer the OTP more often, because the session cookie is what keeps you signed in between visits. Blocking cookies affects this device only.

Tell the account desk, using your registered email. If a name, mobile number or wallet reference is wrong, we fix it after a short verification. Anything that looks like an unauthorised login goes to chat.

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.

InfoLegal AccountRegister Games45a Casino

What Our Privacy Policy Covers

Cookies, Login Security and Retention

Where to Ask About Your Data

Privacy Questions You Might Have

01 What personal data does 45a hold about me?

02 Do you ever see my bKash or Nagad PIN?

03 How do I get a copy of the data on file?

04 Are my records deleted when I close my account?

05 Can I browse with cookies turned off?

06 Who do I tell if my data looks wrong?

Privacy Policy

Related pages

Related pages