Reference

apk rejekibet Privacy Policy for Your Account

Clear account records and wallet handling sit at the centre of our Privacy Policy: we explain what we collect when you create an account, sign in on mobile…

Account detailsWallet activityCookie choicesSupport requests
apk rejekibet apk rejekibet Privacy Policy for Your Account
HELP WITH PRIVACY

Ask About Your Data Through Support

A direct support path helps you ask what a record means, request a correction, or check a privacy question before opening an account. Use the help form linked from the sign-in area and include only the details needed to locate your request. Our account-help route can also connect a policy question with a wallet receipt or device sign-in without asking you to post sensitive data publicly.

Team online

Policy questions

Use the account help form to ask how apk rejekibet collects, uses, or stores a specific detail. Tell us the account step involved and avoid sending passwords or wallet PINs.

Correction requests

If your phone number or account detail is inaccurate, request a change through support. We may ask for account matching details before editing the record, so the request reaches the right account.

Wallet records

For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account query, attach the receipt reference only through the private support route. We use it to locate status data.

DATA HANDLING

Browse How We Handle Your Data

We keep this policy practical by linking each data use to an account action: registration, sign-in, wallet status, support, or security checks.

Account details

During account creation, we may use your submitted contact details to identify the account, send access-related messages, and handle a correction request. We do not need your password in a support message.

Cookies and devices

Cookies and device signals can help keep a sign-in session working and show the correct account state. You can manage browser cookie settings, though changing them may affect policy-page or sign-in access.

Wallet records

A DANA, OVO, GoPay, or QRIS action can create a payment reference linked to your account. Bank transfer and virtual account records may be retained to match receipts and resolve status questions.

Account security

We use account steps such as phone verification before access to reduce mistaken or unauthorised entry. Keep your password and wallet credentials private, and contact support if a sign-in record looks unfamiliar.

Retention choices

We retain personal data only for the operational, dispute, security, or legal purposes described in this Privacy Policy. A deletion or restriction request may depend on records we must preserve.

Your requests

You can ask what personal data we hold, request a correction, question its use, or seek deletion through the private help form. We may verify account ownership before responding to protect your records.

Find Answers About Privacy Policy

These Privacy Policy answers cover the searches we hear most often before account access. They explain why information is requested, how payment references and cookies fit into the record, and where to send a personal request. If your situation involves a specific device or wallet receipt, use the private support route so we can check the correct account.

The Privacy Policy covers account details, phone verification, device signals, cookies, wallet references, support messages, retention, security, and requests to access or change your personal data.

Phone verification helps connect the account to the correct access step and can reduce mistaken entry. We use the related detail for account handling and security as described in the Privacy Policy.

Yes. The Privacy Policy explains how DANA, QRIS, OVO, GoPay, bank transfer, and virtual account references may be linked to an account to match status or receipt questions.

Send a request through the private account-help form and state that you want access to your personal data. We may check account ownership before responding, as set out in the Privacy Policy.

You can request a correction or deletion through support. We assess the request against account security, unresolved payment records, dispute needs, and any retention duty described in the Privacy Policy.

Cookies may support sign-in sessions and account-state checks on your mobile browser. Your browser settings can control them, while the Privacy Policy explains possible effects on access and stored preferences.

Use the help form connected to the sign-in area and share the smallest amount of detail needed. For a wallet query, provide a receipt reference rather than a password or wallet PIN.