Slots / Live
wwe555 explains in this policy how we collect, store and use the details tied to your account, wallet and transaction history, and what you can do if you have a question about how that data is handled.
Your privacy on wwe555 sits alongside the account and wallet steps you already use for deposits and withdrawals. When you link a transaction to Nagad, Rocket or Upay, we record the account reference needed to match that transfer to your wallet balance — not the full login details of your mobile money account. We keep this data to confirm a deposit landed, to resolve a withdrawal query, and to keep your transaction history accurate when you check it from your account page. How this policy applies to you depends on your local law and the eligible region you're accessing wwe555 from; some data-handling steps may differ where regional rules call for a different approach. We don't sell your account data to outside advertisers, and we limit who inside wwe555 can see your wallet and transaction records to the support and verification routes shown on the site. If you open a support ticket about a Nagad or Rocket transfer, the details you submit are used only to track that query through to a response. Cookies and basic device data keep your session active while you move between the lobby, your account page and the sportsbook, but they aren't used to build a profile beyond keeping the site working for you. This policy covers wwe555 directly; it doesn't automatically apply to a linked payment app's own privacy terms, which you should check separately through Nagad, Rocket or Upay.
This policy sets boundaries around four areas of your activity on wwe555, so you know which part of your account is in scope when you ask us a question about your data. Account access, transaction records, site content and third-party services each sit under a slightly different handling rule, depending on whether the data stays with wwe555 or passes through a payment provider like Nagad, Rocket or Upay. Reading these side by side helps you see why a login detail is treated differently from a wallet reference, and why a question about a Nagad transfer may get routed to a different step than a question about a locked account field. None of this changes based on which device you use to sign in; the same scope applies whether you check your account from a browser or a saved session on your phone.
Covers the login details, device sessions and verification steps tied to opening and signing into your wwe555 account, including how we handle a forgotten password request, a changed registered mobile number or a device switch when you sign in from a new phone.
Covers deposit and withdrawal entries linked to Nagad, Rocket or Upay, including the reference data we keep so a transfer can be matched to your wallet balance and checked later from your account page or a support ticket you raise about it.
Covers how we log which lobby sections, game pages or sportsbook screens you open during a session, used only to keep navigation working across devices, not to build an advertising profile or track you once you've signed out of your account on this device.
Covers data shared with a payment provider or verification step outside wwe555, such as Nagad, Rocket or Upay's own systems; how they handle your data sits under their own separate policy, which you should check directly with that provider before you submit a transfer.
You hold a few direct actions under this policy. You can ask us what account and transaction data we hold against your wwe555 profile, request a correction where a detail is wrong, and raise a question about how a Nagad, Rocket or Upay transfer was logged against your wallet. We handle these requests through the support routes listed on the site, not through a separate claims process. Because availability and the exact steps depend on your local law and the region you're accessing wwe555 from, some requests may take a different path depending on where you are. We don't ask you to prove your identity beyond what the account and verification screens already require. If you've changed a registered mobile number or need an account detail updated, use the account settings page first, then contact support if the field won't update on its own.
Open your account page to check the transaction history tied to a Nagad, Rocket or Upay transfer, and confirm the wallet balance shown matches what you expect before you raise a question.
Use the account settings screen to update a registered detail; if a field is locked, contact support so the change can be applied on the record we hold against your profile.
Raise a direct question about why we hold a particular transaction entry or device detail, and we'll explain the reason tied to that specific record rather than a general statement.
If an earlier reply didn't resolve your question about how your data was handled, you can follow up through the same support route and reference your earlier ticket.
If a question about your data doesn't fit neatly into the account settings screen, support is the next step. We've kept the contact routes tied to the account and help pages you already use for a transaction query, rather than adding a separate privacy desk you'd have to go hunting for. A question about a Nagad transfer, a Rocket deposit entry or an Upay reference on your wallet history gets handled the same way as any other support ticket, so you don't need a different login or a different page to raise it. Keep your account signed in when you reach out, since the ticket is matched to your profile automatically, and reference the specific entry or detail you're asking about so the reply can address it directly instead of giving you a general answer.
Reach support directly from the help link inside your signed-in account, where you can raise a question about your data, a transaction entry or a wallet record tied to Nagad, Rocket or Upay, and reference your account details so the query is easy to trace.
Check the published help pages linked from the footer for the current steps on account access, verification and how a privacy question gets routed before you submit a ticket, especially if you're unsure which route covers a transaction question tied to Nagad, Rocket or Upay.
If you already raised a question about your data, follow up on the same ticket thread rather than opening a new one, so your account and transaction context stays attached, which keeps the reply focused on the Nagad, Rocket or Upay transfer you originally asked about.
Keeping your data tidy matters as much as keeping it safe. We tie account security to the verification steps already shown at login and withdrawal, rather than a separate security layer you'd need to set up yourself. Cookies keep a session alive while you move between the lobby and your account page, retention rules decide how long a closed account's data stays with us, and the contact route for a question is the same one you'd use for any other support matter. None of this depends on which payment rail you use day to day — the same handling applies whether your last transfer was through Nagad, Rocket or Upay. Where local law in your region sets a different requirement, that rule takes priority over our general approach, and we'll apply it to your account accordingly.
We hold account and transaction data only for as long as it's needed to keep your wallet record accurate and to resolve a support question, not for an open-ended period, and we check what's kept whenever a closed account comes up for a retention check.
Cookies keep your login session active as you move between the lobby, your account page and the sportsbook; clearing them signs you out and may reset a saved preference such as your preferred lobby view or last payment chip you selected.
Your account is tied to the verification steps shown at login and at withdrawal; we don't store your full Nagad, Rocket or Upay credentials, only the reference needed to match a transfer back to your wallet balance when you check your account page.
When a retention period ends for a closed account, we remove the data tied to it unless local law in your region requires us to keep certain transaction records longer, and you can contact support if you want to ask what's still held against an old profile.
No. We only keep the reference data needed to match a deposit or withdrawal to your wallet balance, not your mobile money app's login credentials or app password, so that detail stays fully under your own control inside Nagad, Rocket or Upay.
Your transaction history is visible to you from your account page and to the support team handling a ticket you've raised about a specific entry; it isn't shared outside that route unless your local law requires a different disclosure, which this policy explains applies by region.
Yes. Update what you can from the account settings screen first, and contact support if a field is locked so the record can be corrected on our side, which keeps the detail accurate the next time you check a Nagad, Rocket or Upay transfer against it.
How certain data steps apply can depend on your local law and the eligible region you're accessing wwe555 from, so the exact process may vary slightly by region, so check the terms shown at sign-up for the specific wording that applies to your account.
We exchange only the reference data needed to confirm a transfer with the payment provider involved; their own handling of your data sits under their separate policy, not ours, so a question about how Nagad, Rocket or Upay stores that detail should be raised directly with them.
Raise it through the support route inside your signed-in account or the published help pages, referencing the transaction or detail you're asking about, and include the date so the record is easy for support to locate against your wallet history.