Reference

pedia4d Privacy Policy For Your Account

Our Privacy Policy explains how pedia4d handles your account details, wallet records and device activity when you use the site.

Clear data purposesWallet record controlsAccount access requestsCookie choices
Explore Our Lobby Read FAQ
pedia4d pedia4d Privacy Policy For Your Account
CONTACT PATHS

Ask About Privacy Through Support

A direct support path helps when you need a copy, correction or explanation of account data. Start from the signed-in account area and include the phone number linked to your account, the request you are making and any relevant payment reference. We use those details to find the correct record without asking you to send a full wallet password. If login is unavailable, use the contact route shown on the pedia4d site and expect an identity check before account details are discussed.

Team online

Data access request

Ask us for the personal data connected with your account. We may confirm your phone verification first, then provide the available account, login and transaction records through the contact path shown on our site.

Correction request

If your phone number or account detail is outdated, tell us what needs changing and why. We compare the request with your verified account record before applying a correction or explaining why a record must remain unchanged.

Wallet record help

For a DANA, OVO, GoPay or QRIS query, include the transaction reference and status shown in your account. We can check the matching record without requesting your wallet PIN or full banking credentials.

DATA PRACTICES

What We Do With Your Account Data

We apply this Privacy Policy to the working details behind account access, wallet status and site security.

Account details

We use your phone number and account identifiers to create your account, complete phone verification and match support requests. We do not need your wallet PIN or full bank password to check a pedia4d transaction reference.

Cookies and devices

Cookies can keep your session open, remember selected settings and help us detect unusual sign-in patterns. On a mobile browser, clearing site data may sign you out and require phone verification again before account access returns.

Security checks

We may compare login events, device signals and phone verification status when an account request looks unusual. This helps us avoid changing account data for the wrong person, especially when a wallet status or receipt is being queried.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account entry may retain its reference, status and time. These records help us match a cashier event, investigate a failed status and answer a receipt request.

Retention periods

We keep account and transaction records for the time needed to provide the requested service, resolve disputes, maintain security or meet a legal duty. When a record is no longer needed, we remove it or separate it from direct account identifiers.

Your requests

You can ask for access, correction or clarification through the support route shown in your account area. Include your verified phone number and request details; we may ask for another account check before sharing or changing personal data.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account questions we hear most often from people using Indonesian wallets and mobile browsers. We explain what we collect, why a phone check may appear, how to request a copy or correction, and what happens to payment records. If your situation is not covered, send the request through the account support path with enough detail for us to locate the correct record.

It covers data connected with account creation, phone verification, sign-in events, device activity, support requests and wallet transactions. It also explains cookies, security checks, retention and your options to request access or correction. Availability and eligibility depends on local law.

We use your phone number to create and identify the account, complete the phone verification step and match a privacy request to the right record. It also helps us investigate an unusual login without asking for your DANA, OVO or GoPay PIN.

Yes. The Privacy Policy covers transaction references, status and timing linked with QRIS, bank transfer, virtual account, DANA, OVO and GoPay activity. We use those records to check cashier status, match receipts and answer account queries.

Use the support route shown after you sign in, state that you want an account data copy, and include your verified phone number. We may ask you to confirm account details before sending records, so another person cannot obtain your account data.

Yes. Send the correction request through the account support path and identify the field that is wrong, such as a phone number or account detail. We compare your request with the verified record, then correct it or explain any legal reason to retain it.

Cookies can keep a mobile browser session active, remember settings and help detect unusual sign-in activity. If you clear cookies or site data, you may be signed out and asked to complete phone verification again before returning to the account area.

We retain account, security and transaction records for the time needed to provide the service, investigate disputes, protect account access or meet a legal duty. Once a record is no longer needed, we remove it or separate it from direct account identifiers.

Related Pages

pedia4d Indonesia Volleyball Betting About Us Lightning Roulette pedia4d Login