Reference

Open with clear Privacy Policy terms

When you create an account to reach Blackjack, Starlight Princess or Football Betting, our Privacy Policy explains the account, device and payment data we use before you fund…

Account data explainedDANA OVO GoPay QRISSupport 09:00-23:00 WIBLocal law applies
perihoki Open with clear Privacy Policy terms
PRIVACY CONTACT

Check your privacy contact routes

Privacy questions need a clear route, not a generic inbox. Our support team handles data access, correction, deletion assessment, cookie questions, and payment-reference checks through live…

Live chat Use live chat from the account menu between 09:00 and 23:00 WIB.
Email desk Send privacy requests to [email protected] with your registered email, account username, and the data…
Account message Inside your profile, open Help, choose Privacy request, and attach only the document we…
ACCOUNT SAFETY

Protect your account data inside perihoki

Account privacy is handled at several points, not only on this page. We limit staff access by role, log changes to wallet and profile fields, and keep payment…

Data collected

At registration we collect your name or username, contact details, password credential and login confirmation records.

Payment records

Wallet records may include payment rail, reference number, status, time and amount for DANA, OVO, GoPay or QRIS.

Cookie controls

Cookies keep your session active, remember language choices and help us measure page errors.

Staff access

Only assigned support and operations staff can view account records needed for a case.

Record retention

We keep account and transaction records for the period needed to operate the wallet, answer disputes, meet legal duties and…

Change requests

To correct contact details, sign in, open Profile > Account details, and update the field.

Ask about privacy rights

These questions focus on your privacy choices inside our account flow. They cover what we collect, why payments create records, how cookies work, and how to ask for a copy or correction. If your question involves a transfer, include only the payment rail and reference number at first; we will tell you if any extra document is needed. That keeps the request easier to verify.

At registration, we collect account credentials, contact details you provide, login records, device type, IP signals and payment references. We may also log whether you opened categories such as Blackjack or Aviator to support account safety checks.

Those rails create transaction references that must match your wallet history. We store the rail name, status, time and reference number so support can trace a funding or withdrawal question without asking for unrelated personal data.

Yes. Contact support from your registered email or account message and state that you want a copy of your data. We verify identity first, then compile records we can provide under applicable law.

For current contact details, sign in and open Profile > Account details. If you cannot access the account, email support with your username and a brief explanation so we can confirm identity before changing records.

We keep records while your account is active and for periods needed to handle disputes, wallet reconciliation, legal duties and security checks. When those reasons no longer apply, we remove or anonymise data where possible.

Our cookies focus on session, language, security and page performance. Some browser or analytics tools may set limited identifiers; you can clear them through browser privacy settings before your next sign-in.

Only staff assigned to support, risk operations or technical checks can handle your request. We record the case status, avoid asking for extra documents, and do not discuss your account with another person.