Mobile / Sports
yytmp3 explains what account and device data we collect when you log in, browse the lobby or contact support, and how that data stays tied to your account. What applies to you depends on your local law and the eligible region you're accessing the site from.
This page covers how yytmp3 handles the details tied to your account — what you give us when you register, what your device sends when you sign in, and what gets logged when you move between the lobby, the sportsbook and your wallet. We don't sell account data to outside parties, and we only pass along what's needed to confirm a transaction or check an account on your behalf. Where you pick a payment route — bKash, Nagad, Rocket — the wallet reference tied to that transaction sits inside your account history, visible to you and to us for verification purposes only; we don't publish or trade that reference anywhere else. Because yytmp3 reaches readers across different districts and account types, the exact rules that apply to your data depend on your local law and the region you're signed in from — protections can differ depending on where your account was opened. We keep this page written in plain language instead of dense legal phrasing, so you can see what's collected, why we collect it, and who to contact if something looks off. If a clause here conflicts with a rule where you live, local law takes priority over this page. We adjust this policy when our account or support process actually changes, not on a fixed calendar.
This policy sits around four parts of your time on yytmp3: signing into your account, moving money through your wallet, browsing what's in the lobby, and touching any outside service we rely on to get a job done. Each works a little differently, so we've split out what each part covers rather than writing one blanket statement. Account access and wallet activity sit squarely inside what we control and explain here. Lobby content — the games, tables and sportsbook markets you browse — carries lighter data handling since it's mostly anonymous browsing. Outside services, like a payment processor confirming a bKash or Nagad transfer, run under their own rules once your request leaves our account system, and we tell you where that handoff happens.
Covers the login details, device type and session data created when you sign in from a phone or desktop browser, and how that session data is matched back to your account to keep access continuous across visits and devices you use regularly.
Covers the wallet references created when you move funds through bKash, Nagad or Rocket, kept inside your account history for verification and record-matching only, never shared outside what's needed to confirm that a specific transfer actually went through on your account.
Covers browsing across slots, live casino tables and sportsbook markets such as BPL Powerplay Slots or Football Straight Bets — this activity is logged at account level but carries no separate personal data beyond standard account access records already described above.
Covers moments where a request leaves our direct account system, such as a payment confirmation step with a wallet provider handling a bKash, Nagad or Rocket transfer, where handling then follows that provider's own terms rather than this page alone.
You can ask at any point to see what account data yytmp3 holds against your profile, correct a detail that's gone out of date, or raise a question about how a specific record got used. We don't run a self-service export tool right now, so these requests go through the published support route on this page instead of an automated form. When you write in, include your registered account identifier so we can match the request to the right profile without back-and-forth. What happens next depends on what you're asking for — fixing a wallet reference tied to a bKash, Nagad or Rocket transaction is handled differently from a general account question — and we'll tell you what we need to confirm it's your account before acting.
Ask us to show the account data on file so you can confirm it matches what you expect, including login and device history tied to your profile.
Flag a detail that's wrong or out of date — a name spelling, a contact field — and we'll update it against your account once we've confirmed it's you.
Raise a question about a wallet reference tied to a bKash, Nagad or Rocket transfer sitting in your account history, and we'll walk through what's logged against it.
Send a written request through the support route on this page if you want a record of the question and our answer, rather than a quick chat exchange.
If something about your account data doesn't look right, or you want a detail corrected, the fastest path is the support route already on this page rather than searching for a separate contact. We keep this policy tied to the same support channel you'd use for an account or wallet question, so there's one place to go instead of several. Mention that your message concerns account data or this policy when you write in — that helps route it to the right person instead of a general queue. We don't operate a separate legal desk apart from account support, so treat this as part of the same conversation you'd already have about your account or a bKash, Nagad or Rocket transaction.
Use the support route published on your account page for questions about data tied to your profile, login history or a specific transaction record, including anything linked to a bKash, Nagad or Rocket payment you've made through your account directly.
Open live chat from within your signed-in account when you need a quick answer about a detail in this policy or a record on your profile — useful if you just need a short clarification rather than a written reply.
Send a written message through the same support form for anything you'd rather keep as a record, including a correction request or a question about this policy — written requests are easier to track back against your account history later.
Keeping your account data straight matters more to us than writing a long legal document nobody reads. Below are the parts of day-to-day handling that affect you directly: how we check it's really you signing in, what cookies do between page loads, how long records stay attached to your profile, and where a change request actually goes. None of this replaces the support route on this page — it just explains what sits behind it so a request you send doesn't feel like a black box.
We match login attempts against your registered account details before granting access, and unusual device activity — a new browser, an unfamiliar location — can trigger an extra verification step on sign-in to keep the account tied to you specifically.
We use cookies to keep you signed in between pages and remember basic preferences such as language or display settings; clearing them signs you out and resets those preferences the next time you open yytmp3 on that device again later.
Account and transaction records, including wallet references tied to a bKash, Nagad or Rocket transfer, stay attached to your profile for as long as your account is active and for whatever period local law requires afterward in your region specifically.
Any change to your account data — a correction, a question about a record, a detail tied to a bKash, Nagad or Rocket transaction — goes through the support route on this page rather than a separate form or portal.
A short set of answers to what returning account holders usually ask about this page — data sharing, wallet references and how to get a detail corrected.
We only share what's needed to confirm a transaction or verify your account — for example, with a wallet provider processing a bKash, Nagad or Rocket transfer. We don't sell account data, and anything shared is limited to that specific confirmation step.
Yes — write in through the support route on this page and include your registered account identifier so we can locate your profile quickly. We'll match your request against your account history and tell you what's recorded there, including login and transaction details tied to your profile.
The wallet reference tied to a bKash, Nagad or Rocket transaction sits inside your account history and is used for verification only, matching the transfer against your profile. We don't publish that reference or pass it along beyond what's needed to confirm the transfer went through on your end.
Local law takes priority over any clause here. Since yytmp3 reaches readers across different regions, the exact data rules that apply to you depend on your local law and whether your region is currently eligible to access the service at all.
Yes — send a written request through the support route on this page and tell us exactly what's wrong. We confirm it's your account before updating a name, contact field or similar detail tied to your profile, so the correction matches your records.
Browsing games, tables or sportsbook markets — including titles like Crash Ignition or Baccarat Insider — is logged at account level alongside your usual access data, but it doesn't create a separate personal record outside your normal account history on yytmp3.