Reference

MAJ777 Privacy Policy For Your Account

MAJ777 Privacy Policy explains how we handle the account, wallet and device details you provide when you open an account or enter the lobby.

Account clarityWallet data controlsCookie choicesSecure account access
MAJ777 MAJ777 Privacy Policy For Your Account
CONTACT PATHS

Privacy Policy Help Beside Account Support

A clear contact path matters when a privacy request concerns a wallet record or a locked account. From the account help area, tell us whether you need a copy, correction, deletion request or explanation of a data use. Include the relevant phone number or payment reference so we can check the right record without asking for unnecessary details.

Team online

Account help

Use the account help contact when your Privacy Policy question concerns phone verification, sign-in records or a request to correct your personal details.

Wallet record

For DANA, OVO, GoPay or QRIS receipts, share the transaction reference rather than your wallet password. We use it to locate the relevant payment record.

Data request

Ask for a copy, correction or eligible removal of personal data through the same support path. We may verify account ownership before making a change.

ACCOUNT SAFEGUARDS

What MAJ777 Does With Your Data

Privacy Policy choices are connected to practical account controls, not hidden behind general wording. We separate identity details from wallet references where possible, limit staff access to operational needs and record security…

Account details

We use your phone number and verification record to link account access to the person completing the account step. We do not need wallet passwords to check a payment status.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a receipt to your account. They are handled for payment checks and support requests.

Device signals

Your browser, device type and session signals help us identify unusual access. On mobile, these checks can appear again when you move from login to the lobby.

Cookie settings

Cookies may keep a session active, remember a selected setting or help identify repeated sign-in errors. You can manage browser cookies, though some account steps may then need repeating.

Data retention

We keep account, security and transaction records for the period needed for operation, legal duties or a payment dispute. When that purpose ends, records are removed or restricted.

Change requests

To request a correction or eligible deletion, contact account help with the affected detail and your account phone number. We verify ownership before changing a record.

Privacy Policy Questions About MAJ777

These Privacy Policy answers cover the questions we hear most often before account access. They explain which records matter, how wallet references are handled and where to send a request. If your situation involves local eligibility or access, it depends on local law, and our account help path can clarify the next step.

It covers account details, phone verification, device and session data, cookies, security records and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We use the verification record to connect account access with the person completing the account step, detect unusual sign-ins and help resolve an access request without exposing another account.

We use the payment reference and status needed to match a receipt to your account or answer a support request. We do not ask for your wallet password to check that record.

Yes. Contact the account help path shown in your account area and request a copy of eligible personal data. We may verify ownership using your account phone number first.

Send the affected detail and your account phone number through account help. We check the request, confirm ownership and update eligible records when the correction is supported.

We retain records for the operational, legal or dispute-handling period connected with their purpose. After that need ends, records are removed, anonymised or access-restricted.

Yes. Cookies and session signals can remember settings, support sign-in continuity and identify repeated errors when you move from a mobile login to the lobby. Browser controls can limit them.