Reference

Privacy Policy Built Around Your Account

pertaslot keeps your account data, wallet records and device signals tied to clear account steps, from joining to checking Speed Baccarat, Garuda Gems or Aviator where local law…

DANA recordsOVO receiptsGoPay checksQRIS logs
pertaslot Privacy Policy Built Around Your Account
CONTACT ROUTES

Three Ways To Ask About Data

Privacy questions should not get lost in a normal lobby chat. We separate account data requests from game questions, so you can ask about correction, deletion…

Live chat window Use the chat bubble inside your account for quick privacy routing between 09:00 and…
Email privacy desk Send data requests to the privacy contact shown in your account menu.
Account menu form Open Profile, choose Help, then select Privacy Request when you want a copy, correction…
ACCOUNT CONTROLS

Six Controls Behind This Policy

We write this policy around real account handling, not vague promises. Your data moves through sign-in, wallet checks, cookie settings, support tickets and retention rules, and each step…

Data minimisation

We ask for account details that support login, wallet matching and support replies.

Cookie choices

Cookies help keep your session active, remember language settings and spot repeated failed logins.

Payment records

DANA, OVO, GoPay and QRIS references are kept with your wallet history so we can match deposits and withdrawal checks.

Device security

We record device and IP signals when you sign in, especially after password changes or unusual location shifts.

Retention timing

Some account and payment records must stay longer because payment partners, dispute handling or local rules require them.

Change requests

You can ask us to correct account data, check stored records or remove details that are no longer needed.

Your Privacy Policy Questions Answered

These answers focus on how your data is collected, used and handled when you open an account, sign in, use local payments or contact support. If your question involves a specific receipt, device or account change, include the date and channel so we can answer without exposing more data than needed.

We collect the details needed to create and secure your account, such as phone number, email, login signals and wallet references. We use them for access, payment matching, support replies and security checks.

We keep payment references so deposits and withdrawals can be matched to your wallet history. These records help us trace failed payments, confirm account ownership and answer disputes with less back-and-forth.

Yes. Open Profile, choose Help, then select Privacy Request. We may verify your registered phone number or email before sending account records, because we need to protect the data from other people.

Cookies keep your session active, remember language choices and help detect repeated failed logins. If you clear cookies on Chrome or Safari, you may need to sign in again and repeat account checks.

Only the support staff and account team handling your request should access those messages. We route privacy requests separately when possible, especially when you include payment receipts, account screenshots or identity checks.

You can request a correction through the account menu. We may ask for a sign-in check and recent payment context, such as a QRIS or GoPay reference, before changing contact details.

Retention depends on the type of record. Payment, dispute and security logs may stay longer where required by partners or local rules, while data without a valid purpose is removed, anonymised or restricted.