Reference

perkasajitu Privacy Policy For You

Your perkasajitu Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, and use DANA, OVO, GoPay or QRIS.

Clear data purposesCookie choicesAccount access rightsLocal law applies
perkasajitu perkasajitu Privacy Policy For You
HELP PATHS

Get Privacy Help From Your Account

A clear support route helps you ask about the Privacy Policy without sending personal details through an unrelated channel. Sign in first where possible, then use the account support path and include the email or phone attached to your account, the request you are making and any relevant wallet reference. We may ask for an account step to confirm that we are speaking with you. Do not send a password, full wallet PIN or one-time access code.

Team online

Policy questions

Ask how we use account, device or cookie records through the support path inside your account. We will use the account contact details you provide to locate the right record and explain the relevant Privacy Policy section.

Wallet record checks

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, share the transaction reference rather than your wallet PIN. We can compare the payment record with your account status while limiting the personal details included in the request.

Access requests

For a copy, correction or eligible removal request, tell us which account detail or device record you mean. We may confirm your identity through the existing account contact before changing or releasing any personal data.

DATA PRACTICES

What We Do With Your Account Data

We keep the Privacy Policy practical by connecting each data type to a clear account purpose. Login records help us investigate access problems, device signals help identify unusual sessions, and wallet references…

Account creation

When you open an account, we collect the contact and verification details needed to create your profile and manage access. Clear phone verification can connect the right person to the right account before you reach the casino or sportsbook areas.

Device sessions

A phone, tablet or desktop session may create technical records such as browser type, login time and security signals. We use them to investigate unfamiliar access, including a session that changes from mobile browsing to a desktop login.

Cookie controls

Cookies can keep your session active and remember selected settings while you move between pages. You can manage cookie controls in your browser; disabling some cookies may require another login or affect saved page preferences.

Payment references

We receive payment references rather than your wallet PIN when you use DANA, OVO, GoPay or QRIS. Bank transfer and virtual account records can also be matched to your account so a receipt query reaches the correct status record.

Retention period

We retain personal data only while it serves account access, security, service handling or legal duties. When a record is no longer needed for those purposes, we remove it, anonymise it or restrict access according to the applicable retention process.

Changes and contact

If your phone, email or another account detail changes, contact us through the account support path before opening a second profile. We can explain the Privacy Policy, verify the request and record the change against the existing account.

Privacy Policy Answers For perkasajitu

These Privacy Policy answers focus on the account questions you may search before opening access from Indonesia. We explain the practical path for data requests, cookie choices, device records and wallet references, while keeping eligibility wording tied to local law. If your case involves a specific account, use the support route after signing in so we can check the correct record.

The perkasajitu Privacy Policy covers account details, phone verification, login and device records, cookies, support requests and payment references. It explains how we use those details for access, security, service handling and legal duties when you use the site where local law permits.

We collect the contact and verification details you submit during account creation, then create technical records when you sign in. A phone or desktop may provide browser, session and security signals, while DANA, OVO, GoPay or QRIS activity creates a payment reference.

Sign in and use the account support path to request a copy of eligible personal data. State the account contact attached to your profile and the records you want. We may confirm your identity before releasing the response, and access depends on local law.

Yes, contact us through the existing account support path and identify the detail that needs correction, such as a phone number or email. We may ask for a verification step to protect your account, then record the approved change against your current profile.

The Privacy Policy covers cookies that help maintain a mobile session and remember selected page settings. You can control them through your browser settings. If you disable needed cookies, you may need to sign in again when moving from a phone to a desktop.

We do not ask you to send a wallet PIN through support. DANA and QRIS activity is handled through a payment reference used to match status with your account. For a receipt question, share the reference only and keep your PIN and access code private.

We keep records for as long as they serve account access, security, service handling or applicable legal duties. After that, we remove, anonymise or restrict them through our retention process. You can ask support about a specific record and its eligible request path.