Reference

kepo66 Privacy Policy for Your Indonesian Account

Our Privacy Policy explains how we collect, use and protect the account details connected with DANA, OVO, GoPay and QRIS activity.

Clear data purposesWallet activity contextDirect request path
kepo66 kepo66 Privacy Policy for Your Indonesian Account
PRIVACY HELP DESK

Get Privacy Policy Help Beside Account Support

A clear support path matters when you need a copy of your data or a correction to account details. Tell us which account step is involved, such as phone verification, DANA status or a QRIS receipt, so we can route the request accurately. We may ask for account identifiers before discussing private records, and we will use the details you provide only to handle the Privacy Policy request.

Team online

Data access request

Ask us to identify the personal data linked to your kepo66 account. Include your registered phone detail and the account step involved so we can locate the correct record.

Correction request

If your phone, wallet status or profile detail is inaccurate, contact our support path with the changed value. We may verify your account before applying a correction.

Payment record question

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account record, provide the receipt reference and date. We use those details to check the relevant privacy record.

DATA CONTROL PATH

What kepo66 Does With Your Account Data

We keep the Privacy Policy practical by connecting each data use to an account action you can recognise.

Account details

We collect details you submit during account opening and phone verification. These details let us identify your account, respond to requests and keep account records separated from another person’s data.

Wallet references

When you use DANA, OVO, GoPay or QRIS, we record the payment reference and status needed to match the account action. We do not need your wallet password for that check.

Device signals

Your browser or phone may send connection, session and device signals when you access the account. We use them to investigate unusual sign-ins and protect the account path.

Cookies on mobile

Cookies can keep a login session and remember technical choices on the mobile path. You can manage browser cookie settings, although changing them may affect account access or session continuity.

Retention decisions

We retain personal and payment records for the period needed for account operation, security checks or legal duties. When that purpose ends, we remove or de-identify the applicable record.

Security requests

If you suspect account access is not yours, contact us with the affected phone detail and last known account step. We can review access signals and apply verification before discussing records.

Privacy Policy Answers For Your Account

These Privacy Policy answers cover the searches we hear most often before an account is opened or a wallet is connected. We explain what data is collected, how access checks work and how you can contact us about a correction or deletion. If a request involves a payment record, keep the receipt reference ready so we can identify the right account action.

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

We use your phone detail to create and identify the account, complete the required verification step and respond to account requests. We may verify ownership before sharing private account records.

Yes. The Privacy Policy covers references and status linked to DANA, OVO, GoPay and QRIS, plus bank transfer and virtual account records needed to match an account payment action.

Where local law permits, you can request the personal data linked to your account. Send your registered phone detail and request purpose through our support path so we can verify and respond.

Contact us with the inaccurate field, such as a phone detail or wallet status, and explain the correction. We may request account verification before changing the stored record.

We keep data while it serves account operation, security checks or legal duties. After the relevant purpose ends, we remove or de-identify records unless another obligation requires continued storage.

Where local law permits, you can ask us to delete applicable personal data. Some payment or security records may remain when a legal, dispute or account-protection need requires them.