Reference

markas338 Privacy Policy For Your Account

Our Privacy Policy explains how markas338 handles the details you provide when you open an account, verify your phone, use DANA or QRIS, and move through the lobby…

Account clarityWallet dataCookie choicesPolicy requests
Browse the Home lobby Read FAQ
markas338 markas338 Privacy Policy For Your Account
PRIVACY HELP ROUTES

Where To Ask About Your Privacy Policy

A clear support route matters when a privacy question sits beside a wallet receipt or a sign-in check.

Account privacy request Use the support path after signing in to ask for a copy, correction, or deletion review of personal data connected with your account. We may ask you to confirm the phone verification step before discussing account records.
Wallet record question For DANA, OVO, GoPay, or QRIS records, send the payment reference and date rather than a wallet password or security code. We use the reference to trace the status while keeping sensitive credentials out of support messages.
Cookie access concern If a mobile browser keeps an old session or blocks a policy page, tell us your device type and browser path. We can explain the account steps without asking for a screen recording or unrelated device content.
HANDLING YOUR RECORDS

What Our Privacy Process Covers

We handle privacy requests as part of the same account process used for phone verification and wallet status checks.

Account data

We may hold your phone number, account identifier, verification result, sign-in events, device details, and support history. These records help us connect a privacy request to the correct account instead of relying on a name alone.

Cookie use

Cookies can keep your session available, remember selected settings, and help identify unusual browser activity. You can clear or restrict cookies through your mobile or desktop browser, though some account steps may then need to be repeated.

Security checks

Phone verification and sign-in records help us check that a request comes from the account holder. Never place a password, wallet PIN, or one-time security code in a support message about this Privacy Policy.

Payment matching

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity, we use references and status details to match a transaction question. We do not need your wallet password to investigate a receipt or account record.

Retention approach

We retain account, security, support, and payment records only for the period needed for the stated account purpose, dispute handling, security checks, or legal duties. When a record is no longer needed, our process addresses its removal or restriction.

Change requests

Ask through the account support route if your phone detail, contact detail, or other personal record needs correction. We may request phone verification, then confirm the action taken or explain why a record must remain available.

Privacy Policy Questions For markas338

These Privacy Policy answers address the account questions we expect before you open an account or connect an Indonesian wallet. They explain the practical path for data access, cookie control, payment references, security checks, and contact requests. If your situation is not covered, use the account support route and describe the exact record or account step involved.

It covers personal details linked to your account, phone verification, sign-in and device records, cookies, support messages, and payment references. It also explains how we use those records for account access, security, receipt matching, and policy requests where local law permits.

We may collect the phone number and account details you submit, the result of your phone verification, sign-in events, device and browser details, support messages, and transaction references. We use each category for the account purpose explained in this Privacy Policy.

We use payment references, wallet status, and transaction dates to match an activity with your account or answer a receipt question. We do not need your wallet password or security code. The same approach applies to bank transfer and virtual account references.

Yes. Send the request through the signed-in account support path and state whether you want a copy or a correction. We may confirm the phone verification linked to your account before sharing or changing records, subject to local law and required retention.

Cookies may keep your session active, remember settings, and help us detect unusual sign-in behaviour. You can clear or restrict them in your mobile browser settings. After that change, you may need to repeat phone verification or another account step.

Retention depends on the purpose of the record, such as account access, security checks, support handling, payment matching, disputes, or legal duties. When the applicable purpose ends, we address deletion or restriction through our internal record process.

Sign in and use the account support route, then include your account phone detail, request type, and any relevant payment reference. Do not send passwords or wallet PINs. If access is unavailable, describe the sign-in issue so we can direct the request safely.

Related Pages

markas338 Indonesia Access guide bolahou About Us Account information