Reference

slot25 Privacy Policy for Your Account

Clear control over your account details, wallet references, and device choices begins with the slot25 Privacy Policy.

Account clarityWallet recordsPhone verification
slot25 slot25 Privacy Policy for Your Account
SUPPORT ROUTES

Privacy Help Beside Login and Wallets

A direct support path helps when a privacy question appears during login, phone verification, or a wallet status check. Use the support link beside the account area and include the relevant receipt reference without sending your password. For a request from Medan or another Indonesian city, we can explain the record involved, the reason for its use, and the next account step.

Team online

ACCOUNT QUESTIONS

Ask through the account support path when a phone check, sign-in record, or device entry looks unfamiliar. We will request enough detail to locate the account without asking for your password.

WALLET RECORDS

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account questions, include the receipt reference and wallet name. We use those details to trace the relevant payment record.

PRIVACY REQUESTS

Ask us to access, correct, or explain personal details through the same support route. We may first confirm your phone number so a request is linked to the right account.

DATA PRACTICE

Phone, Cookies, and Account Data Choices

Our privacy process follows the account actions you can recognise: phone verification, sign-in, payment matching, support contact, and a request to change your details.

DATA COLLECTION

We gather details needed for account access, phone verification, payment matching, support replies, and security checks. We avoid asking for unrelated personal details when a request can be handled without them.

COOKIE USE

Cookies and similar browser records can keep a session active, remember access choices, and help identify unusual sign-in behaviour. You can clear browser data, though this may require phone verification again.

ACCOUNT SECURITY

Phone verification connects account access to the number you provide. Never send a password or one-time code in support messages; we use account details and receipt references instead.

RETENTION PERIOD

We keep account, payment, and support records for operational, dispute, or legal needs. When a record is no longer needed, we remove it or make it non-identifying under our schedule.

CHANGES REQUEST

You may ask us to correct inaccurate account details or explain how a record is used. Include your registered phone number and the specific field you want checked.

CONTACT ROUTE

The support link connected to your account is the practical route for privacy questions. We confirm account ownership before discussing personal records or completing a change request.

Privacy Policy Questions for Indonesia

These Privacy Policy answers address the searches we hear most often before account access. You can use the support path for a personal request, while eligibility and access depends on local law. Keep your phone and receipt details ready so we can locate the correct record.

It covers account details, phone verification, device and cookie records, support messages, payment references, retention, access requests, corrections, and deletion options where local law permits.

Yes. We may process DANA and QRIS references, along with OVO, GoPay, bank transfer, or virtual account details, to match a payment or withdrawal request.

Phone verification helps connect access to the correct account and supports security checks. We may use the result to investigate unusual sign-ins without requesting your password.

Use the support link beside your account area and ask for an access request. Include your registered phone number, then complete any ownership check we ask for.

You can ask us to correct an inaccurate name, phone number, or account field. Tell us exactly what should change; we confirm ownership before updating the record.

We retain payment references only for operational, dispute, or legal needs. Once a record is no longer needed, we remove it or make it non-identifying under our internal schedule.

Contact support through the account-linked route and describe the browser or phone involved. We can explain session cookies, access logs, and the steps available for your request.