Reference

Open avatarslot Privacy Policy Clearly

avatarslot Privacy Policy explains how we collect, use and protect the account data connected to your lobby access, wallet status and support requests.

Plain-language policyPhone verification contextIndonesia wallet access
avatarslot Open avatarslot Privacy Policy Clearly
CONTACT PATHS

Ask About Privacy Before Account Access

Privacy questions should reach the same account support path used for login or wallet-status concerns, so we can connect your request with the right account record. Tell us which email or phone identifier is attached to your profile, and avoid sending a wallet password or full payment credentials. We can explain a data entry, help locate a policy request and confirm when a change has been applied.

Team online

Policy questions

Send a clear request about the avatarslot Privacy Policy through our account support path. Include the subject you need explained, such as phone verification, cookies or payment references, so we can respond without asking for unnecessary account data.

Access requests

If you need a copy of account data linked to your profile, state the phone or email identifier used at sign-in. We may ask for an account check before sharing records, helping keep another person from accessing your details.

Correction requests

Tell us which account field appears incorrect and what should change. We compare the request with your profile and payment status records, then explain any step needed before the corrected detail can be used for wallet or lobby access.

DATA PRACTICES

See How avatarslot Handles Your Policy

We apply the Privacy Policy to the practical moments that affect your account: opening access, verifying a phone, returning to the lobby on mobile and checking a wallet status.

Account collection

We collect the contact and verification details you provide when creating an account, including a phone identifier used for access checks. We use these details to connect your profile with sign-in events and account requests rather than asking for unrelated personal data.

Payment references

DANA, OVO, GoPay and QRIS may return a reference, amount and status for reconciliation. Bank transfer and virtual account records serve the same purpose. We use those references to match a request to your account, not to obtain your wallet password.

Cookies and devices

Cookies and device signals help keep a mobile session connected to the correct account and flag unusual sign-in patterns. You can manage browser cookie settings, but reducing them may affect the route from phone verification to the lobby.

Account security

Phone verification adds an account step before access, while sign-in records help us investigate a session that does not look familiar. Keep your verification details private and contact support if you see a login or wallet status you do not recognise.

Retention choices

We retain account, security and payment-reference records only as needed for the purposes described in the Privacy Policy, including support follow-up and required record keeping. A request to remove data may be limited when a record is needed for those purposes.

Your requests

You can ask what account data we hold, request a correction or ask how a record is used. Send the request through account support with your profile identifier; we may verify ownership before discussing or changing private account details.

Find Privacy Policy Answers For avatarslot

These Privacy Policy answers address the searches we hear before an account is opened or a wallet is connected. They cover the data behind phone verification, mobile access, cookies, local payment references and requests to change or receive account records. If your question is not listed, use the account support path and describe the specific policy point.

The avatarslot Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, payment references and support requests. It explains why we use each data type, how we protect account access and how you can request a copy, correction or clarification where local law permits.

No. Our Privacy Policy describes the transaction references and status details needed to match DANA, OVO, GoPay or QRIS activity with your account. We do not ask you to send a wallet password through support, and you should keep those credentials private.

Phone verification links the account to the contact detail you supplied and helps us check that a sign-in request belongs to you. Under the Privacy Policy, the verification record supports account security and access control; it is not a reason to request unrelated personal data.

When you open the lobby on a phone, we may use device signals and cookies to maintain your session, remember necessary settings and identify unusual access. You can adjust browser cookie controls, though limiting required cookies may interrupt the path after sign-in or verification.

Yes. The Privacy Policy lets you request a correction when an account field is inaccurate. Contact account support with the profile phone or email identifier and explain the change. We may verify ownership first, then confirm whether the correction also affects a wallet or access record.

You can request access to data connected with your profile and ask how it is used. You may also request removal where local law permits. Some security, payment-reference or record-keeping data may need to remain for the purposes stated in the Privacy Policy.

Use the account support path and label your message as a Privacy Policy request. Include the subject, such as cookies, phone verification, payment status or correction, plus your profile identifier. Do not include a wallet password or full payment credentials in the message.