Reference

Open generasislot Privacy Policy Before Account Access

Our Privacy Policy explains what generasislot records when you create an account, sign in from a phone or desktop, use DANA or QRIS, and contact support about a…

Account data explainedWallet records coveredCookie choices includedSecurity steps outlined
generasislot Open generasislot Privacy Policy Before Account Access
CONTACT ROUTES

Use Support When Privacy Questions Stall

A clear contact path matters when a login record, payment receipt or account detail does not look right.

Account access request If phone verification blocks your account, contact support from the account path and state…
Wallet record question For a DANA, OVO, GoPay or QRIS receipt concern, provide the payment reference and…
Privacy change request Ask us to correct an account detail or explain a stored record through the…
DATA PRACTICES

Explore Your Data And Security Choices

Our handling process follows the account journey rather than collecting every detail by default. We separate contact, device, payment-reference and activity records, apply access checks to account changes, and use retention periods…

Account details

We use your submitted contact details for account access, phone verification and replies to privacy requests. If a name or contact entry is wrong, ask us to correct it through the account support path.

Device signals

A phone or desktop session can create records such as browser type, login time and security events. These signals help us compare a new sign-in with your account without reading unrelated device content.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may leave reference and status records. We use them to match account requests and receipts, not to request your wallet PIN.

Cookies and sessions

Cookies can keep your sign-in session connected to the correct account and record a policy-page visit. Your browser settings can control cookies, although changing them may affect account access.

Security controls

Phone verification and account checks help us respond to unusual access, including a change from mobile to desktop. We may ask for account details before discussing a private record.

Retention and requests

We retain records only as needed for account service, payment queries, disputes or legal duties. You can ask about retention, access, correction or deletion through the available support contact.

Browse Answers About Your Privacy Policy

These Privacy Policy answers address the searches we receive before account creation: what is collected, why wallet records appear, how device sessions work and how to request a change. If your question concerns a specific login or payment reference, include that context through the private support path rather than posting it publicly.

It covers account details, phone verification, device and session records, cookies, payment references, support requests, retention and available rights. It applies to processing connected with your account where local law permits.

A DANA or QRIS transaction can create a reference and status record linked to your account request. We use that record to check payment questions and do not need your wallet PIN.

We may store technical signals such as device type, browser session, login time and security events. These help us protect account access; they do not give us access to unrelated files on your device.

Use the account support path and describe the incorrect detail, such as a contact entry or payment reference. We may confirm your account step before changing a record linked to your identity.

Retention depends on the record and whether it supports account service, a payment question, a dispute or a legal duty. Ask support which retention reason applies to the record you name.

You can request deletion or ask whether a record can be removed where local law permits. Some records may need to remain for account security, unresolved disputes or legal duties.

Use the private support route beside the account or cashier path. Include your account contact, device type and approximate event time, but never send a wallet PIN or unrelated private credentials.