Reference

irama togel Privacy Policy

irama togel explains how we collect, use and protect the details connected with your account, including phone verification and DANA or QRIS activity.

Clear data purposesWallet record handlingAccess request pathCookie choices
irama togel irama togel Privacy Policy
REQUEST ROUTES

Where To Ask About Privacy

A privacy question should reach the same account support path you already use for login or wallet status, so you do not need to search through unrelated channels.

Account support Use the support route connected with your account when you need to ask how phone verification, login records or wallet references are used under our Privacy Policy.
Wallet query For a DANA, GoPay, QRIS or bank transfer record, identify the payment rail and date without sharing a password; this helps us check the correct account reference.
Data request Ask for access, correction or deletion through support, and we may verify account ownership before responding so another person cannot obtain your private account details.
DATA PRACTICES

What We Do With Your Details

We separate account, payment and device records by purpose rather than treating every visit as the same type of data.

Account details

We use your phone number and login details to create, verify and protect your account. Keep your password private, because support will not need it to assess a Privacy Policy request.

Payment references

DANA, OVO, GoPay and QRIS records can include a reference, amount status and time. We use those fields to match activity without asking you to reveal wallet credentials.

Cookies

Cookies and similar browser storage can preserve session state and security preferences. You can manage browser settings, though removing them may require another login or affect account access.

Device security

We may record device or browser signals linked to unusual access attempts. These checks help us protect the account path from login through the lobby without reading private content on your device.

Retention period

We retain records only for operational, security or legal needs described by the Privacy Policy. Payment matching records may remain after a session ends when reconciliation or a lawful request requires them.

Changing details

If your phone detail is wrong or you want to ask about stored data, contact account support with a clear request. We may confirm ownership before changing or disclosing anything.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the account and payment questions we expect you to ask before opening access. They cover the details we collect, how wallet references are handled, what cookies do, and how to contact us about a correction or removal request. If your situation is specific, use the support path rather than sending sensitive credentials in a message.

It covers account details, phone verification, login and device records, cookies, payment references, retention and requests to access or change personal data connected with your account.

We use your phone number for account creation, verification and access checks. It helps us identify the correct account when you ask about login, wallet status or a Privacy Policy request.

Yes. We may retain payment references, status and timing for DANA, QRIS, OVO, GoPay, bank transfer or virtual account activity so we can match account records.

You can contact account support with an access request. We may verify ownership first, then assess which records can be provided under the Privacy Policy and local law.

Send a correction request through the account support route and describe the detail that needs changing. Do not include your password; we will use an ownership check where needed.

Contact us with a clear removal request and the account detail needed to locate it. Some records may need to remain for security, reconciliation or legal duties where local law permits.

Cookies can keep a login session and security preference available on your browser. If you clear or block them, you may need to verify access again or see altered session behaviour.