Reference

keitogel Privacy Policy for Your Account

Our Privacy Policy explains how we handle the details connected with your keitogel account, including phone verification, mobile access and wallet records from DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesContact steps
keitogel keitogel Privacy Policy for Your Account
HELP PATH

Privacy Help Through Your Account Path

A clear contact route matters when you want to ask what we store or why a record appears. After login, open the account support panel and include the phone number linked to your account, the relevant payment reference and the action you want us to take. This gives our team enough context to check your request without asking you to send sensitive wallet credentials.

Team online

Account data request

Use the logged-in support panel to ask which account details we hold. Include your verified phone number so we can confirm the request belongs to you.

Wallet record check

For DANA, OVO, GoPay or QRIS questions, attach the payment receipt reference rather than a wallet PIN. We use that reference to trace status safely.

Access correction

If your phone or account detail needs changing, tell us through support after login. We may request a clear verification step before applying the update.

DATA PRACTICES

Cookies, Security And Retention At keitogel

We keep this policy practical by connecting each data practice to an account action you can recognise.

Account security

Phone verification helps us confirm account access before sensitive changes. Keep your login details private, and contact support through the signed-in account path if access behaves unexpectedly.

Mobile device data

When you open the lobby in a mobile browser, we may process device and session signals needed for login continuity, fraud checks and a usable account path.

Cookie controls

Cookies can help remember session choices and security settings. You can review cookie controls in your browser, though changing them may require another login.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us reconcile payment status. We do not need your wallet PIN to check a receipt.

Retention approach

We retain account, security and payment records for the period needed for support, fraud prevention and operational duties, then remove or restrict them when no longer needed.

Policy requests

To request access, correction or a clarification, contact us through the account support panel with your verified phone number and a precise description of the requested change.

Privacy Policy Answers For Indonesia Accounts

These Privacy Policy answers address the account, device and wallet questions you may have before opening access. We keep the process tied to real actions, such as phone verification, a QRIS receipt check or a request made through your signed-in support panel.

It covers account details, phone verification, login and device signals, cookies, payment references, support requests, retention and the steps for asking about or correcting your data.

No. We use transaction references, receipt details and payment status for checks. You should not send a DANA, OVO, GoPay or QRIS PIN through support.

Phone verification helps us confirm that an account change or access request comes from you. It also gives support a clear account reference when a login or wallet status stalls.

After login, open the account support panel and request an account data check. Include your verified phone number and explain the records or categories you want us to address.

Yes, you can ask us to correct an inaccurate account detail through the signed-in support path. We may complete a verification step before changing phone or account records.

Mobile browser cookies may preserve session and security choices. You can adjust them in your browser, but clearing cookies can sign you out and require phone verification again.

Yes. Data access and account eligibility depends on local law. Where local law permits, contact us through the account support panel for the request path that applies.