Reference

Privacy Policy for Your sewaplay Account

sewaplay Privacy Policy explains what we collect when you open an account, use the lobby, or check a DANA or QRIS transaction.

Account dataWallet recordsCookie choicesSecurity requests
sewaplay Privacy Policy for Your sewaplay Account
DATA HELP PATH

Get Privacy Policy Support

A clear contact path helps when you want to ask about personal data rather than a game or wallet result.

Account request Ask us to explain the personal data linked with your account. Include the contact detail used during account access and identify whether your question concerns login records, device signals or a Privacy Policy change.
Wallet reference For a DANA, OVO, GoPay or QRIS data question, share the transaction date and visible reference only. We can use that context to check the record without asking for your wallet password or security code.
Receipt check If a bank transfer or virtual account reference appears in a data request, attach only the relevant receipt detail after removing passwords and codes. Our support path can explain what record is held and why it is needed.
HANDLING DETAILS

What We Do With Account Data

Privacy depends on practical handling, so we describe the account steps behind this policy. We record information needed to create and protect your account, connect support replies to the right request and…

Data collection

When you open an account, we may collect your contact detail, verification result, login events and support messages. We use these records to provide access, answer your request and identify activity that does not match your account.

Cookie controls

Cookies can keep a session active and help us see whether the Privacy Policy loads correctly on a mobile browser. You can manage cookie settings through your browser, although changing them may affect account access or saved preferences.

Account security

We use account-step checks and session signals to reduce unauthorised access. Never send a password or one-time code through support. If your phone or login detail changes, contact us through the account support path before sharing further records.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may produce references used to reconcile a request. These references help us investigate status without requiring the full credentials for your payment wallet or bank account.

Retention choices

We keep personal data only while it supports the stated account, security, support or legal purpose, subject to local requirements. When you ask about deletion or retention, we explain which records can change and which must remain for a defined reason.

Change requests

To request correction or ask what data is linked to you, contact support with your registered contact detail and a clear Privacy Policy subject. We may ask for an account step to confirm the request belongs to you.

Privacy Policy Answers for Indonesia

These Privacy Policy answers cover the questions we expect before an account is opened or while an account is being used. They explain the practical records connected with login, wallets, cookies and support. If your circumstances are not covered, contact us through the account route with the smallest amount of detail needed to identify your request. Access remains subject to local law.

The sewaplay Privacy Policy covers account details, contact information, login and device signals, cookies, support messages and payment references. It explains why we use those records for access, security, support and payment checks, and how to ask about correction or retention where local law permits.

We may collect the contact detail you submit, account-step results, login events, device signals and messages sent to support. If you use DANA, OVO, GoPay or QRIS, we may also receive a transaction reference needed to check wallet status or answer a related request.

Yes. The Privacy Policy covers payment references connected with DANA and QRIS, along with OVO, GoPay, bank transfer and virtual account checks. We use a date, visible reference or status detail to investigate a request and do not need your wallet password or one-time code.

Use the account support path and identify your request as a Privacy Policy matter. Provide the registered contact detail and explain whether you want a correction, access request or retention explanation. We may ask for an account step to confirm your identity before making a change.

Cookies can preserve a login session, remember a setting and show us whether the Privacy Policy page works on a mobile browser. You can manage them in your browser controls. If you block required cookies, some account access steps or saved preferences may not function as expected.

We retain personal data while it serves the stated account, security, support or payment-check purpose, and for any period required by local law. If you ask about a specific record, we explain its purpose, the applicable retention reason and whether a change or deletion is available.

You can ask through support which type of data is connected with your account and why it is used. Internal access is limited to people who need the record for account access, security, support, payment checking or a legal requirement where local law permits.