Reference

petir108 slot Privacy Policy for Your Account

petir108 slot Privacy Policy shows how we handle your account details, phone verification, device access and payment records when you use our Indonesia-facing service.

Account clarityWallet recordsCookie choicesLocal-law access
petir108 slot petir108 slot Privacy Policy for Your Account
CONTACT THE POLICY TEAM

Privacy Help Beside Your Account Path

A clear contact route helps when you need to ask about a record, cookie or account detail.

Account privacy request Use the help route from your signed-in account to ask what personal data is…
Wallet record question If a DANA, OVO, GoPay or QRIS reference appears in your account, share only…
Cookie access request Tell us whether your question concerns cookies on Android, iPhone or desktop access.
DATA HANDLING DETAILS

Six Practical Privacy Commitments

Privacy is handled through ordinary account steps rather than hidden settings. We separate the details needed for account access from payment references, limit internal access to relevant handling…

Data we collect

We collect details you provide for an account, such as contact information and phone verification data, plus login, device and…

Cookie operation

Cookies can keep a signed-in session active, remember selected settings and help us identify a return from the same browser.

Account protection

Phone verification and account checks help us distinguish an authorised request from an attempt to access another person’s record.

Storage and retention

We retain account, security and transaction references only for the period needed for the stated service, dispute handling, security checks…

Requesting a copy

You can ask what personal data we hold by using the account help route and identifying the account with its…

Correcting details

If your contact detail, phone number or account data is inaccurate, tell our support channel which field needs correction.

Privacy Policy Questions About petir108 slot

These Privacy Policy answers address the account and payment questions you may search before opening an account. We keep the wording specific to petir108 slot, including phone verification, browser sessions and local wallet references. If your situation is not covered, use the account help route and describe the data record involved; access depends on local law.

The Privacy Policy covers account details, phone verification, login activity, device signals, cookies and payment references. It explains why we handle those records, how we protect them, how long they may be retained and how you can request access or correction.

We may collect the contact details you submit, your phone verification result, login and session activity, and device information used to protect account access. A DANA, OVO, GoPay or QRIS transaction can also create a payment reference linked to your account.

No. Our Privacy Policy distinguishes a payment reference or status from your wallet credential. When you use DANA or OVO, we may receive details needed to match the transaction, but you should not send a wallet PIN or password through our support channel.

Open your signed-in account, select the help route and ask for a personal-data request. Identify the account with its connected phone or email. We may complete an identity check before sharing records, particularly when the request concerns login, device or wallet activity.

Yes. Use the account help route and name the inaccurate field, such as a phone number or contact detail. Provide the account identifier needed to locate it, but do not include a password, wallet PIN or complete bank credential in your request.

Cookies may keep your session active and remember browser settings on Android or iPhone. Removing them can sign you out or require account steps again. Your browser controls manage these files, while our Privacy Policy explains the related session and preference handling.

We keep records for the period needed for account operation, security checks, payment disputes or applicable legal duties. After that need ends, the relevant data follows our deletion or anonymisation process. The exact period can differ by record type and local requirements.