Reference

marvel77 Privacy Policy for You

DANA, QRIS and a clear account step should not come with guesswork about your personal data.

Account dataWallet recordsDevice choicesContact path
marvel77 marvel77 Privacy Policy for You
CONTACT ROUTES

Browse Privacy Help Through Account Support

A clear contact route matters when you want to ask about personal data rather than wallet status.

Policy questions Use the account help path to ask how marvel77 handles sign-in records, cookie choices…
Access requests Ask for a copy, correction or deletion assessment through the stated contact route.
Wallet concerns If a payment receipt contains personal details, mention the rail used and the account…
HANDLING PRACTICE

Explore How Your Policy Works

Privacy decisions should match real account actions. We apply the policy to the moment you create an account, confirm contact details, sign in on a phone, open a game category or request…

Data use

We use account, session and transaction references to provide requested access, answer support questions, detect unusual sign-ins and maintain records required for the service.

Cookie choices

Cookies and similar device storage can remember session settings and consent choices. Your browser controls can remove them, although some account steps may then need repeating.

Account security

A clear account path, contact verification and unusual-access checks help protect your records. Never share your password, wallet PIN or one-time verification code with support.

Retention approach

We keep records for the period needed for the stated purpose, account support, dispute handling or applicable legal duties. The Privacy Policy explains how those needs guide removal.

Payment references

DANA, OVO, GoPay and QRIS may appear as transaction references rather than full wallet credentials. Bank transfer and virtual account records can follow the same separation.

Change requests

Contact us through the account help route to request correction, access or deletion review. We confirm ownership first and explain any legal reason a record must remain.

Check Privacy Policy Answers Before Joining

These questions focus on the points Indonesian account holders usually need before creating access or contacting us. Each answer follows our Privacy Policy and the practical steps you take on mobile, desktop or through a local wallet.

It covers account details, verification responses, device and session signals, cookie choices, support messages and payment references created when you use the service where local law permits.

We use details supplied during account creation to provide access, confirm account ownership, answer requests and protect sign-in activity. Eligibility still depends on local law and applicable requirements.

Yes. It explains how we handle references showing a DANA or QRIS request, while DANA, OVO, GoPay and other payment providers manage records held in their own systems.

We may receive browser, device, connection and session signals needed to keep the account path working, remember cookie choices and identify unusual access from a phone or desktop.

Use the account help contact route, describe the request and provide enough account detail for matching. We may verify ownership before releasing, correcting or assessing the requested record.

You can submit a deletion request through the stated contact path. We assess it against service needs, dispute handling and applicable legal duties, then explain any record that must remain.

Contact us through account help with the cookie or retention question. We can explain the relevant policy section, browser choice and the reason a record may still be stored.