Reference

markaswd Privacy Policy Explained Clearly

markaswd Privacy Policy shows how we collect, use, store and protect the details connected with your account, phone verification and wallet activity.

Account dataCookie choicesWallet recordsAccess requests
markaswd markaswd Privacy Policy Explained Clearly
CONTACT ROUTES

Privacy Questions Near Your Account

A clear contact route helps when you want to ask about the Privacy Policy rather than solve a lobby question. We connect your request to the relevant account or cashier context, so you can describe the issue precisely. Include the email or phone detail linked to your account, but never send a password or one-time verification code.

Team online

Account data request

Use the support contact shown in your account area to ask what personal details we hold, why we use them, and which account step your request concerns.

Wallet record query

For DANA, OVO, GoPay or QRIS records, include the transaction reference and date. We can match the receipt or wallet status without asking for your secret code.

Access and correction

If phone verification or a device login creates a data concern, tell us what changed and request correction or access through the same support path.

DATA PRACTICES

How We Handle Account Privacy

Our Privacy Policy is applied to the practical moments around your account: signing in, confirming a phone, checking a wallet status and asking for help.

Collected details

We may collect your contact details, phone verification result, login timestamps, device information and support messages when those details are needed to provide or protect account access.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account action can create a reference, amount, status and time record; we do not need your wallet password.

Cookie controls

Cookies can keep a session active or remember a device preference. You can adjust cookie settings in your browser, although blocking some cookies may affect account access.

Account security

Phone verification, login monitoring and checks around sensitive account actions help us identify unusual access. Keep your password and verification code private, including when contacting support.

Retention period

We retain account and transaction records for the period needed for service operations, dispute handling and applicable legal duties, then remove or anonymise them when no longer needed.

Changes and contact

You can ask for access, correction or clarification through our support contact path. Tell us which detail needs attention so we can locate the correct account record.

Privacy Policy Answers for markaswd

These Privacy Policy answers address the account and wallet questions you may search before opening an account. If your situation is not covered, use the support route beside your account area and describe the relevant device, verification or payment record.

It covers account details, phone verification, login and device signals, cookies, support messages, and transaction references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use the verification result to help confirm account access, investigate unusual sign-ins and respond to account requests. We do not need your password or wallet security code for this process.

Yes. The Privacy Policy explains that cookies may keep your session active or remember a device preference. You can manage them through browser settings, though blocking some may affect sign-in.

You can request access through the support contact shown in your account area. Include the account email or phone detail and describe the records you want us to locate.

Send a correction request through our support path and identify the inaccurate detail, such as a contact record or verification status. We may ask for account checks before changing it.

We retain wallet references, status details and related account records for operational needs, dispute handling and applicable legal duties. When those purposes end, we remove or anonymise records when appropriate.

Access and eligibility depends on local law. The Privacy Policy describes our handling approach, while legal requirements may affect which requests we can complete and which records we must retain.