Reference

star77 Privacy Policy for Your Account Data

star77 Privacy Policy explains what we collect when you create an account, verify your phone, use DANA or QRIS, and contact our support desk.

Account dataWallet recordsCookie choicesContact requests
star77 star77 Privacy Policy for Your Account Data
CONTACT PATHS

Contact star77 About Your Account Data

A direct support path helps when a Privacy Policy question concerns your login, wallet status or a personal-data request.

Account contact Send a Privacy Policy question from the account contact path so we can match your request with the verified phone number without asking you to repeat unrelated wallet details.
Wallet status For DANA, OVO, GoPay or QRIS records, provide the transaction reference and date. We use those details to trace the status while keeping your account credentials private.
Cashier help If a receipt or account record looks wrong, use the help route beside the cashier area. We can explain which data was used and what correction request we need.
DATA PRACTICES

Security Around Wallet And Lobby Data

We handle Privacy Policy requests through the same account controls used for phone verification and sign-in protection.

Data we collect

We may hold your account name, phone number, verification result, device details, sign-in events, wallet references and support messages when those records help operate or protect access.

Cookie controls

Session cookies keep your login path working, while preference cookies can remember selected settings. Your browser controls let you clear stored cookies, though sign-in may need verification again.

Account security

Phone verification helps us connect an access request to your account. Never send a password or one-time code in a support message, even when asking about Privacy Policy.

Retention timing

We retain records for the period needed for account operation, payment matching, security checks and legal duties. Ask support which retention reason applies to a specific record.

Change requests

You can request correction, access or removal of eligible personal data by contacting support from your account path. We may verify ownership before changing or releasing a record.

Who receives requests

Our support team handles Privacy Policy questions and routes wallet or security details to the relevant account process. We do not need your full payment credentials to begin.

Privacy Policy Questions About Your Account

These Privacy Policy answers address the searches we hear most often before account access. They explain the records connected with phone verification, cookies, local wallets and support requests, while keeping the legal position clear: access depends on local law. If your question concerns a particular transaction, include its reference rather than sending complete card or wallet credentials.

It covers account details, phone verification, sign-in events, device signals, cookies, wallet references and support messages used to operate and protect your account where local law permits.

Yes. When you use DANA or QRIS, we may keep the transaction reference, amount status and timing needed to match the wallet action with your account and answer receipt questions.

Contact support through your account path and ask for a data copy. Include your verified phone number and the record type you want, but do not send passwords or one-time codes.

Yes. Send the correction request from your account contact route and describe the record clearly. We may verify account ownership before changing details linked to phone or wallet activity.

Session cookies help keep your login active and preserve selected settings. You can clear them in your browser, but doing so may end the session and require phone verification again.

Retention depends on the reason for keeping a record, including account operation, payment matching, security checks and legal duties. Support can explain the applicable reason for a specific entry.

Use the support contact shown inside your account and state whether you want access, correction or removal of eligible data. We will explain the next verification step where local law permits.