Reference

ribut4d Privacy Policy For Your Account

ribut4d Privacy Policy explains what we collect when you create an account, complete phone verification, browse from a mobile browser and use DANA or QRIS.

Clear data purposesWallet record contextMobile cookie choicesContact steps

Explore Our Lobby Read FAQ

Check How We Handle Wallet Data

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

Our Privacy Policy applies when you open an account, verify your phone number, sign in, browse the lobby or contact account support. We may record account details, verification results, device signals, cookie choices, login events and payment references needed to match a wallet action with the

1
correct account. DANA, OVO, GoPay and QRIS may appear in transaction records, while bank transfer and virtual account references can help us trace a status question. We use these records to provide access, detect unusual activity, answer requests and meet applicable legal duties. We do not
2
describe access as available everywhere: eligibility depends on local law. If you are in Bandung or elsewhere in Indonesia, the same policy access steps apply through the account area or our support route. Ask us to clarify a record before sending extra personal details.

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

CONTACT DATA CARE

Contact Us About Your Privacy Policy

A clear contact path helps when an account record looks wrong, a cookie choice needs changing or a wallet reference is difficult to identify. Start from your signed-in account support route and include the relevant account step, such as phone verification or a QRIS receipt. We ask you to share only the details needed to locate the request.

Team online

Account support route

Use the support path inside your account for a Privacy Policy question. Tell us whether it concerns phone verification, login records or a DANA, OVO, GoPay or QRIS reference.

Data access request

Ask us to locate the personal data connected with your account. We may request account details or a verification step before discussing records, helping prevent disclosure to the wrong person.

Correction request

If your contact detail or transaction reference needs correction, describe the specific field and account step. We will assess the request and explain any record that must remain for legal or security reasons.

DATA CONTROL PATH

See How We Protect Your Privacy

Privacy work is tied to ordinary account actions rather than hidden processes. We separate identity checks from routine browsing signals, limit access to records needed for support and…

Account details

We handle the details you provide during account creation and phone verification so we can identify the correct account.

Device signals

A mobile browser may send device and login signals that help us recognise unusual access.

Cookie choices

Cookies can remember session settings and help us understand whether a sign-in step has completed.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may be retained beside transaction status.

Security checks

Phone verification and sign-in checks help us confirm that a privacy request comes from the account owner.

Retention requests

You may ask why a record is retained, request a copy where applicable or ask for correction.

Find Answers About Your Data

These Privacy Policy answers focus on the account situations you are most likely to search for before opening an account. We keep the steps practical: identify the record, use the account support route and complete any verification needed to protect your details. If access is restricted, that position depends on local law.

It covers data connected with account creation, phone verification, sign-in, mobile browsing, cookies, support requests and wallet references such as DANA, OVO, GoPay and QRIS.

Use the signed-in account support route and ask for a data access request. Include the account step involved; we may verify your phone or account details before sharing records.

Yes. Our Privacy Policy covers relevant device signals, login events and cookie settings from a mobile browser. Browser controls can change cookies, but they may also require another sign-in.

Wallet references help us match a payment status or receipt with the correct account. We use the reference for support and reconciliation, rather than asking you to repeat every transaction detail.

You can ask for correction through account support by naming the exact field or reference. We assess the request and explain if a record must remain for security or legal duties.

Retention depends on the record and its purpose. Login, verification or wallet entries may remain while needed for account security, dispute handling or duties that apply where local law permits.

Start with the support route inside your account and describe the privacy concern without sending unnecessary personal material. We can then identify the correct request and explain the next verification step.

ribut4d Privacy Policy For Your Account

Contact Us About Your Privacy Policy

Account support route

Data access request

Correction request

See How We Protect Your Privacy

Account details

Device signals

Cookie choices

Wallet references

Security checks

Retention requests

Find Answers About Your Data

01 What does the ribut4d Privacy Policy cover?

02 How can I request my ribut4d account data?

03 Does Privacy Policy cover mobile browser data?

04 Why are DANA or QRIS details linked to my account?

05 Can I correct personal data held by ribut4d?

06 How long does ribut4d keep privacy-related records?

07 Who should I contact about a Privacy Policy concern?

Related Pages