Reference

Open Your Privacy Policy View on pedro4d

The pedro4d Privacy Policy explains what we collect when you create an account, sign in, use a mobile browser, or check DANA and QRIS activity.

Account and phone detailsWallet activity contextCookie and device choicesRequest and contact paths
Explore Our Lobby Read FAQ
pedro4d Open Your Privacy Policy View on pedro4d
CONTACT ROUTES

Switch To A Clear Privacy Contact Path

A direct support route helps when you want to ask about a record, cookie, wallet reference, or account correction. Sign in first when possible so we can connect the request to the right account without asking you to send a password. If access is unavailable, use the contact route shown on our site and include only the details needed to locate your request.

Team online

Account help

Use the account help route for access, phone verification, or a request to correct your name, email, phone number, or other account details. We may ask for a verification step before changing records, so another person cannot alter your account through a simple message.

Wallet status

Choose the cashier support path when a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference appears incorrectly. Share the transaction reference and date, not your wallet password or one-time code, so we can check the matching record.

Policy requests

For a copy, correction, deletion question, or objection about personal data use, contact us through the privacy route listed with this policy. We may confirm account ownership, explain any legal or operational reason for keeping a record, and respond through your registered contact.

DATA HANDLING

Browse pedro4d Data Handling Choices

We keep the Privacy Policy practical by linking each data category to an account action you can recognise.

Account records

We use your submitted account details to create the login path, send account-related replies, and complete phone verification before access. Keep your sign-in details private and tell us through the account route if your phone number or email needs correction.

Payment references

A wallet or bank reference helps us match a cashier event to your account without needing your wallet password. For DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri, or BNI transfers, we use the status and reference needed for checking.

Cookies and devices

Cookies can keep a session connected and help us remember a language or access setting. Device and browser signals can help identify repeated sign-in failures. You can adjust cookie controls in your browser, although some account functions may then need another login.

Account protection

We use phone verification, session checks, and unusual-activity signals to reduce unauthorised account access. We will not ask you to disclose a password or one-time code in support messages, and we may pause a request while ownership is checked.

Retention periods

We keep records only for the period connected to the stated purpose, account support, security checks, dispute handling, or a legal duty. When a record is no longer needed, our process is to remove it or separate it from direct account identifiers.

Changes and requests

You can ask which personal data we hold, request a correction, ask about deletion, or question a stated use through the privacy contact path. Include your account email or phone only through the secure route, and we will explain the next verification step.

Check Privacy Policy Answers Before Opening

These Privacy Policy answers address the questions we expect from an Indonesian account holder before using the site. They cover account creation, local wallets, cookies, device access, corrections, and contact requests. If your situation is not listed, use the privacy contact route and describe the specific record or action you want us to check.

The pedro4d Privacy Policy covers account details, phone verification, login sessions, cookies, device signals, support messages, and payment references. It also explains why we use each category, how long records may remain, when sharing can occur, and how you can request access or correction.

No. When you use DANA or QRIS, we may handle a transaction reference, status, amount, and account match needed for cashier support. We do not ask for or need your wallet password. Never send a password or one-time code through a support message.

Phone verification connects the account to a contact route and helps us check ownership before account access or a record change. If your phone number is outdated, contact support through the account route. We may request another ownership check before editing the stored details.

Cookies can retain a sign-in session, language setting, or security marker, while browser controls let you remove or block them. Blocking cookies may require another login or affect a policy preference. The Privacy Policy explains their purposes, and your browser provides the control to change them.

Yes. Send a request through the privacy contact path to ask what account data we hold or to correct an error. Use the secure route and provide only the needed account identifier. We may verify ownership, then explain the action, timing, or reason a record must remain.

When you sign in from a phone or desktop, we may process browser type, device signals, IP region, and session times for access protection and fault checking. These details can help us investigate a failed login without collecting the content of unrelated apps on your device.

Use the privacy contact route shown with this Privacy Policy for questions about collection, cookies, retention, deletion, or sharing. For a DANA, OVO, GoPay, or QRIS record, use the cashier support route instead. Access to services depends on local law and where local law permits.

Related Pages

pedro4d Indonesia Account information Access guide GoPay Min Deposit pedro4d Casino