Reference

Privacy Policy for Your episode88 Account

episode88 Privacy Policy explains what we collect when you open an account, sign in, use the lobby or check a wallet status.

Account clarityWallet recordsCookie choicesDevice access
Explore Our Lobby Read FAQ
episode88 Privacy Policy for Your episode88 Account
CONTACT WHEN NEEDED

Privacy Policy Help Near Your Account

A direct account support path helps when you need to ask about the Privacy Policy, correct a profile detail or understand a wallet record. Start from the support route attached to your account or cashier area so we can match the request with the right account context. Include the email or phone detail linked to your account, the subject of your request and any relevant payment reference. Do not send a full password, one-time code or complete wallet credentials. We answer policy questions about access, cookies, retention and data changes through the available account contact route.

Team online

Policy questions

Ask about the Privacy Policy through the account support path shown after sign-in. Tell us whether your question concerns account data, cookies, a device record or a DANA, OVO, GoPay or QRIS payment reference, and we can direct it to the right handling step.

Data correction

If your account detail is inaccurate, request a correction through account support and identify the field that needs attention. We may ask for a verification step before changing contact or phone data, so the request does not weaken the security of your account.

Wallet record help

For a payment record that does not match your account view, share the date, rail name and reference visible to you. We can check the account-side record without asking you to disclose a password or one-time code, including for QRIS or bank transfer activity.

DATA HANDLING DETAILS

What We Do With Account Data

The Privacy Policy sets out how we handle data across the account journey rather than treating every record as the same.

Account details

We handle the contact and verification details needed to create and maintain your account. Phone verification can be required before account access, and support may use the linked contact detail to confirm that a data-change request comes from the account holder.

Cookies

Cookies and similar browser signals can remember selected settings and help us understand whether a sign-in session is functioning. You can manage available cookie choices in your browser, while changing them may affect saved preferences or parts of the account path.

Device signals

A mobile or desktop sign-in can produce device, browser and security signals connected with the session. We use them to protect account access and investigate unusual login activity, not to request your password or one-time code through a support message.

Payment references

A cashier record may show a DANA, OVO, GoPay, QRIS, virtual account or bank transfer reference. We use the account-side details needed to check status and reconcile activity, while the named payment provider remains responsible for its own processing practices.

Retention

We retain a record only for the purpose described in the Privacy Policy, such as account operation, security, dispute handling or a legal duty. When a record is no longer needed for those purposes, our handling follows the applicable deletion or archival process.

Your request

You can contact us to ask about access, correction, deletion where applicable, cookie choices or the use of your data. Use the account support route, describe the request clearly and provide only the minimum detail needed for us to locate the relevant record.

Privacy Policy Questions for episode88

These Privacy Policy answers cover the account and payment questions that usually matter before you proceed. They explain the practical path for checking data, changing a detail, understanding cookies and asking about retention. For any request tied to a specific account, use the signed-in support route and avoid sending passwords or one-time codes. Account access remains subject to local requirements, so availability depends on local law or where local law permits.

The episode88 Privacy Policy covers data linked to account creation, phone verification, sign-in, device and browser signals, cookies, support messages, security events and payment references. It also explains purposes, retention, request paths and the role of external payment providers such as DANA, OVO, GoPay and QRIS.

Use the account support route available after sign-in and ask for access to the data connected with your account. Include the linked email or phone detail and describe the records you need. We may verify the request before responding, so account data is not disclosed to the wrong person.

Yes, you can ask for a correction through account support when a profile or contact detail is inaccurate. Name the field that needs attention and provide the linked account detail. We may require phone verification or another account check before changing information that affects access or payment status.

It covers the account-side payment references needed to check a DANA, OVO, GoPay, QRIS, virtual account or bank transfer status. The relevant payment provider may collect and process additional data under its own terms. Our Privacy Policy explains our handling, not the provider's separate practices.

Cookies and related browser signals can remember selected settings, support a sign-in session and help us identify technical problems. Your browser provides controls for available cookie choices. Removing cookies may clear preferences or require another sign-in, but it does not by itself erase every account record.

We keep account, security, support and payment-related records only for the stated operational purpose, account protection, dispute handling or a legal duty. The applicable retention period can differ by record type. You can ask support how a particular record is handled without sending your password or one-time code.

Start with the signed-in account support path and state whether your request concerns access, correction, deletion where applicable, cookies, retention or a payment reference. Add the relevant date or reference, but share only necessary details. Availability of account services in Indonesia depends on local law.

Related Pages

episode88 Indonesia ShopeePay Wallet Topup Account information Access guide episode88 Casino