Reference

777rt Privacy Policy For Your Account

777rt Privacy Policy explains how we handle your account details, phone verification, wallet records and device access when you use our Indonesia service.

Account dataWallet recordsCookie choicesPolicy requests
777rt 777rt Privacy Policy For Your Account
HELP WITH REQUESTS

Browse Your Privacy Support Path

A clear support path helps you raise a Privacy Policy question without sending payment details into an unrelated message.

Account access If you cannot sign in after phone verification, use the account help route and state that your request concerns the Privacy Policy. We may ask for account identifiers or a verification step, but you should not send a wallet password, one-time code, or full payment credentials.
Wallet records For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account record, describe the date, amount reference, and status shown in your account. We use those details to locate the relevant record while limiting unrelated personal data in the support exchange.
Privacy request Ask us to access, correct, delete, or explain eligible personal data through the same support path. We first check account ownership, then assess the request under local requirements and tell you if a security, dispute, or legal record must remain.
DATA HANDLING

Explore How We Handle Policy Requests

Privacy work is part of the account flow rather than a separate promise hidden from you.

Account details

When you open an account, we receive the details needed to create it and may connect them with phone verification. We use those details for sign-in, account messages, security checks, and requests you send us, rather than treating every browsing visit as a full account record.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account status can create a reference linked to your account activity. We use that reference to reconcile a cashier event and investigate a receipt question; we do not ask support messages to include private wallet credentials.

Cookies and devices

Our mobile browser path may use essential cookies or device signals to keep a session working, remember security choices, and identify unusual login behaviour. Your browser settings can clear or restrict optional storage, though removing essential data may interrupt account access or phone verification.

Account security

Phone verification, login records, session checks, and account ownership questions help us protect your information. If a sign-in appears unusual, we may pause a request until you complete an account step. Never share your password or one-time code with a support contact.

Retention periods

We retain personal data only for the period needed for the stated purpose, account security, payment reconciliation, dispute handling, or a legal duty. When a retention period ends, we delete, anonymise, or securely isolate the record according to the applicable requirement.

Changes and contact

You can contact us through the privacy support route to request access, correction, deletion, restriction, or an explanation of a data use. We may update this Privacy Policy when our handling changes and will show the current wording before you rely on it.

Check Privacy Policy Answers Before Joining

These Privacy Policy questions cover the account steps you are most likely to consider before opening access through 777rt. We explain how data connects with phone verification, mobile sessions, local wallets and support requests without turning the policy into a general description of the lobby. If your situation is not listed, send a focused request through the privacy support route and we will assess it under applicable local requirements.

The 777rt Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages, payment references, security events, retention, and requests about your personal data. It explains why we use each category and when a record may need to remain for security or legal reasons.

When you use DANA or QRIS, we may receive a payment reference, status, and account link needed to reconcile the transaction. We use that information for cashier records, security, and support. Do not send your wallet password, PIN, or one-time code when asking about a status.

Where local law permits, you can ask us what eligible personal data we hold and how it is used. Send the request through the privacy support route, identify the account, and complete an ownership check. We may withhold details that would expose another person or weaken account security.

You can request a correction when an account detail is inaccurate and ask for deletion where the law allows it. We assess the request after checking ownership. Some payment, security, dispute, or legal records may need to remain, even when other information can be removed.

Yes. The Privacy Policy explains that essential cookies and device signals can keep your mobile session working, support phone verification, remember security choices, and detect unusual access. Your browser can restrict optional storage, but clearing essential cookies may require you to sign in again.

We keep each category for the period needed for its stated purpose, account protection, payment reconciliation, dispute handling, or a legal duty. Retention can differ between a login event, a support message, and a QRIS or bank transfer reference. We delete, anonymise, or isolate records when appropriate.

Yes, access depends on local law. Eligibility, data rights, retention duties, and available account actions can differ by location. Where local law permits, we process access, correction, deletion, restriction, or objection requests through our support route after verifying that you control the account.