App / Mobile
vs555s collects and uses your personal information only to operate your account, process transactions through routes like bKash and Bank Transfer, and keep your session continuous across devices. What we collect, why we collect it, and how you can review or correct it — that is exactly what this policy covers.
This policy applies to information you provide when you open an account with us, log in from any device, or initiate a transaction. When you deposit via bKash or Bank Transfer, we record the transaction reference, the amount and the timestamp — not your full wallet credentials, which remain with your payment provider. We store the minimum data needed to keep your account whole: your registered contact detail, your session identifiers and your transaction history as it appears in your account wallet view. Data we hold about your device — browser type, screen resolution and session token — is used solely to maintain continuity when you move between your phone and another device. We do not sell your personal information to third parties. Sharing occurs only where a payment processor requires it to complete a bKash or Bank Transfer instruction, or where applicable law in your eligible region compels disclosure. Access to and use of this platform depends on your local law and the eligible regions defined in our terms. If you are unsure whether access is permitted in your jurisdiction, review the eligibility section in our published terms before proceeding.
Not every interaction on the platform falls under this single document. Understanding the boundary between what we control and what third-party services handle helps you know where to direct a data question.
Any data you enter during login — your registered identifier and session token — is covered by this policy. We control how that data is stored, how long it is retained and who inside our operation can view it. Your login path on mobile or browser falls within this scope.
When you use bKash or Bank Transfer, the payment leg of that instruction passes through your payment provider's own system. We receive a transaction reference and status only. The payment provider's separate privacy terms govern what that provider does with your wallet credentials and personal details.
Game content delivered by studios listed in our lobby — including titles available from our catalogue — is rendered inside our platform environment. Session data generated during gameplay is covered here. We do not attribute data handling to individual studios; that sits with us as the platform operator.
Links that take you away from vs555s — such as a support tool hosted on a third-party domain — fall outside this policy the moment you leave our site. Those external services publish their own data terms, and we encourage you to read them before sharing any personal detail there.
Your account record is yours. If you believe a detail we hold is wrong — your registered contact, a transaction entry in your wallet history or a device linked to your session — you have a clear path to address it. Log in to your account and open the account settings page; the fields shown there reflect what we currently hold for your profile. For wallet-level transaction records, the history view inside your account shows the reference, method and status of each completed instruction, including bKash and Bank Transfer entries. If a record looks incorrect and you cannot amend it from settings, raise it directly through our published support route so we can investigate and correct it. You may also ask what categories of data we hold about you, request that outdated information be updated and ask us to confirm whether your data has been shared with any payment processor. We aim to acknowledge all data questions promptly and respond with the information available to us within the scope of this policy.
Open the account settings page after logging in. The fields shown — registered contact detail, linked device identifiers and session preferences — reflect the live data we hold for your profile at that moment.
Edit editable fields directly in account settings. If a field is locked and the value appears wrong, contact support with your account reference and the correction you need. We will verify and update accordingly.
You can ask us to confirm whether your information was passed to a payment processor during a bKash or Bank Transfer instruction. We will confirm the scope of any sharing that occurred under this policy.
For questions this policy does not answer clearly, use the privacy contact route listed in the support section below. State your account reference so we can locate the relevant records and respond with specifics rather than a generic reply.
If you have a question about how we handle your data — or you want to exercise any of the rights described in this policy — use the contact routes published on vs555s. State your account reference in any message so we can locate your record without asking follow-up questions. Response scope and timing depend on the complexity of the request and the information available to us under applicable law in your eligible region.
The live chat widget visible on the site is the fastest route for policy questions that need a quick clarification. Open a chat session from any page on vs555s and state that your question relates to the privacy policy.
For written records of your data request, use the email address published on the site's contact page. Include your registered account identifier and a clear description of what you are asking us to review, correct or confirm.
The help centre linked from your account area contains articles on data retention, session management and how bKash and Bank Transfer records appear in your wallet history. Start there for self-service answers before opening a support request.
We apply access controls to the data we store so that only the functions that need a given record can read it. Session tokens used to maintain device continuity are issued per login and expire when you sign out or when the session reaches its natural timeout — whichever comes first. Cookies we set are limited to those needed for session continuity and basic site performance; you can manage cookie preferences through your browser settings at any time without losing your account. We retain your account data for as long as your account is active and for a period after closure as required by applicable law in your eligible region. When retention is no longer required, records are deleted from active systems on a scheduled basis. Payment references for bKash and Bank Transfer instructions are kept as part of your transaction history for the retention period applicable in your region.
Internal access to your account record is restricted to the platform functions that require it. We do not give unscoped access to personal data, and payment references from bKash or Bank Transfer instructions are separated from your browsing and session data.
Session and performance cookies are the only types we set by default. You can clear or block them through your mobile browser settings. Doing so may end your active session, but it will not affect your account balance or transaction history.
We keep your account data active while your account is open. After closure, retention follows the period required by the law applicable to your eligible region. Once that period ends, data is removed from our active systems on a scheduled cycle.
To request a correction, deletion or data summary, use the email or chat route in the support section above. Provide your account reference. We will confirm what we can action under this policy and the timeline that applies to your request.
These are the questions we hear most often about data, account records and your rights under this policy. If your question is not here, the support routes in the contact section above are the right place to raise it.
We do not store your full bKash wallet credentials. When you use bKash to fund your account, the transaction reference and status are recorded in your wallet history. Your wallet number and PIN stay within the bKash system, which operates under its own privacy terms.
We collect the contact detail you register with, your session identifiers and your transaction history as it appears in your account. Device information — browser type and session token — is recorded to maintain continuity when you switch between your phone and another device.
Yes. Log in and open account settings to view your current profile data. Your transaction history, including Bank Transfer and bKash records, is visible in the wallet section. For a fuller summary of what we hold, raise a data request through the email contact route.
Retention after account closure follows the period required by applicable law in your eligible region. Once that period ends, your data is removed from active systems. We cannot give a universal figure because the applicable period depends on your jurisdiction.
Game session data stays within the platform environment we operate. We do not pass your personal account details — name, contact or payment references — to the studios whose game content appears in our lobby. Payment data sharing is limited to the processors needed to complete a transaction.
Open account settings and check the editable fields first. If the incorrect value is in a locked field or appears in your transaction history, contact support via live chat or email with your account reference and the specific detail you believe is wrong. We will investigate and correct it where we are able to.