Reference

pohonemas33 Privacy Policy for Indonesia

At pohonemas33, our Privacy Policy explains how we handle your account details, wallet records, device signals and cookie choices when you use the lobby.

Account recordsWallet activityCookie choicesLocal-law access
pohonemas33 pohonemas33 Privacy Policy for Indonesia
CONTACT ROUTES

Privacy Policy Help Beside Account Support

A clear contact path helps when you need to ask about a Privacy Policy record, cookie choice or wallet reference.

Policy questions Send your Privacy Policy question through our support chat with the account phone number or email attached. We use that detail to locate the correct record and reply without exposing another account.
Account access If phone verification blocks access, mention the device and browser used for login. Our support route can explain which account record is involved and what detail may need correction.
Wallet records For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account query, include the transaction reference only. Do not send a wallet password, PIN or full authentication code.
CONTROL AND SECURITY

Inside pohonemas33 Data Handling

We keep this policy practical by linking each data purpose to a visible account action. Your login, wallet and device records support access checks, while cookie settings and contact requests give you…

Account details

We use your phone or email, verification result and account activity to connect you with the correct profile. This helps prevent one person’s wallet status or support case appearing under another account.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a receipt with an account action. We do not need your wallet PIN to investigate a status question.

Cookies

Cookies and similar browser signals can keep your session working, remember selected settings and help identify repeated login problems. You can ask support how a cookie choice affects your account access.

Device security

We may use device type, browser version, login time and related signals to flag unusual account access. If your mobile path changes unexpectedly, contact support before sharing any verification code.

Retention periods

We retain account, payment and support records only for as long as needed for the stated purpose, account checks or a legal request. Ask support which category applies to your specific record.

Change requests

You can request a correction, ask about stored records or question a data purpose through the listed support route. Include your account contact detail so we can verify the request.

Privacy Policy Questions About Your Account

These Privacy Policy answers address the account and wallet questions you may have before using pohonemas33. They cover access records, cookies, payment references, device checks and requests for changes. If your case involves a specific transaction or login, use the account support route with only the details needed to identify your record.

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

Phone verification connects access to the correct account and helps us investigate login issues. We may retain the verification result and related account details for security and support purposes.

Yes. A QRIS reference may be used to match a payment receipt with your account and answer a status request. We do not ask for your QRIS wallet PIN or authentication code.

Cookies can keep your session active, remember browser preferences and help identify repeated access problems. You can contact support to ask about a cookie choice or its effect on your account.

Where local law permits, you can ask about records connected to your account or request a correction. Send the request through support with your verified phone or email detail.

Retention depends on the record’s purpose, account checks and legal needs. For a DANA, OVO, GoPay, QRIS or bank reference, support can explain which category applies.

The policy is available for you to read, while account access and eligibility depends on local law. Where local law permits, support can explain a region-specific data request.