Reference

semesta66 Privacy Policy for You

The semesta66 Privacy Policy explains what we collect when you open an account, check wallet status, or enter the lobby from your phone.

Account clarityWallet dataCookie choicesContact path
semesta66 semesta66 Privacy Policy for You
CONTACT OPTIONS

Three Ways To Ask About Privacy

A clear contact route matters when you want to ask about the semesta66 Privacy Policy or correct account data.

Account message Send a privacy question through the account support path after login.
Cashier query For a payment-related data question, include the DANA, OVO, GoPay or QRIS reference shown…
Access request If you cannot sign in, state that your request concerns the Privacy Policy and…
HANDLING DETAILS

How We Manage Your Account Data

We handle personal data according to the purpose that brought you to semesta66: account access, phone verification, wallet status, payment matching, support or policy administration.

Account records

When you open an account, we record the details needed for account access and phone verification. We use those details to connect your login, support messages and account requests, not to ask you for unrelated personal details.

Cookie controls

Cookies and browser storage may keep your session active or remember a page preference on mobile and desktop. You can review or remove these settings through your browser controls, although changing them may affect sign-in continuity.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can be linked to your account transaction record. We use the reference to check status and receipts, while wallet passwords and verification codes stay with you.

Login protection

Phone verification and device activity help us assess account access requests. If a sign-in looks unusual, we may ask you to confirm ownership before changing account data or discussing a payment record.

Retention purpose

We retain account, support and transaction records only for operational, security or legal purposes connected with the service and this policy. If you ask about removal or retention, we explain the applicable limitation and the next account step.

Correction requests

You can ask us to correct inaccurate account details or clarify how a record is used. Send the request through account support with a safe identifier; we may verify ownership before making a change.

Privacy Policy Questions Before Access

These Privacy Policy answers address the account and wallet questions we expect from Indonesian customers before they open an account. They explain the practical path for data access, corrections, cookies, payment references and account security. If your situation is different, contact us with a safe identifier and tell us which part of the policy you need clarified.

It covers account details, phone verification, login and device signals, cookies, support messages and transaction references. It explains how we use those records for account access, payment matching, security and policy administration. Service access depends on local law.

We may keep a transaction reference and status connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. This helps us check a receipt or stalled status. We do not need your wallet PIN or one-time verification code.

Send an account support message that identifies your request as a Privacy Policy data request. Add a safe account identifier, such as the connected phone detail, and avoid sending passwords. We may confirm ownership before discussing or supplying account records.

Yes, you can ask us to correct inaccurate account or contact details through the account support path. Explain which field is wrong and provide a safe identifier. We may request phone verification before changing the record or confirming its status.

Cookies or browser storage can support a session and remember a page setting when you move from login to the lobby. You can manage them in your device browser settings. Removing them may require you to complete the account access step again.

We use phone verification and relevant device or login signals when assessing access requests. If activity appears unusual, we may ask you to confirm account ownership before changing details or discussing payment records. Never share a password or verification code.

Use the account support path after login and label the message as a Privacy Policy request. For a DANA or QRIS receipt question, include the transaction reference instead of wallet credentials. If you cannot sign in, explain that clearly so we can provide the next verification step.