Reference

Legal access for your ran4d account

ran4d Legal details tell you how account access, payment records and personal data are handled before you open an account.

Account termsPrivacy controlsLocal accessContact route
ran4d Legal access for your ran4d account
HELP ROUTES

Get help with legal account steps

A clear contact path matters when a Legal question affects your account or wallet record.

Account access Use the support link shown after login when phone verification, account ownership or a Legal access condition needs clarification. Include the email or phone attached to your account, but never send your password or a one-time security code.
Wallet records For a DANA, OVO, GoPay or QRIS record, open the cashier status path and copy the transaction reference into your message. We use that reference to locate the relevant account entry without asking you to repeat payment credentials.
Policy requests Ask through the account support route when you need the current Legal wording, a privacy clarification or a correction request. Tell us which section concerns you, so our team can send a focused response and the next account step.
DATA PRACTICE

How account data is handled

Our Legal process is designed around records you can identify and questions you can send to us.

Data collection

We collect the account details you submit, verification results and payment references needed to connect an account with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. Our Legal wording explains why each category is used.

Cookie choices

Cookies can keep a signed-in session working and remember selected site settings. Our policy explains necessary cookies separately from optional settings, so you can understand the effect before changing a browser choice on your phone or desktop.

Account security

Phone verification is required before account access, and we use ownership checks before changing sensitive details. If a message asks for your password or one-time code, do not share it; use the account support route instead.

Record retention

We retain account, payment and support records only for the period needed for stated operational, dispute and legal purposes. The Legal notice explains the relevant categories, while a request can ask for clarification about a particular record.

Who to contact

Send privacy, access or correction questions through the support link inside your account. Include the policy section or record type involved, and we may verify account ownership before discussing personal details or making a change.

Policy changes

When Legal wording changes, we place the current version in the policy area and identify the affected subject. Check that page before using your account again, especially if the change concerns eligibility, data handling or wallet records.

Legal answers for ran4d accounts

These Legal answers address the searches we hear before account creation or a policy request. We keep the wording practical: what you submit, when access can proceed, how payment references are handled, and where to ask for a correction. If your situation is different, use the signed-in support route and quote the relevant policy section.

Legal covers account terms, access conditions, privacy handling, cookies, payment records and requests to change or correct account details. It also explains that access depends on local law, so the current policy should be checked before you open or continue using an account.

Yes. Account eligibility and access depends on local law. We cannot describe one access outcome for every location, so check the current Legal notice from Indonesia and contact support if an account step or regional condition is not clear.

Phone verification helps connect the account to the person requesting access and supports later ownership checks. Complete it before account access is enabled. If the verification step stalls, use the support link and provide your account phone or email without sharing a code.

DANA and QRIS references are used to match a payment event with the correct account record. They can appear in cashier or support history, but you should not send wallet passwords or security codes. Use the transaction reference when asking about a record.

Yes. Send a correction request through the signed-in support route and identify the data or policy section involved. We may verify ownership before changing details, then explain the next step or why a record must be retained.

Use the account support link for a question about cookies, stored details or retention. Tell us whether your request concerns browser settings, account data or a payment reference. We will use the applicable Legal wording to explain the available path.

Open the Legal area from the account or policy navigation and check the current version before proceeding. If you cannot reach it after login, contact support with your account email or phone and request the relevant policy section.