Reference

rekening168 Privacy Policy For Your Account

Our Privacy Policy explains how we handle your account details, device signals and payment records when you use rekening168.

Account dataPayment recordsDevice choicesContact route
rekening168 rekening168 Privacy Policy For Your Account
CONTACT OPTIONS

Get Privacy Policy Help Directly

You do not need to search through account screens to ask about privacy. We provide a support path linked beside the cashier area, so you can raise a data question while checking a DANA, OVO, GoPay or QRIS reference. Include your account contact, the subject of your request and any relevant receipt number; please remove wallet passwords and unrelated private details before sending.

Team online

Privacy request

Use the support route beside the cashier when you want to ask what account, device or payment data we hold. We will use your account details to locate the correct record.

Receipt question

For a QRIS, DANA or bank transfer record, share the transaction reference and date rather than private wallet credentials. This helps us check the status without collecting unnecessary access data.

Account access

If phone verification or sign-in blocks your privacy request, tell support which step stopped and which device path you used. We can direct the request without asking for your password.

DATA HANDLING

Six Practical Privacy Safeguards

Privacy is handled through small account actions rather than a vague promise. We separate payment status from wallet credentials, use security checks around sign-in and phone verification, and give you a route…

Account records

We use your account contact and phone verification status to match requests to the right account. This reduces mistaken changes when several accounts share a device or payment reference.

Payment separation

DANA, OVO, GoPay and QRIS data is treated as transaction context: reference, status, amount and time. We do not need your wallet password to investigate a receipt.

Cookie choices

Cookies and similar device signals can support session continuity, security checks and preference storage. Ask support which cookie category relates to your concern and what change is available.

Security events

Login timestamps, device details and verification events may be checked when access looks unusual. We use these records to protect the account and explain a sign-in decision.

Retention review

We keep personal and payment records for operational, security or legal needs. When a record is no longer required, we remove it or restrict its use according to applicable rules.

Change requests

You can ask us to correct account details, explain a data use or consider deletion. Send the request through support with enough account context, while excluding passwords and wallet codes.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the account and payment questions you are most likely to have before opening an account. We keep the process practical: identify the account, describe the data question, and use the support path beside the cashier when a record needs checking. Access depends on local law and applies where local law permits.

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

Phone verification helps connect account access to the correct contact and supports security checks. It can also help us locate a privacy request without asking you to send a password.

Yes. We may handle transaction references, status, amount and time for DANA and QRIS, along with similar records for OVO, GoPay, bank transfer and virtual account payments.

Contact support through the route beside the cashier, identify your account contact and state whether you want access, correction or an explanation. Do not include wallet passwords or security codes.

We retain records for operational, security or legal needs, then remove or restrict them when they are no longer required. The period can depend on the type of record and applicable law.

Yes. Ask support which cookies or device signals relate to your session, security check or saved preference. We can explain the purpose and tell you what adjustment is available.

Our handling is provided where local law permits, and access depends on local law. If your location or eligibility creates a question, contact support before sending account or payment details.