Reference

Open Privacy Policy Before Your Account

einstein 22 slot Privacy Policy explains how we handle details connected with your account, including phone verification, DANA, OVO, GoPay and QRIS records.

Account dataWallet recordsCookie choicesContact requests
einstein 22 slot Open Privacy Policy Before Your Account
ASK OUR TEAM

Contact Us About Privacy Policy

A clear contact route matters when you want to ask what data we hold or why a wallet record appears in your account.

Account support form Send a Privacy Policy question through the support form inside your account. Add the phone or email connected to your profile, plus the subject of your request, so we can identify the correct record without asking for your password.
Cashier data query If your question concerns DANA, OVO, GoPay, QRIS, bank transfer, or virtual account data, mention the payment rail and receipt reference. We use those details to locate a status check while keeping your secret wallet credentials out of the message.
Access correction request Ask us to correct an account detail through the same support path. Confirm the profile contact detail when requested, and we will explain the next account step for checking, updating, or clarifying the personal data linked with your access.
DATA CONTROL

Browse Security Details Beside Your Login

We treat Privacy Policy questions as account matters rather than generic messages. Our process connects the policy with the practical events you can recognise: phone verification before access, login activity on a…

Account details

We handle the details needed to create and maintain your account, such as your contact information, verification status, login records, and requests sent to support. We use these details to connect the right person with the right account action and to reduce confusion during access checks.

Device signals

When you open the lobby on a phone or desktop browser, technical signals such as browser type, device identifiers, and login time may be recorded. These signals help us recognise unusual access and investigate a security question without reading private content stored on your device.

Cookie choices

Cookies and similar tools may remember a session, support account navigation, or help us understand which policy page brought you to the support path. Your browser settings can control some cookies, although changing them may affect login continuity or the way account pages load.

Wallet records

A cashier action can create a record for DANA, OVO, GoPay, QRIS, bank transfer, or virtual account processing. We use the rail name, account reference, status, and receipt details to reconcile the request; we do not need your wallet password for that check.

Retention checks

We keep account, security, support, and payment records only for the period needed for the stated service purpose, account protection, dispute handling, or duties that apply where local law permits. You can ask support why a particular record remains and what rule guides its retention.

Change requests

To request access, correction, or clarification, use the account support form and identify the profile detail involved. We may ask for a matching account contact or verification step before discussing personal data, so a request does not expose your records to someone else.

Find Privacy Policy Answers Quickly

These Privacy Policy questions address the account and wallet situations you are most likely to search for before opening access. Each answer points back to a practical step: checking the policy page, using the support form, confirming a phone detail, or identifying a payment reference. If your question is not listed, contact us through the account support route and describe the data issue in plain English.

The Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages, and records connected with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account requests. It also explains retention, security handling, correction requests, and the contact route for privacy questions.

Phone verification helps connect access to the correct account and supports security checks when you sign in from a new browser or device. We may retain the verification result and related account event as part of access protection. Do not send your one-time code through support messages.

Yes. The Privacy Policy covers records showing that a DANA or QRIS request was created, received, checked, or matched with your account. We may use a reference, amount status, timestamp, and rail name for reconciliation. Wallet passwords or secret access codes are not needed for that check.

Open the account support form and ask for a data access request. Include the email or phone detail attached to your profile and describe the records you want checked, such as login events or a GoPay status reference. We may request an account verification step before disclosing personal data.

You can ask us to correct inaccurate account data through the support form. Name the field that needs attention and provide the matching profile contact detail. For a wallet record, include the DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference so we can check the source.

On a mobile browser, cookies may keep your session active and support movement between login, policy pages, and the lobby. Browser controls can remove or restrict them, but that may require another login or affect page loading. The policy explains the purposes connected with these browser signals.

Access depends on local law. We do not treat an Indonesian location, device, or payment rail as permission by itself. If you are unsure whether an account action is available, check the current policy wording and contact support through your account path before submitting personal or wallet details.