Reference

slot45 Privacy Policy For Your Account

Our Privacy Policy explains what slot45 collects, why we use it and how you can ask about your records before opening an account.

Account dataPayment referencesCookie choicesYour requests
slot45 slot45 Privacy Policy For Your Account
REQUEST HELP

Where To Ask About Your Data

A clear contact route helps you act on this Privacy Policy without searching through unrelated pages.

Account data request Open the support path from your account and state whether you want access, correction or deletion of personal data. Include your registered phone detail so we can check the right record.
Payment record question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account references, attach the receipt detail available to you. We use that reference to trace the related account activity.
Access concern If phone verification or sign-in appears unusual, contact support through your account path and describe the device and time involved. We may ask for account details before discussing protected records.
HANDLING DETAILS

Six Ways We Handle Personal Data

We keep this Privacy Policy practical by tying each data use to an account task you can recognise.

Account creation

When you open an account, we use submitted contact details and phone verification status to create and protect the account record. We do not treat an unverified request as proof of account ownership.

Payment matching

DANA, OVO, GoPay and QRIS references can appear alongside account activity when you check a receipt or wallet status. Bank transfer and virtual account references serve the same matching purpose.

Cookie controls

Cookies and similar browser storage can remember sign-in preferences, support page choices and technical settings. You can manage available browser controls, though some account functions may then need another sign-in.

Mobile access

When you use a mobile browser, we may record device and connection details needed to deliver pages, protect the session and investigate an access problem. We do not require a separate mobile application.

Security checks

We review sign-in, phone verification and unusual account activity to help prevent unauthorised access. If a check affects your request, support may ask for details that confirm you control the account.

Retention requests

We retain records for the period needed for the stated account, payment or support purpose, subject to local requirements. Where local law permits, contact us to ask about deletion or a retention reason.

Privacy Policy Questions Before Account Access

These Privacy Policy answers address the searches we hear most often before account creation or a data request. They explain the records linked to your account, how payment references are used and the steps available when you want clarification. Account access and any eligibility matter where local law permits.

The slot45 Privacy Policy covers account details, phone verification, sign-in records, cookie activity, payment references and support messages connected with your account. It also explains your available data requests.

We may collect contact details supplied during account creation, verification status, technical browser or device details, payment references and messages you send through support. The exact record depends on your activity.

Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account may be linked to your account so we can match receipts and investigate status questions. We use them for that operational purpose.

Use the account support path and ask for a data access request. Include your registered phone detail or another account identifier, then complete any ownership check needed before records are discussed.

Yes, where local law permits. Contact support with the inaccurate detail, the corrected version and your account identifier. We may request phone verification or another account check before changing protected records.

We keep records for the period needed for account security, payment matching, support handling and applicable local requirements. You can ask support why a particular record remains stored, where local law permits.

Send a cookie or mobile browser question through the account support path, describing the device and browser involved. We can explain the relevant technical record and available controls, where local law permits.