Reference

Privacy Policy for peraktoto Account Data

Your peraktoto Privacy Policy explains what account, device and wallet details we use when you open an account, sign in and check DANA, OVO, GoPay or QRIS status.

Clear data purposesWallet record contextAccount access rightsIndonesia policy terms
peraktoto Privacy Policy for peraktoto Account Data
CONTACT PATHS

Where To Ask About Privacy Policy

A clear contact path matters when a Privacy Policy question affects your account or wallet record. Start with the support contact shown inside your signed-in account area and include the phone number or account detail we can use to locate your request. If a DANA, OVO, GoPay or QRIS reference is involved, share only the transaction reference requested by our team, not your wallet password or security code.

Team online

Account data request

Use the support contact displayed after sign-in to ask what account details we hold, why they are needed, or which record should be corrected. Include your registered phone number so we can match the request without requesting unrelated wallet credentials.

Wallet record question

For a DANA, OVO, GoPay or QRIS reference, send the relevant transaction identifier through the account support path. We use that reference to locate status records while keeping your wallet PIN, one-time code and full security details out of the request.

Access concern

If a sign-in or phone-verification step appears connected to a privacy concern, tell us which device path you used and when it occurred. Our team can separate an access record from a wallet record and explain the next request step.

DATA HANDLING

What Our Privacy Process Covers

We treat the Privacy Policy as an operating process rather than a page to overlook. Account creation, phone verification, sign-in, wallet checks and support contact each create different…

Account details

We use the details you enter when opening an account to create your profile, complete the phone-verification step and connect…

Device signals

When you move from a mobile sign-in to the lobby, technical signals such as device type, browser session and connection…

Cookies

Cookies can keep a session active, remember selected settings and help us understand whether a page opened correctly.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may create reference data such as status, amount, time and…

Retention period

We keep account, device, support and transaction references for the time required to provide the stated service, resolve a dispute…

Policy requests

You can ask us to access, correct or clarify personal data through the support contact shown in your account area.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account steps you are most likely to meet from Indonesia, including phone verification, mobile sign-in, wallet references and contact requests. We keep each answer tied to peraktoto records so you know what to prepare before asking for access, correction or removal where local law permits.

The peraktoto Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, support messages and payment references. It explains why we use each type of record, how retention works and how you can send a data request through the support contact inside your account.

Phone verification links the account request to a contact route you control and helps us handle access requests safely. It can also help separate your account from another device session. We use the verification step for account security and do not ask for your DANA or wallet PIN.

Yes. The Privacy Policy covers references created when DANA, OVO, GoPay or QRIS status is checked against your account. These may include a reference, time, status and account link. They do not require us to receive your wallet password or one-time security code.

A mobile or desktop sign-in may create technical records such as device type, browser session, connection timing and security signals. We use them to keep the account path working and identify unusual access. The Privacy Policy explains how these records are used and retained.

Use the support contact shown in your signed-in account area and state that you want a data correction. Include your registered phone number, the record you believe is wrong and the corrected detail. We may ask for an account confirmation step before changing personal data.

You can request removal or restriction through the account support path where local law permits. We first identify the account and check whether a record must remain for a transaction, dispute or legal duty. The Privacy Policy explains when a request may have a limited result.

Contact us through the support route displayed inside your account and describe the privacy concern in clear terms. Mention whether it involves account access, a cookie, a device session or a DANA, OVO, GoPay or QRIS reference so we can send it to the right handling path.