Reference

Privacy Policy For Your pelangi4d Account

pelangi4d Privacy Policy explains what we collect when you open an account, use the mobile lobby, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet detailsDevice securityPolicy requests
pelangi4d Privacy Policy For Your pelangi4d Account
CONTACT YOUR WAY

Privacy Help For Login And Wallet Questions

A clear contact path matters when your account record or wallet reference needs attention. Use the support route connected to your account and include the phone number or payment reference you want us to check, without sending a password or full wallet credential. We can then narrow the request to access, correction, deletion, retention or a payment-status record. If you are in Medan or elsewhere in Indonesia, the same privacy request path applies where local law permits.

Team online

Account access

If phone verification blocks your account, contact us through the account support path and describe the device, sign-in time and message shown. We use those details to locate the relevant security event without asking you to disclose your password.

Wallet references

For a DANA, OVO, GoPay or QRIS privacy question, send the transaction reference and date rather than a wallet PIN. We compare the reference with the account record and explain what payment data remains stored.

Policy requests

You can contact us to ask for a copy, correction or removal request concerning your personal data. We may first confirm account ownership through the phone verification step before changing or disclosing account-linked records.

DATA CONTROL

Six Privacy Checks Inside Your Account

We keep this Privacy Policy practical by tying each privacy decision to an account action you can recognise.

Collected details

We may receive your contact details, phone verification result, account preferences and support messages when you create or use an account. We collect only what helps provide account access, answer a request or connect a payment reference to the correct record.

Cookie choices

Cookies and similar browser signals can keep a session active, remember selected settings and help us detect repeated security failures. Your browser can manage these files, although changing the setting may affect sign-in continuity or parts of the mobile lobby.

Account security

Phone verification, session checks and device signals help us distinguish your normal access from an unusual sign-in. We do not ask for your DANA, OVO, GoPay or QRIS password, and you should never place one in a support message.

Payment records

A payment reference, amount status and selected rail may be kept to match account activity with DANA, QRIS, bank transfer or virtual account records. These details help us investigate a receipt question without storing your wallet login credential.

Retention requests

We retain account and support records for as long as needed to provide the requested service, resolve disputes, check payment history or meet applicable duties. You can ask why a particular record is retained and request action where local law permits.

Data changes

If your phone number or another account detail is inaccurate, contact us with the account identifier and the correction needed. After confirming ownership, we can assess the change and tell you whether any connected security or payment record must remain unchanged.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the searches we hear most often from people considering an account. They explain what happens during phone verification, how wallet references are handled, how device access affects cookies and security records, and how to contact us about a correction or removal request. If your situation is specific, use the account support path and include enough detail for us to locate the record safely.

The pelangi4d Privacy Policy covers account details, phone verification, device and session signals, cookies, support messages and payment references. It explains why we use those records, how long they may remain available and how you can ask about access, correction or removal where local law permits.

Yes. Our Privacy Policy covers the payment references and status details needed to connect DANA or QRIS activity with your account. We may also handle OVO, GoPay, bank transfer and virtual account references, but we do not ask for your wallet password or PIN.

Phone verification helps us confirm that the account belongs to you before access or a privacy request is processed. The result can also support security checks when a sign-in comes from a new device. We use the verification record for account protection and related support.

The Privacy Policy allows us to explain cookies used for session continuity, settings and security checks. On a mobile browser, you can manage cookies through browser controls. Turning them off may require more sign-ins or affect selected account settings when you return to the lobby.

Yes. Contact us through the account support path with the detail you believe is wrong and the requested correction. We may confirm ownership through your phone verification step, then assess the change against connected security, account and payment records.

We keep account, support and payment-reference records for the period needed to provide account service, resolve payment or access questions, protect security and meet applicable duties. The exact period can depend on the record and local requirements, and you can ask us to explain its retention.

Send a removal request through the account support path and identify the account record involved. We may confirm ownership before acting. Some records can need continued retention for security, payment disputes or applicable duties, and we will explain that reason if it applies.