Mobile / Sports
This policy explains exactly what data 777rk collects when you create an account, fund your wallet through Nagad or Upay, and browse the lobby. Access to this platform and the rights described here depend on your local law and eligible regions.
When you register an account on 777rk, we collect the details you provide directly: your name, contact number, and the wallet identifier you link for transactions — whether that is Nagad, Upay or another configured local payment method. We also record device and session data generated during your visit: browser type, screen resolution, session duration and the pages you navigate. This operational data helps us keep the account area working correctly for mobile access and to identify unusual patterns that could indicate unauthorised use. For payment transactions, we log the method used, the amount, the transaction reference and the timestamp. We do not store full wallet credentials on our servers; payment processing happens through the configured payment channel directly. We retain transaction records for as long as required to resolve disputes and meet record-keeping obligations under applicable rules — the exact retention window is stated in your account settings area. If you have questions about what data is held against your account, the support contact route in the section below is the correct path to raise that request.
Not every part of your online activity falls under this policy. Understanding what is and is not covered helps you know where to look when questions arise about your data or your account behaviour.
This policy covers all data generated when you log in, update your profile or change your account wallet settings. Any action taken inside your authenticated session is within scope and subject to the retention and access rules described here.
Payments processed through configured local routes — including Nagad and Upay — generate records covered by this policy. The payment channel itself operates under its own terms; we cover only the record we hold on our side of the transaction.
General browsing of game lobbies, reading published terms or viewing promotional notices creates session data covered here. We do not link anonymous browsing data to your account unless you are signed in at the time.
External links, third-party game studios such as CQ9, Pragmatic Play, Habanero and Joker, and any offsite resource operate under their own privacy terms. We are not responsible for data practices outside the 777rk platform boundary.
You have a set of practical options when it comes to the data we hold on your account. These are not abstract legal entitlements — each one has a real path inside your account or through our support channel. Start by opening the account settings area when signed in; the profile section shows the personal details attached to your registration. If anything there is incorrect — a contact number, a linked wallet reference, a display name — you can edit it directly from that screen without contacting support. For transaction records, the account history tab shows a log of your deposit and withdrawal activity, including the method used and the reference number for each entry. If you need a copy of your full account data, or you want to ask that certain records be reviewed or removed where permitted under applicable rules, that request goes through our support contact route. Availability of specific data rights depends on local law and your eligible region.
Open the account history tab when signed in to see your full transaction log, including Nagad and Upay entries with reference numbers and timestamps.
Edit your name, contact number or linked wallet identifier directly from the profile section in account settings — no support request needed for standard corrections.
For data access or removal requests that go beyond self-service edits, contact the support team through the published route and reference your account ID in the message.
If any part of this policy is unclear in relation to your specific account or payment method, submit a written query via the support channel and we will respond through the same route.
For any question specifically about how your data is handled — what we hold, how long we keep it, or how to request a correction — use one of the contact routes published on this site. Availability of each route depends on the channels currently active; check your account area for the most current list.
Open the live chat widget from any page when signed in. For data and privacy queries, describe your question clearly and include your account reference so the agent can pull the correct records.
Send a written data query to the support email address published in your account help section. Written requests create a reference trail useful for data access or correction follow-ups.
The help section inside your account lists current contact routes and submission forms. This is the most reliable place to confirm which channels are active for your region.
Our approach to your data is built around what you can check, not what we ask you to assume. Each of the four areas below describes a real practice you can verify through your account or by raising a query through support.
We use cookies to keep your session active and remember your account state between pages. You can review and adjust cookie settings through your browser. Disabling certain cookies may affect how account features and the lobby load on your device.
Your account is protected by password authentication. We do not store your Nagad or Upay wallet credentials on our platform servers. If you notice unexpected access, use the account security section to change your password immediately and contact support.
Transaction records and account data are kept for the period required to resolve disputes and meet applicable record-keeping obligations. The retention period applicable to your account is stated in the account settings area. Requests for earlier removal are assessed case by case.
When we update this policy, the revised version is published on this page with a notation of the change. Continuing to use your account after a policy update is published means you accept the current version. Check this page if you want to review the version currently in effect.
These are the questions we see most often from account holders in Bangladesh about how their data is handled on 777rk.
We collect the details you submit during registration: your name, contact number and any wallet identifier you link for payments. We also collect device and session data automatically during your visit. You can see what is attached to your account in the profile section when signed in.
We record the wallet identifier or reference number associated with a transaction for our records, but we do not store full wallet credentials on our servers. Payment processing flows through the configured payment channel directly. Your wallet account remains under the terms of your Nagad or Upay provider.
Records are kept for as long as required to resolve disputes and meet record-keeping obligations under applicable rules. The specific retention period for your account is visible in the account settings area. For questions about a specific record, raise a query through the support channel.
Yes. Submit a written data access request through the support email or live chat route published in your account help section. Include your account reference. Availability of this right depends on local law and your eligible region, and we will confirm the scope when we respond.
Open account settings while signed in and navigate to the profile section. Most fields — contact number, display name, linked wallet reference — are editable directly from that screen. For fields you cannot edit yourself, contact support through the published route and describe the correction needed.
No. Studios such as CQ9, Pragmatic Play, Habanero and Joker supply game content to the lobby and operate under their own data terms. This policy covers only the data we hold on our side. For any data question related to a studio's own systems, refer to their published policy directly.