Reference

Privacy Policy For Your pedesslot Account

Our Privacy Policy explains how pedesslot handles the details connected with your account, mobile browser, cookies and payment status.

Account clarityCookie choicesWallet recordsPolicy contact
pedesslot Privacy Policy For Your pedesslot Account
CONTACT YOUR WAY

Privacy Questions Reach Our Support

A clear support path helps when your Privacy Policy question concerns an account record, cookie choice or wallet status.

Account data request Use the account support path to ask what personal details we hold, where they…
Wallet record check If a DANA, OVO, GoPay or QRIS status appears incorrectly, send the transaction reference…
Cookie assistance For cookie or mobile-browser questions, tell us the device path you used, such as…
DATA HANDLING

What The Policy Covers In Detail

The Privacy Policy is designed around the moments that create real account records: opening an account, completing phone verification, moving through the mobile lobby, checking a wallet status and contacting support.

Account details

We use the contact and account details you provide to create access, complete the stated phone verification step and connect your requests to the correct account. Please keep those details current so a data-access or correction request can be handled safely.

Mobile and device signals

When you use a mobile browser to move from login to the lobby, we may record device, browser, language and session signals. These help detect broken access and protect the account; they are not a request for your private device files.

Cookies

Cookies can preserve an essential login session, remember a consent choice and help us understand whether a page path loads correctly. You can manage available preference cookies in your browser, while disabling essential cookies may interrupt account access.

Payment references

Our records may show a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference and its status. We use those details to match cashier activity and support requests, while your wallet PIN and banking password should never be sent to us.

Security and retention

We protect account records through access controls and verification checks before discussing personal data. Retention depends on the reason for collection, an unresolved support matter and any legal duty; when the applicable period ends, eligible records are removed or anonymised.

Changes and contact

You can ask for a copy, correction, restriction or eligible deletion of your personal data through the support route attached to your account. We may confirm your identity before acting, and we will explain if local law prevents a requested change.

Privacy Policy Questions For Indonesia

These Privacy Policy answers cover the practical points you may check before opening a pedesslot account or asking us to change an existing record. We keep the examples close to the actual account path: phone verification, mobile browsing, cookie settings and wallet references for DANA, OVO, GoPay and QRIS. If your situation is different, contact support with the smallest useful detail.

It covers account and verification details, device and browser signals, cookies, support messages and payment references linked with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains use, retention, security, your requests and limits that depend on local law.

Phone verification connects account access to the contact detail you submitted and helps us respond to the correct person. We may use that record when you ask for a copy, correction or deletion, but support can request additional checks before releasing personal data.

No. Our policy concerns transaction references and status linked with your account, not your DANA, OVO, GoPay or QRIS password or PIN. Never place wallet credentials in a support message. Send only the account detail and transaction reference needed for a status check.

Yes. Use the account support route and ask for a copy of the personal data connected with your account. Include your registered contact detail, identify the records you mean and complete any identity check we request before we disclose account-specific data.

Send a correction or eligible deletion request through support, naming the exact account detail or record. We check the request, make the change where possible and explain any retention duty that requires us to keep a record. Account access depends on local law.

The policy describes essential cookies for session continuity and preference cookies for choices such as consent. Your browser can control available preferences. If essential cookies are blocked, the login-to-lobby path may not work correctly on mobile or desktop.

There is no single period for every record. We consider the purpose of collection, account security, an open support matter and applicable legal duties. After the relevant period ends, eligible data is removed or anonymised, while some records may need longer retention.