Reference

markasgg Privacy Policy for Your Account

Our Privacy Policy explains how markasgg handles the details connected with your account, including phone verification, wallet activity and device access.

Account dataWallet recordsCookie choicesContact requests
markasgg markasgg Privacy Policy for Your Account
PRIVACY CONTACTS

Contact Us About Your Privacy Policy

A clear contact route helps you ask about the Privacy Policy without searching through payment screens.

Policy questions Send a question through the support contact path with the policy section or data type you mean. We can explain account records, cookies, phone verification and payment references.
Access requests Ask us to identify the personal data linked to your account through the available support route. Include your registered contact detail so we can check the request safely.
Wallet records If your question concerns DANA, OVO, GoPay, QRIS or a bank transfer reference, tell us the relevant account action without sending a password or full security code.
DATA HANDLING

Switch On Clear Data Choices

We describe the practical controls behind the Privacy Policy so you can make an informed account decision.

Account details

We use the contact details and phone verification steps you provide to create, secure and maintain your account. Keeping your registered phone current helps us match privacy requests to the right record.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account action can create a reference, amount and status record. We use those details to reconcile account activity and answer wallet questions.

Device signals

When you move from login to the lobby on a phone or desktop, technical signals may help identify unusual access, maintain sessions and protect your account from unauthorised activity.

Cookies

Cookies can remember session settings and your choices about site functions. You can manage browser cookie controls, although changing them may affect login continuity or the way policy notices appear.

Retention

We retain account, security and payment-reference data only for the period needed for the stated service purpose, account records, dispute handling or a legal requirement that applies where local law permits.

Changes and removal

Use the support contact path to request correction, access or another permitted change. We may verify your identity first, then explain what can be changed, retained or restricted under the current policy.

Browse markasgg Privacy Policy Answers

These Privacy Policy answers address the account questions you may have before entering your details. They cover payment references, mobile access, cookies, retention and requests for copies or changes. If your situation is not listed, contact us through the site support path and mention the account step or data type involved.

It covers account details, phone verification, payment references, device signals, cookies, security records, retention and requests connected with your use of markasgg where local law permits.

Yes. The policy explains how we handle references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account actions. Payment providers may keep separate records under their own terms.

Phone verification helps connect an account request with the correct contact detail and supports account security. It also lets us check that a privacy request comes from the relevant account holder.

When you use a phone or desktop browser, we may handle session and security signals linked with login activity. These details help identify unusual access and maintain the account path.

Use the support link on the site or inside your account, state that you want a data access request and provide your registered contact detail. We may verify identity before responding.

Yes. Send a correction request through the available support path and identify the record that needs attention. We will check the account, explain any required proof and apply permitted changes.

Retention depends on the record and its purpose, including account security, payment reconciliation, disputes or legal requirements. The Privacy Policy explains the applicable approach where local law permits.