Mobile / Slots
Your account data belongs to you. We collect only what is needed to run your wallet, verify your identity and keep your session secure across devices — whether you are on mobile or desktop in Bangladesh. Access and data handling depend on your local law and eligible regions.
The 45ok privacy policy sets out exactly what information we collect when you open an account, load your wallet or interact with the lobby. It covers account registration data, device identifiers, payment records tied to your bKash or bank transfer activity, and session logs used to restore your mobile lobby state. We do not sell your data to third parties for marketing.
When you open an account, we collect your name, contact number and email address. This is used to verify your identity and link your wallet. No extra documentation is collected unless your account triggers a verification review as described in the published policy.
Transactions processed through bKash or bank transfer create a record in your account wallet history. We retain this to resolve disputes and confirm wallet balance accuracy. You can view your own transaction log from the account section at any time after logging in.
We log the device type, browser version and session timestamps so the lobby can restore your last position when you return on a phone or switch to desktop. This is purely functional — it keeps your account state consistent without requiring you to navigate back manually.
Any message you send through the published support route is stored against your account reference. We keep this record to track resolution history. It is never shared externally. You may request a summary of your support history via the account help channel listed on the site.
Transparency about data handling is built into the account flow, not buried. The privacy policy link appears in the site footer and again at account registration so you see it before you submit any information.
The full privacy policy is linked from the footer on every page of 45ok. It is also presented at the account registration step so you can read it before submitting any details.
Each category of information we collect — registration, payment, device, support — is listed by name in the policy with a plain explanation of purpose. No unnamed or implied data categories are used.
The policy states how long each data category is held. Payment records are kept as long as required by applicable rules. Session data is cycled on a rolling basis as described in the published document.
A dedicated section in the policy describes how to request access to your data, submit a correction or ask for deletion. The process involves contacting the published support route with your account reference.
If you have a question about your personal data — what we hold, how long we keep it or how to request deletion — the published support channels on 45ok are the right starting point. Bring your account reference so the team can locate your records quickly.
The support route published on 45ok handles privacy requests directly. Open the help section from your account, include your registered number or email and describe the data question clearly so the team can act without unnecessary back-and-forth.
If a specific clause in the privacy policy is unclear, ask the support team to point you to the relevant section. They cannot change the policy, but they can explain what a clause means for your account and wallet in plain terms.
To request a copy of your data or ask for deletion, contact support with your account reference and the specific data category you are asking about. The team will confirm receipt and follow the steps described in the published policy.
Account data accuracy matters most when your wallet balance or transaction history is in question. We maintain records of every bKash top-up and bank transfer processed through your account so there is always a reference point if a discrepancy appears. Session logs kept for device continuity are functional only — they are not shared with advertisers or analytics firms outside the platform.
Every transaction through bKash or bank transfer is logged against your account with a reference you can view. If a discrepancy appears, the support team uses this record to investigate and resolve the issue without requiring you to provide external proof.
Your registration details, device data and payment records are not passed to third parties for advertising or profiling purposes. The privacy policy names the limited circumstances under which data may be shared — read the relevant section before registering.
The privacy policy link in the footer always points to the version currently in effect. When we make material changes we update that document. Check it periodically from the footer if you want to confirm what applies to your account at any given time.
The published policy explains which data is deleted after account closure and which records we are required to retain. If you close your account and want confirmation of what remains, contact support with your account reference and the team will clarify.
Personal data is any information that can identify you — your name, phone number, email address or payment details. In the 45ok context it includes the details you provide at registration and wallet verification.
A retention period is how long a platform keeps a specific category of data after it is collected. The 45ok privacy policy states the retention period for each data type, including payment records and session logs.
A data subject request is a formal ask from you to the platform — to see what data is held, to correct an error or to have it deleted. The published policy explains how to submit one through the support channel.
A session token is a temporary identifier stored on your device that keeps you logged in while you are active. It allows the lobby to restore your position on return without requiring you to log in again from scratch.
A third party is any company or entity outside 45ok that might receive your data. The privacy policy lists the specific circumstances under which data is shared and confirms it is not passed to marketers or advertisers.
KYC stands for Know Your Customer — the identity verification step some accounts require. Documents submitted for KYC are covered by the same data protection rules as all other personal data described in the published policy.
The privacy policy is linked from the footer of every page on 45ok. It is also shown during the account registration flow. You can open it at any time without being logged in. All data handling details are in that published document, and access depends on your local law and eligible regions.
Yes. Every bKash top-up processed through your account wallet creates a record that you can view from the transaction history in the account section. This record is held for the period stated in the privacy policy and is used only for account management and dispute resolution — not for marketing.
Contact the support channel published on 45ok and include your account reference plus the specific data you want deleted. The team follows the steps described in the privacy policy. Deletion may be partial if certain records must be retained under applicable rules for your eligible region.
The privacy policy names the limited circumstances under which data may be shared — for example where required by law or for payment processing. Your data is not shared with advertisers or third-party marketers. Read the relevant section of the published policy for the full list of circumstances.
Device and session data is collected so the mobile lobby can restore your position when you return to the site. It keeps your account state consistent across phone and desktop without you needing to navigate back manually. This data is functional only and is described in the privacy policy.
The privacy policy sets out which categories of data are deleted after account closure and which must be retained under applicable rules. Contact support with your account reference after closure if you want written confirmation of which data has been removed and which remains on record.