Reference

peraiktoto Privacy Policy for Indonesia

Our peraiktoto Privacy Policy explains what account, device and payment details we collect, why we use them, and how you can request changes.

Account clarityWallet detailCookie choicesAccess controls
peraiktoto peraiktoto Privacy Policy for Indonesia
CONTACT ROUTES

Privacy Help Through Your Account

A clear contact path helps you act on this Privacy Policy without sending sensitive details through an unverified channel. Sign in first where possible, then use the account support route to ask about stored data, a correction or a deletion request. For a wallet question, include the relevant receipt or status reference rather than a full password or security code. We use the same account context when checking a phone-verification issue, a device access concern or a cashier record.

Team online

Account privacy request

Open the account support path and state whether you want access, correction, deletion or a copy of personal data. We may ask you to confirm the account phone number before discussing records.

Wallet record question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account queries, attach the payment receipt reference only. We use that reference to locate the relevant record without asking for your wallet password.

Access and device concern

If a new phone, browser or login path creates a privacy concern, tell us the device type and approximate access time. Do not send your password; we will use account checks before discussing account details.

DATA PRACTICE

How We Handle Personal Data

Our handling approach is designed around practical account actions rather than unnecessary collection. We separate details used for login and phone verification from payment references used to reconcile DANA, OVO, GoPay, QRIS…

Account details

When you create an account, we use the details needed to identify your account and complete phone verification. Keeping your phone number current helps us distinguish an access request from an unauthorised attempt.

Device signals

Browser type, operating system, session time and related signals may be recorded to recognise unusual login behaviour. A shared device can create mixed sessions, so sign out after use and avoid saving credentials in a public browser.

Cookies and sessions

Cookies can keep a session active, remember selected preferences and help us understand whether a page is functioning. You can manage cookies through your browser, although blocking necessary cookies may interrupt account access.

Wallet references

We may retain a payment reference, amount status and time for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We do not need your wallet password to check a receipt or cashier status.

Security controls

Phone verification and account checks help protect access when a login comes from a new device or an unusual session. We do not ask you to disclose a password or one-time security code through a support message.

Retention and requests

We keep records only for the period needed for account support, security, payment reconciliation or legal duties. You can contact us to request access, correction or deletion; some records may need to remain where local law permits or requires it.

Privacy Policy Questions Answered

These Privacy Policy answers focus on the account and wallet questions you are most likely to ask before opening access. They explain the practical steps for Indonesia, from phone verification and device signals to payment references and requests for changes. If your situation is not covered, use the account support path and describe the specific record or access event you want us to check.

You can read the current peraiktoto Privacy Policy on this page before opening an account. It covers account details, phone verification, cookies, device signals, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

The policy covers details you submit for an account, contact and phone verification, plus device, browser, session, cookie and support data. Payment reconciliation may include a receipt reference, status, time and amount, but you should never send a wallet password or security code.

We use DANA or QRIS references to match a cashier request with its status and answer a receipt question. The same approach applies to OVO, GoPay, bank transfer and virtual account records. We do not need your wallet password to check a reference.

Yes. Use the account support route to request access to your stored details or ask for a correction. Include the account phone number or another account identifier, but do not include your password. We may verify ownership before releasing or changing records.

On a phone or tablet, cookies may support the login session, remember a preference and help identify a technical issue. You can adjust browser cookie settings, but blocking necessary cookies may interrupt the path from phone verification to the account area.

We keep payment, device and account records for the period needed for support, security, reconciliation or legal duties. The exact period can depend on the record and applicable rules. You may ask us to explain the retention basis for a particular account detail.

This policy is written for access connected with Indonesia, but account access and eligibility depends on local law. If you are in Jakarta, Yogyakarta or another location, check the rules that apply to you and contact support when a local restriction affects your request.