Reference

Privacy Policy For Your star55 Account

Our Privacy Policy explains how star55 handles the details connected with your account, wallet activity and lobby access.

Account clarityWallet recordsPrivacy requestsCookie choices
star55 Privacy Policy For Your star55 Account
PRIVACY HELP DESK

Get Clear Answers About Your Data

A privacy question should not leave you guessing about the next step. Contact our support desk from the account or cashier path and tell us whether your request concerns login data, wallet…

Account privacy request Ask us to confirm the personal details connected with your star55 account, explain why a field is needed or correct an error. We first check the account step and phone verification status so private account data is not disclosed to another person.
Wallet record question If a DANA, OVO, GoPay, QRIS, virtual account or bank transfer record looks unfamiliar, include its date and status when contacting support. We can trace the account event without asking you to send a wallet password or full banking credentials.
Cookie and device help Tell us if a cookie choice, browser setting or mobile login is affecting your privacy preferences. We can explain which setting controls the site session and which device details may be retained for account security or repeated login checks.
DATA CARE ROUTINE

What We Do With Your Privacy Choices

Privacy work is part of the account flow, not a separate promise added after payment. We separate contact details, verification events, wallet status and device signals by their operational purpose, limit internal…

Account data

We use the name, contact details and phone verification result you provide to create and maintain your account. These fields help us distinguish your login from another account and let support answer a request without mixing your records.

Payment matching

A wallet or bank record is used to match a cashier event with the correct account. DANA, OVO, GoPay, QRIS, virtual account and bank transfer entries can carry a status and timestamp, while we avoid requesting your private wallet password.

Device signals

Browser type, device settings and connection signals may be recorded when they help us identify failed logins or unusual access. These signals support account security; they are not used as a reason to collect unrelated content from your phone.

Cookies

Cookies can keep your session open, remember a selected privacy setting and help the account path load correctly on mobile or desktop. You can manage or clear them in your browser, although removing some cookies may require another login.

Retention period

We retain account, verification and payment-status records only as long as needed for account operation, security checks, dispute handling or a legal requirement. When a record is no longer needed, we delete it or remove details that link it to you.

Changes and contact

You can ask about access, correction, deletion or the purpose of a data field through support. We may request account confirmation, assess the request under local rules and explain any record that must remain for security or legal reasons.

Privacy Policy Questions For star55

These Privacy Policy answers focus on the questions you may have before creating an account or checking a wallet record. We keep the wording practical: what we collect, how we use it, what happens on a mobile device and how you can contact us. If your request involves a specific account, use the support path after signing in where local law permits.

The star55 Privacy Policy covers account details, phone verification, login and device signals, cookies, wallet and bank-transfer status records, support requests, retention and privacy choices. It explains why each category is used and how you can ask for access, correction or deletion.

We may store the payment rail, account reference, timestamp and status needed to match a DANA, OVO, GoPay or QRIS event. We do not need your wallet password for that match. Virtual account and bank transfer records can be handled in the same operational way.

Phone verification helps confirm that the account access request belongs to you and reduces confusion when login support is needed. The verification result can be retained with the account record for security and service handling, subject to the Privacy Policy and local requirements.

Yes. Contact the support desk with the account detail you want to access or correct. We may confirm your identity through the account step before responding. If a record must remain for security, payment matching or a legal reason, we explain that limit.

On mobile, cookies can keep your session active, remember a privacy selection and help the route from login to the lobby load correctly. Your browser lets you clear or restrict them. Clearing cookies may sign you out and can remove saved preferences from that device.

We keep records for the period needed to operate the account, complete security checks, resolve a payment-status question or meet an applicable legal duty. After that period, we delete or anonymise them when possible. Support can explain the category and reason for retention.

Yes. Use the support path to ask about a Privacy Policy change, a new data field, cookie handling or a privacy request. Include your account contact and the topic, but never send a wallet password. Account access and any request outcome depend on local law.