Reference

quark slot Privacy Policy In Plain English

quark slot Privacy Policy explains what we collect when you open an account, sign in from a phone, and use DANA, OVO, GoPay or QRIS for wallet activity.

Account recordsWallet activityDevice cookiesYour requests
quark slot quark slot Privacy Policy In Plain English
CONTACT YOUR WAY

Privacy Questions Through Your Account

A clear contact route helps you act on this Privacy Policy without guessing where a request belongs. From your signed-in account, open the support panel and describe whether you need a copy, correction, deletion request or explanation of a wallet record. Include only the details needed to locate your account; do not send a full wallet password or one-time phone code. We may ask you to confirm account ownership before discussing personal records, and access depends on local law.

Team online

Account support panel

Use the support panel after login for a Privacy Policy question, a request to correct your name or phone record, or a query about information linked to your account. We may confirm the registered phone before sharing account-specific details, so your request stays connected to the right profile.

Wallet status query

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the date, amount and visible status from the wallet screen through support. We use those details to locate the relevant record without asking you to disclose your wallet PIN, password or one-time verification code.

Device access check

A phone sign-in that looks different may trigger an account check before we discuss personal data. Tell us the device path you used, such as mobile browser login, and whether the phone verification step completed. This helps us separate an access concern from a normal session change.

DATA HANDLING

What We Do With Your Account Records

Your Privacy Policy choices matter most when the handling steps are visible. We limit internal access to records needed for account operation, security checks, support and legal duties, while wallet references remain…

Account data

When you open an account, we handle the details needed to create and protect it, including your registered phone and verification result. We use the account step to reduce mistaken identity when you later ask about a session, wallet reference or personal record connected with your profile.

Wallet references

A DANA, OVO, GoPay or QRIS status can create a reference in our records so we can match the wallet event with your account. Bank transfer and virtual account references are handled in the same practical way, without asking us to store your wallet PIN.

Cookies and browser use

Cookies can keep a signed-in session, remember a selected setting or help us understand an error on the mobile lobby. You can remove cookies in your browser controls. After removal, the account may require phone verification again before personal account details are shown.

Security signals

We may use sign-in time, browser type, device signals and failed verification events to protect account records. These checks can appear when you move from a mobile browser to desktop or when a session changes unexpectedly, helping us ask for the right account confirmation.

Retention choices

We keep personal records for the period needed to provide the requested account service, resolve a stated support matter or meet a legal duty. When you ask how long a particular record remains, tell us its category, such as login, cookie or QRIS reference, so we can answer precisely.

Changes and contact

You can ask us to correct inaccurate account details, explain a data use or consider a deletion request through the signed-in support panel. We may need phone verification or another account check first, and some records may remain where a legal duty requires their retention.

Privacy Policy Questions About quark slot

These Privacy Policy answers address the account and device questions you are most likely to have before opening an account from Indonesia. We describe the practical request path rather than hiding behind broad wording: where to ask, what details to include, why a phone check may appear and how wallet references are handled. If your question is not covered, use the signed-in support panel and mention the exact record or screen involved.

It covers personal details connected with your account, phone verification, sign-in events, cookies, device signals, support messages and wallet references. That includes activity connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account when those records are needed for account operation or a stated legal duty.

Phone verification helps us confirm that a request comes from the account holder before we discuss personal records or change account details. It may be requested after a new mobile browser sign-in, an unusual session change or a request involving wallet activity. Never send us your one-time code.

Yes. Send the request through the signed-in support panel and state that you want a copy of the personal records connected with your account. Mention the relevant category, such as login, cookie or QRIS reference. We may confirm ownership first, and the response depends on local law.

Use the account support panel after login and identify the field that needs correction, such as your registered phone. We may ask you to complete the phone verification step before making a change. Please provide the accurate replacement detail, not your password or wallet PIN.

Yes. Our Privacy Policy covers cookies used to keep a mobile browser session, remember settings or help identify an access error. You can clear them in your browser settings. Clearing cookies may sign you out and can require phone verification before account records appear again.

We retain each category for the period needed for its stated purpose, an unresolved support matter or an applicable legal duty. Ask through the support panel about a particular login, device, wallet or cookie record. We can then explain the relevant retention position, subject to local law.

You can ask us to consider deletion through the signed-in support panel and identify the records involved. We first confirm account ownership and assess the request against operational and legal requirements. Some records may need to remain for a stated legal duty, and access depends on local law.