Reference

Open spyslot Privacy Policy Before Account Access

spyslot Privacy Policy explains what we collect when you create an account, sign in from mobile or desktop, and use DANA, OVO, GoPay or QRIS.

Clear data purposesWallet records explainedAccount request pathCookie choices

Explore Our Lobby Read FAQ

Browse Privacy Rules For Your Account

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

Our Privacy Policy applies to the account journey from phone verification through lobby access and wallet status checks. We may process contact details, verification results, login records, device signals, approximate location, support messages and transaction references so we can secure your account and match payment activity.

1
DANA, OVO, GoPay, QRIS, bank transfer and virtual account references are used to identify a payment request, reconcile its status and investigate a mismatch; we do not treat a wallet name as permission to collect unrelated content. Cookie and device settings can affect sign-in continuity. Access
2
and eligibility depends on local law, and this policy does not change those local requirements. If you access from Yogyakarta or another Indonesian location, the same request route in your account remains available where local law permits.

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

REQUEST HELP

Check Privacy Questions Through Account Help

A privacy question should not require you to repeat your account story. Start from the account help route, identify the subject of your request, and include…

HOW WE HANDLE DATA

Explore Data Handling Behind Each Login

We keep this Privacy Policy practical by linking each data category to an account action. Login and device records help us recognise unusual access; payment references help us reconcile wallet activity; support…

Account details

During account creation, we use your contact details and phone verification result to establish access. You can ask us to correct an inaccurate name, phone detail or account record through the account help route.

Device signals

When you sign in on a mobile browser or desktop, we may record device and session signals. These help us compare familiar access with an unexpected login without reading unrelated files on your device.

Cookies

Cookies can keep a session connected and remember selected settings. Browser controls let you clear or restrict them, although changing those settings may require another login before the lobby or account page opens.

Wallet records

For DANA, OVO, GoPay and QRIS, we use payment references, status results and timestamps to match an account action. We do not need your wallet password to investigate a receipt or status question.

Retention

We keep account, security and transaction records for the period needed for their stated purpose, account protection, dispute handling or legal duties. A deletion request is assessed against those duties before we respond.

Your request

You can ask for access, correction, deletion, restriction or an explanation of processing where local law permits. Send the request through account help and complete reasonable verification so we protect your records.

Browse Answers About Privacy Policy

These Privacy Policy answers cover the searches we hear most often before account access. They explain the practical path for Indonesian account holders, including phone verification, mobile sessions, cookies, wallet references and requests for changes. If your situation is not listed, use account help and describe the record or action you want us to check.

It covers data used during account creation, phone verification, login, device sessions, cookies, support requests and payment-status checks. It also explains your available requests and our retention approach where local law permits.

Phone verification helps connect an account to the contact detail supplied at access and helps us investigate unusual sign-ins. We use the result for account protection and do not ask you to provide a password.

Yes. We may use DANA and QRIS references, timestamps and status results to match an account payment action. A wallet password is not required for us to check a receipt or status mismatch.

A mobile session may create login, device, browser and security records, along with cookie data if enabled. These signals help keep account access consistent and identify activity that needs an account check.

Open the account help route and state whether you want access to records or correction of a specific detail. We may verify your account first, then assess the request where local law permits.

You can submit a deletion request through account help. We assess it against security, dispute-handling and legal record duties, explain any data that must remain, and remove eligible records where local law permits.

We retain payment references, login records and support context only for their stated purpose, account protection, dispute handling or legal duties. The applicable period depends on the record and local law.

Open spyslot Privacy Policy Before Account Access

Check Privacy Questions Through Account Help

Explore Data Handling Behind Each Login

Account details

Device signals

Cookies

Wallet records

Retention

Your request

Browse Answers About Privacy Policy

01 What does the spyslot Privacy Policy cover?

02 Why does spyslot need phone verification?

03 Does the Privacy Policy cover DANA and QRIS records?

04 What data is collected when I use a mobile device?

05 How can I request a copy or correction of my data?

06 Can I ask spyslot to delete my account data?

07 How long does spyslot keep payment and login records?

Related Pages