Reference

Privacy Policy for Your supempo Account

VIP Baccarat, Aviator, Royal Fishing, and Tennis Betting stay under one account, and our Privacy Policy explains what account, device, cookie, and DANA, OVO, GoPay, QRIS payment records…

Account data explainedDANA OVO GoPay QRIS contextCookie controlsPrivacy request contacts
supempo Privacy Policy for Your supempo Account
PRIVACY HELP

How To Reach Our Privacy Desk

Fast privacy help starts with the channel that matches your request. Use live chat for account-access questions, email for correction or deletion requests, and the account inbox when you need us to…

Live chat privacy queue Use live chat from the lobby footer when you need help with login history, cookie choices, or a device you do not recognise. We answer privacy-related chat requests from 09:00 to 01:00 WIB.
Email request path Send correction, deletion, or export requests to [email protected] from the email attached to your account. Include your username, phone number ending, and one payment reference so we can confirm the request safely.
Account inbox checks For small privacy questions, open Account > Inbox after login and message us there. This path lets us connect your request to the right account without asking for extra documents in chat.
ACCOUNT CONTROLS

How We Handle Privacy Requests

Privacy work is part of our account operation, not a separate formality. We limit internal access to payment records, keep security logs for account protection, and check request identity before changing stored…

Registration data

When you join, we store the details needed to open and protect your account: username, password status, phone number, email address, referral code if used, and timestamps linked to your registration step.

Payment records

DANA, OVO, GoPay, and QRIS activity creates references we use to match deposits, verify withdrawal ownership, and answer wallet questions. We keep only the payment data needed for account and record checks.

Cookie choices

Cookies help keep your session open, remember language choice, and spot repeated failed logins. You can change browser cookie settings anytime, though some account pages may ask you to log in again.

Device monitoring

Account > Security > Devices shows the phones, tablets, and desktops recently linked to your login. If a device looks unfamiliar, contact chat so we can help you secure access and update credentials.

Retention periods

We keep account, payment, and security records only as long as needed for operation, dispute handling, fraud screening, and legal obligations. When data no longer serves those needs, we delete or anonymise it.

Correction requests

If your phone number, email, or wallet label is wrong, contact us before making another transaction. We verify the request against account history before changing records that affect payments or account recovery.

Common Privacy Policy Questions

You should be able to check privacy points before you open an account or update your wallet details. These answers cover the requests we receive most often about account data, device records, cookies, payment references, and contact paths. For anything linked to a live account, we may ask you to message us from the registered email or account inbox first.

We collect the details needed to create and protect your account, including username, phone number, email address, password status, registration time, IP address, and device signals used to spot unusual access attempts.

We store payment references, wallet labels, transaction status, and timestamps needed to match deposits or verify withdrawals. We do not store payment app passwords, PINs, or full credentials from DANA, OVO, GoPay, or QRIS.

Email [email protected] or contact live chat from your logged-in account. Tell us which detail is wrong, include your username, and be ready to confirm a recent payment reference or registered phone number.

Yes, you can request an account data copy by email from your registered address. We verify identity first, then prepare available account, payment, and login records that can be shared under applicable rules.

Cookies keep your session active, remember preferences, and help us detect repeated login failures. You can clear them in your browser settings, but the next visit may require a fresh login and device check.

Only staff who need access for support, payment checks, security review, or legal handling can see relevant request records. We restrict access by role and keep action logs when sensitive account details change.

Simple corrections can be handled during support hours after identity checks. Data copies or deletion requests may take longer because we must verify ownership, check payment records, and follow legal retention duties.