Reference

How jita33 Handles Your Account Data

A privacy policy should read like a receipt, not a riddle: what we hold, why we hold it, and how you get it changed.

What we collectWhy we need itWho can see itHow to change it

What Our Privacy Policy Applies To

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

When you open a jita33 account we hold the minimum needed to run it: the mobile number you sign in with, the one-time code sent to that number, the wallet reference from a bKash, Nagad or Rocket transfer, and everyday device data such as browser type

1
and approximate region. The wallet reference exists to match your deposit to your account. Device data tells us whether a sign-in came from the phone you normally use, so a session you did not start stands out. We also keep your activity — the cricket markets
2
you opened, the slots you played, the times you signed in. That history answers a payment query faster than memory can, and it is the record we show you when you ask what we hold. We do not sell your details. Inside the team, access to
3
an account is limited to whoever is fixing a wallet query or a security flag, and each lookup is logged against a staff ID. How long we keep any of this depends on your local law and eligible regions. Some jurisdictions require transaction records to be
4
held for a set period after closure; others let you ask for erasure. Where the two conflict, local law sets the rule. If a lawful request reaches us from an authority with jurisdiction, we release only the records named in it. Cookies sit under the same
5
policy. They keep you signed in between visits and remember your language and payment preference. Clear them and you sign in again, nothing more.

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

LOCKED DOWN BY DEFAULT

Security Steps Behind Your Account

Security around your record is boring on purpose. Every sign-in needs the one-time code, and you can end a session from another phone or browser without waiting on us. Cookies split the same way — the ones keeping you signed in do real work, the rest are preference only, and clearing them costs you a fresh sign-in rather than your account. Retention follows local law, so a closed account keeps its transaction trail only as long as the rules require. Want a field corrected or removed? Ask through the help desk and we say what we can change, and what a legal duty keeps in place.

Sign-in codes

The one-time code is the lock on your account. We never ask for it in chat or email, and it expires quickly, so a copied message is useless a few minutes later.

Cookie control

Sign-in, language and wallet preference cookies do real work. Everything else is cosmetic. Clear the lot from browser settings whenever you like and carry on with one extra sign-in.

Keeping records

Transaction trails stay as long as your local law requires and no longer. Close the account and marketing data goes straight away; payment records remain because a duty, not a preference, keeps them.

Fixing a field

Request a correction, a copy or a deletion from the help desk. We confirm identity first, then tell you plainly what we can amend and what we are obliged to retain.

ASK US DIRECTLY

Where to Send a Privacy Request

Ask us and we move it. Any privacy request — a copy of your data, a correction, a deletion after closure — starts in the help desk inside your signed-in account, because that is the only place we can tie the request to your number and wallet. Name the topic and the account. If the message arrives from a number we don't recognise, we verify before we touch anything: the old number, one recent bKash, Nagad or Rocket reference, and the code we send to the new device.

In-account help desk Open it from your signed-in account and pick the privacy topic. It routes to the team that actually owns account data, so you skip the general queue entirely.

Written request Prefer writing? Send from the number or address already on your account. Anything arriving from a new contact goes through verification before a single field is changed.

Number change Changed your phone? We confirm the old number plus one recent bKash, Nagad or Rocket reference, then move the account across to the new handset.

Privacy Questions You Ask Us

Your mobile number, the sign-in codes we send to it, the wallet reference from your first bKash, Nagad or Rocket transfer, and basic device detail such as browser and region. Nothing beyond what keeps the account running.

No. Your number and wallet references sit against your own account and are visible only to the team handling your payment or security query. Nobody else on the platform can see them.

Yes, and we'll tell you honestly what is possible. Payment records usually have to be kept for a period set by local law; the rest, marketing data included, can go once the account is closed and verified.

Use your browser settings to clear or block them. The sign-in cookie is the one you will notice missing — the next visit asks for a one-time code before the account opens.

The help desk inside your signed-in account passes it to the team that owns account data. Send it from the number already registered and it moves without extra identity checks.

Yes, with verification. We ask for the old number, one recent bKash, Nagad or Rocket reference and the code sent to your new handset before anything is moved across.

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 InfoRoulette Nightspin InfoGreen Star Slots

How jita33 Handles Your Account Data

Security Steps Behind Your Account

Where to Send a Privacy Request

Privacy Questions You Ask Us

01 What data do you collect when I open an account?

02 Is my bKash or Nagad number shown to other account holders?

03 Can I ask you to delete my data?

04 How do I stop cookies on jita33?

05 Who actually handles a privacy request?

06 My phone changed — can I still reach my old account?

Privacy Policy

Related pages

Related pages