Reference

Open siki4d Privacy Policy before you join

Your account path from Mobile App login to DANA, OVO, GoPay, and QRIS wallet checks is covered here, so you know what we collect before you enter Sic…

Account data useCookie choicesDANA recordsQRIS checks
siki4d Open siki4d Privacy Policy before you join
CONTACT PATHS

Ask support about your privacy request

Fast privacy contact matters when you need to correct a phone number, ask about cookie use, or question a wallet reference. Our support team handles privacy questions through live chat inside the account area and email from the help page. For identity protection, we may ask you to confirm your username, registered phone number, last login device, or a recent DANA, OVO, GoPay, or QRIS reference before we discuss account data.

Team online

Live chat window

Open the chat icon after login and choose the privacy topic. We reply during 09:00–23:00 WIB, and we may ask for your username plus last wallet reference before checking personal data.

Email request

Send privacy questions through the help page email form with your registered phone number and account username. Keep payment screenshots cropped to the reference line, not your full wallet screen.

Account verification

Before changing stored details, we compare your request with login history, device type, and recent DANA, OVO, GoPay, or QRIS activity. This step keeps another person from editing your profile.

ACCOUNT CARE

Review how we handle account data

Practical privacy control starts with clear account steps. When you create a profile, we ask only for details needed to run login, wallet checks, support, and security monitoring.

Account setup data

During account setup, we store your username, password hash, phone number, referral field if used, and login timestamp.

Payment references

DANA, OVO, GoPay, and QRIS records are kept as transaction references, status markers, and time stamps.

Cookie choices

Cookies remember session state, language display, and security prompts.

Device signals

We read practical signals such as device type, IP range, browser version, and failed login count.

Retention handling

We keep account and transaction records for operational, support, security, and legal needs.

Correction requests

If your phone number, profile detail, or contact email is wrong, contact support from the registered account.

Find answers about privacy control

Privacy questions usually come up before account creation, after a wallet check, or when you change devices. The answers below explain what we collect, how we use it, and how you can reach us about correction or access requests. Each answer is tied to account privacy, not general lobby promotion, so you can decide whether our data handling fits your expectations.

We collect the details needed for account access, such as username, phone number, password hash, login time, and device signals. Wallet activity may add DANA, OVO, GoPay, or QRIS references.

We keep payment references to match wallet actions with your account, answer support questions, and check unusual activity. We do not need your full wallet app history to confirm a transaction.

Yes. Contact us through live chat or the help page email form from your registered account. We verify ownership with your username, phone number, last device, or recent wallet reference first.

No. Our cookies support session status, language display, login checks, and account security prompts. They do not read your contacts, photos, messages, or private files stored on your phone.

Use your browser settings to clear site cookies and cached data. After clearing them, you may need to log in again and complete extra account checks before wallet actions are shown.

Only staff who need the case can access your request details. We keep privacy questions in support tools connected to your account record, with checks before any profile change is made.

Access and eligibility depend on local law and are available only where local law permits. If a privacy or account request is affected by legal rules, support will explain the next available step.