Reference

lokethoki Privacy Policy for Your Account

lokethoki Privacy Policy explains how we handle your account details, phone verification, device activity and wallet records when you use DANA, OVO, GoPay or QRIS.

Clear data purposesWallet record contextRequest support path
lokethoki lokethoki Privacy Policy for Your Account
CONTACT DATA HELP

Where to Ask About Your Privacy Policy

A clear contact route helps when you want to understand an account record, wallet status or device detail held under our Privacy Policy.

Account request Ask us to access, correct or clarify details linked to your lokethoki account. Include your verified phone number and we can compare the request with the account record.
Wallet status For DANA, OVO, GoPay or QRIS records, send the relevant payment reference rather than a wallet password. We use the reference to check status without requesting unnecessary credentials.
Policy question Contact us through the account help route beside the cashier path when you need a Privacy Policy explanation. We can clarify cookies, retention, security checks or a change request.
DATA HANDLING PATH

What We Do With Your Account Details

Privacy choices are easier when each data step has a practical reason. We connect account, device and payment records only when needed to provide access, check a status or answer your request.

Account details

We may handle your phone number, verification result and account identifiers to create access, confirm that a request comes from you and keep account records matched correctly.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references are used to trace payment status. We do not need your wallet password to investigate a receipt.

Cookies and sessions

Cookies can keep your sign-in state, language choice and security session consistent. You can manage browser cookies, though removing them may require another account sign-in.

Device security

We may record browser, device and connection signals to identify unusual access and protect your account. These checks can appear before the lobby opens on a new device.

Retention periods

We retain account, support and transaction records only for the period needed for the stated purpose, account administration, dispute handling or a legal obligation that applies.

Changes and requests

You can ask us to correct eligible details, explain processing or assess removal. We may verify your identity first, then respond according to local law and record needs.

Privacy Policy Questions About lokethoki

These Privacy Policy answers cover the account steps, local wallet records and browser behaviour you are most likely to ask about before opening an account. If your situation is not listed, use the account help route and give us only the details needed to locate your request.

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

Phone verification helps us confirm account ownership before access or a privacy request is completed. It also reduces the chance that another person can change details or request records for your account.

Yes. The Privacy Policy explains how we use QRIS, DANA, OVO and GoPay references to match payment status, investigate receipts and answer account questions without asking for your wallet password.

You can contact us through the account help route and ask for access, correction or an explanation. We may verify your phone number first, and the outcome depends on local law.

On a mobile browser, cookies can retain your session, language choice and security state between the login page and lobby. Clearing them may sign you out and trigger phone verification again.

We keep records for the time needed for account administration, support, payment status checks, dispute handling or legal duties. A removal request is assessed against those purposes and local law.

Use the support path beside the cashier area in your account and describe the request, such as a wallet reference, cookie question or correction. Share no password or unnecessary payment credential.