Reference

pedia4d Privacy Policy for Your Account

The pedia4d Privacy Policy explains what we collect when you open an account, verify your phone, access casino rooms or use DANA and QRIS.

Account dataWallet checksCookie choicesContact route

Explore Our Lobby Read FAQ

How Privacy Policy Covers Wallet Activity

pedia4d Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers details you provide during account creation, including your phone number, login details and verification responses. We also record transaction references needed to match a DANA, OVO, GoPay, QRIS, virtual account or bank transfer request with the correct account. Payment status may be

1
shared with the relevant payment rail so we can identify a receipt, resolve a pending cashier status and protect the account from misuse. Device details, browser signals and security events help us recognise unusual login attempts, while cookie data helps keep your selected session active. We
2
use this material for account access, payment processing, security checks, service communication and legal duties where local law permits. The policy does not change the terms set by your bank or wallet provider. Before opening an account, read this page and check whether access depends on
3
local law.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT YOUR WAY

Three Routes For Privacy Questions

A clear contact route helps you ask about the Privacy Policy without explaining your whole account journey.

Account privacy request Use the account help route to ask what personal details are held, why they are used or how your phone verification record connects to account access where local law permits.

Wallet data question For DANA, OVO, GoPay or QRIS queries, provide the payment reference rather than a wallet password. We can then check the receipt trail without asking you to expose private wallet credentials.

Cookie or device query If a browser session behaves differently on mobile and desktop, contact us through the policy support route with your device path. We can explain cookie use and security checks tied to that session.

DATA HANDLING MAP

Six Privacy Checks Around Your Account

We keep the Privacy Policy practical by linking each data category to a reason and an account action.

Account details

We use the phone number and account details you submit to create your login path, confirm the account step and send service messages connected to security or policy changes.

Payment references

A DANA, OVO, GoPay, QRIS, virtual account or bank transfer reference helps us match a cashier event to your account. We do not need your wallet password for that check.

Device signals

Browser type, device path and security events can help us identify an unusual login. On mobile, these signals may be used when you move from login to the lobby.

Cookie choices

Cookies can keep a session active, remember selected settings and support security checks. You can manage browser controls, although changing them may affect account access or saved preferences.

Retention periods

We retain account, payment and security records only for the period needed for the stated purpose, dispute handling, fraud checks or legal duties where local law permits.

Change requests

Ask us to correct account details or explain their use through the privacy contact route. Include your account identifier, but never send a password, wallet PIN or full payment secret.

Privacy Policy Answers Before Account Access

These Privacy Policy answers focus on the questions you may search before opening an account or checking a wallet status. We keep the wording tied to real account steps, including phone verification, cookies, payment references and device access. If your situation depends on local law, the applicable rule takes priority over a general statement here.

It covers account details, phone verification, device signals, cookies, payment references and security records used when you access the account, browse casino or sports areas, or contact us.

We use your phone number to create and protect the account path, complete the required verification step and help distinguish your account from another person’s login where local law permits.

Yes. The policy covers references and status details for DANA, OVO, GoPay, QRIS, virtual account and bank transfer activity. These records help match payment events without requesting wallet passwords.

You can send a correction or access request through the privacy contact route. Include your account identifier and the requested change, while keeping passwords, PINs and private wallet credentials out of the message.

Cookies may keep your session active, retain selected settings and support security checks. Browser controls can limit them, but changing cookie settings may interrupt login or remove saved preferences.

We retain data for the period needed for account operation, payment matching, security review, dispute handling or legal duties. The applicable period can depend on the record type and local law.

Use the privacy support route linked near account help and the cashier path. Describe the request, such as a phone record, QRIS reference or cookie concern, without sending secret credentials.

pedia4d Privacy Policy for Your Account

Three Routes For Privacy Questions

Six Privacy Checks Around Your Account

Account details

Payment references

Device signals

Cookie choices

Retention periods

Change requests

Privacy Policy Answers Before Account Access

01 What does the pedia4d Privacy Policy cover?

02 Why does pedia4d need my phone number?

03 Does the Privacy Policy include DANA and QRIS data?

04 Can I ask pedia4d to change my account data?

05 How does the Privacy Policy handle cookies?

06 How long does pedia4d retain personal data?

07 Where can I ask about a Privacy Policy request?

Related Pages