Reference

6rt Privacy Policy For Your Account

The 6rt Privacy Policy explains what we collect, why we use it and how you can ask about your account records, wallet status or device access.

Account recordsWallet activityDevice accessCookie choices

Explore Our Lobby Read FAQ

What This Privacy Policy Covers

6rt Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers details you provide during account creation, such as contact credentials and phone verification, plus records created when you sign in, move through the lobby or ask support about a wallet status. We may connect transaction references from DANA, OVO, GoPay, QRIS, bank

1
transfer or virtual account steps with your account so we can identify a receipt or investigate a pending status. Device type, browser signals, security events and cookie choices help us protect access and keep pages working. We use this material for account operation, security, support and
2
legal duties that apply where local law permits. The policy does not change the payment provider’s own handling rules. Eligibility and access depends on local law, and you should read the current policy before opening or continuing an account.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

REQUEST PATHS

Get Help With Privacy Policy Requests

A clear request path helps you ask about the 6rt Privacy Policy without guessing which team to contact. Start from the support route linked to your account and include the email or phone detail used for access. For a payment question, add the DANA, OVO, GoPay or QRIS receipt reference so we can separate an identity request from a wallet-status check.

Team online

Account support

Use the support route attached to your account to ask what personal details we hold, why a phone check was requested or how to correct an account record.

Receipt context

For a privacy request linked to DANA, OVO, GoPay or QRIS, include the relevant receipt reference and approximate date so we can locate the right transaction record.

Access concern

If a login or device concern affects your request, tell us which device path you used and the account detail available to you; do not send a password or security code.

DATA PRACTICES

How We Handle Your Privacy Choices

We keep the Privacy Policy practical by linking each data use to an account, security or support need.

Data collected

We may receive account contact details, phone verification results, sign-in events, device signals and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Purpose of use

We use these records to provide account access, identify a wallet status, protect against suspicious sign-ins, answer support requests and meet duties that apply where local law permits.

Cookie controls

Cookies can remember a session, device preference or consent choice. You can adjust browser settings, although refusing required cookies may interrupt login or the path from your account to the lobby.

Account security

Phone verification, sign-in event checks and device signals help us assess account access. Keep your password and one-time security codes private, and contact support if an access event looks unfamiliar.

Retention timing

We retain account, support and transaction records only for the period needed for the stated purpose, security checks or applicable legal duties, then remove or restrict them under our retention process.

Change requests

Ask us to correct, access or clarify your personal details through the account support route. Include your account contact detail and the specific record you want checked; we may verify ownership first.

Privacy Policy Answers For 6rt Accounts

These Privacy Policy answers address the account, wallet and device questions we hear most often before someone opens an account. They explain the practical request path, while the full policy remains the reference for exact wording, retention decisions and access that depends on local law.

It covers account details, phone verification, sign-in and device signals, cookie choices, support records and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps connect you with the correct account and reduces mistaken access. We may use the result during login checks or a privacy request, but you should never send us your security code.

Yes. We may keep a payment reference, status or receipt detail needed to match an account request or investigate a transaction question. The payment provider has its own privacy rules as well.

Yes. Contact us through the support route linked to your account, identify the detail that appears wrong and provide your account contact detail. We may confirm ownership before changing the record.

Send an access request through account support and state which records you want checked, such as sign-in events, cookie choices or wallet references. We may ask for verification before responding.

Retention depends on the purpose, security needs and legal duties that apply where local law permits. Account, support and transaction records are restricted or removed when the applicable period ends.

Use the account support route and describe the device path, approximate sign-in time and account contact detail. Do not include your password, one-time code or full payment credentials in the request.

6rt Privacy Policy For Your Account

Get Help With Privacy Policy Requests

Account support

Receipt context

Access concern

How We Handle Your Privacy Choices

Data collected

Purpose of use

Cookie controls

Account security

Retention timing

Change requests

Privacy Policy Answers For 6rt Accounts

01 What does the 6rt Privacy Policy cover?

02 Why does 6rt need my phone verification?

03 Does the Privacy Policy include DANA and QRIS data?

04 Can I ask 6rt to correct my account details?

05 How can I request access to my Privacy Policy data?

06 How long does 6rt retain personal data?

07 What should I do if my device access looks unusual?

Related Pages