Sports / Casino
777js keeps a plain privacy policy covering what we record when you open an account, log in from your phone, or move funds through bKash, Upay or Bank Transfer. We explain what stays on your account record and what you can ask us about.
This privacy policy applies to your account on 777js, wherever you reach it — mobile browser, desktop, or a shortcut saved to your home screen. We record the details tied to your login, your session state, and the payment method you choose at the cashier, whether that is bKash, Upay or Bank Transfer. We do not sell this detail to outside advertisers, and we only share it with the services needed to run your account, confirm a transfer, or respond to a support query. Because access depends on your local law and the regions eligible to use 777js, this policy sits alongside the terms that apply in your market — if a rule in your region sets a different standard, that local rule takes priority over this general statement. We keep records only as long as your account history, a payment query, or a support question needs them open, and no longer than that purpose requires. If you switch devices — say, moving from a shared browser at home to your own phone later — your account picks up where you left off, using the same login rather than a new data trail. This page is the reference point for how that data is handled; the account and payment screens inside your profile show the live detail for your own record, not this document.
This policy sets out boundaries so you know what sits inside it and what doesn't, rather than treating every page the same way. Account access, payments, lobby browsing and third-party payment steps each carry a slightly different handling rule, and we lay those out below instead of folding them into one vague statement.
Covers the login details, device identifiers and session timestamps tied to your 777js account whenever you sign in from a phone browser or a saved shortcut, including how long that session stays open before you need to log in again on a new device.
Covers the payment reference recorded against your account wallet when you move funds through bKash, Upay or Bank Transfer, including the confirmation note attached once a transfer clears, kept apart from the lobby pages you browse that day.
Covers which lobby pages, game categories or sportsbook sections you open while signed in, logged only to keep your account navigation and device continuity working — this detail stays inside account support, not outside marketing lists.
Covers only the limited data passed to a payment partner to confirm a bKash, Upay or Bank Transfer transfer against your account; it does not extend to any service outside that payment step, and we do not pass your details to unrelated outside platforms.
You hold a few practical options under this policy, and they live inside your account rather than in a separate request form. If you want to check what we hold against your profile, start from your account page and look at the fields tied to your login and payment history. Spotted an old phone number or a payment detail that no longer matches your bKash, Upay or Bank Transfer method? Update it directly where account settings allow a change, or raise it with support if the field is locked. Any question about how a specific record is used — a session log, a transaction note, a support ticket — can go to our published support route rather than a general enquiry box. We keep this simple on purpose: fewer forms, fewer separate processes, and the account screen stays the first place to check.
Open your account page to see the login history and payment references tied to your profile, including entries logged against bKash, Upay or Bank Transfer activity on your wallet.
Update outdated contact or profile fields directly in account settings where editing is allowed, or flag a locked field to support so the correction gets applied to your record.
Send a specific question about a session entry, payment note or support ticket through our published support route instead of a general enquiry, so it reaches the right record.
Ask support to walk through a record you don't recognise — a login, a transfer note, a device change — and get a direct answer tied to your account, not a form reply.
Questions about this policy go through the same channel as any other account question — we don't run a separate privacy desk, since every record it covers already lives inside your account. Point your question to the specific entry you're asking about, and keep the device or payment detail handy so support can match it against your profile quickly.
Reach the account support route listed on 777js when you have a question about your login, your profile fields or a record on your account page that you don't recognise — the same route handles device-switch queries too.
Use the same support channel to ask about a bKash, Upay or Bank Transfer entry showing on your account wallet, pointing to the date and amount you see on your end so the record gets matched correctly against your login.
Send a direct question about this privacy policy through the published support route rather than a general message, so your query reaches the right desk and gets tied to the correct account record instead of sitting in a generic queue.
This policy only means something if the handling behind it is consistent, so here's how data, cookies, security checks and retention fit together on your account. None of this changes depending on whether you open 777js from a saved browser shortcut or a fresh login — the same handling applies either way, tied to one account record.
We hold only the account, login and payment detail needed to run your 777js profile and confirm a bKash, Upay or Bank Transfer entry — nothing is collected beyond what your account page and wallet already show you.
A session cookie keeps you logged in as you move between a saved browser shortcut and your phone, so your account state carries over without asking for a fresh login every time you switch screens or come back later in the day.
Login attempts and device changes on your account are logged so an unusual pattern can be flagged and checked against your history; this detail supports your own account safety and is not shared outside the support and payment process.
We keep account and payment records only as long as your profile stays active or a support query needs them open; to ask about a specific entry or request a change, use the published support route tied to your account.
A short set of answers to the questions we actually get about this policy — how your data is used, what you can check, and who to ask when something on your account doesn't look right.
No — we only pass the minimum detail needed to a payment partner to confirm a bKash, Upay or Bank Transfer transfer against your account wallet. We do not sell this detail or hand it to outside marketing lists, and it stays tied to your account record for payment and support purposes only.
Yes. Open your account page to see the login history, device entries and payment references tied to your profile. If a specific record isn't visible there, raise it through our published support route and ask for the detail directly.
Your account carries over using the same login, not a new data trail — switching from a desktop browser to your phone, or the other way round, keeps your session, payment history and account settings matched to one profile.
Update it directly where account settings allow a change. If the field is locked — a payment method entry, for example — contact support with the correction so it gets applied to your bKash, Upay or Bank Transfer record.
Not exactly — access and data handling depend on your local law and the regions eligible to use 777js, since availability and account rules vary by market. Where a local rule sets a different standard, that rule takes priority over the general wording on this page.
Use the support route published on 777js and reference the specific record — a login, a payment note, or a device change on your account — so your question reaches the right desk instead of sitting in a general enquiry queue.