Reference

sedayu55 Privacy Policy For Your Account

Our sedayu55 Privacy Policy explains how we handle the details linked to your account, from phone verification before access to wallet records for DANA, OVO, GoPay and QRIS.

Clear data categoriesCookie choicesAccount contact pathIndonesia access wording
sedayu55 sedayu55 Privacy Policy For Your Account
CONTACT ROUTES

Ask About Privacy From Your Account

A direct contact route helps when you want to ask about a Privacy Policy clause, correct an account detail or check why a data request needs another verification step.

Account data request Use the support route inside your signed-in account to ask what personal details are connected to your profile. We check the registered phone first, then explain the available access or correction step without sending account records to an unverified contact.
Cookie question If a mobile browser keeps a session choice or shows a cookie prompt again, contact us through the account support path. Tell us your device type and browser behaviour so we can separate a cookie setting from a sign-in or account issue.
Payment record query For a Privacy Policy question involving DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, include the relevant transaction reference. We use that reference to locate the correct record while limiting disclosure to the verified account contact.
DATA PRACTICES

How We Handle Your Privacy Choices

We keep this Privacy Policy close to the account journey so you can check data practices before using the lobby.

Account details

When you open an account, we record the details needed for sign-in and phone verification. We use them to recognise your account, deliver account notices and handle a request connected to your profile, rather than asking you to repeat the same details in every support message.

Device activity

A mobile browser may send device and session signals when you move from login to the lobby, including while opening Live Baccarat Elite or Fortune Fishing Game. We use these signals for access checks, fault diagnosis and account protection, not as a replacement for your registered account details.

Cookies

Cookies can retain a session, remember a browser choice or help us measure whether a page loads correctly. You can manage cookie settings through your browser, although removing some cookies may require you to sign in again before reaching the lobby.

Payment records

A DANA, OVO, GoPay or QRIS reference can be stored with the account event it relates to, while bank transfer and virtual account records support matching and status checks. We use these records to resolve a payment query and keep the account ledger consistent.

Account security

Phone verification and sign-in checks help us distinguish your request from an unknown contact. Keep your login details private, sign out on shared devices and contact us through your account route if a session or wallet status looks unfamiliar.

Retention and changes

We retain account, security and transaction records only for the period needed for the stated service, legal duties and dispute handling. To ask for a correction, deletion where available or a copy of your data, contact us after signing in so we can verify the request.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover what we collect, how wallet references are handled, what happens on a phone and how you can ask us to change or explain a record. For a case tied to your own account, use the verified contact route rather than sharing personal details in a public message.

It explains how we handle account details, phone verification, device signals, cookies, support requests and transaction records. It also describes contact steps for access or correction requests. The services available to you depend on local law and may differ where local law permits access only to certain regions or account functions.

We may collect the contact and sign-in details needed to create your account, verify your phone and protect access. We can also record session activity, device signals, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

We keep the payment reference and status needed to match a DANA or QRIS request with the correct account event. This helps us answer a receipt or status query without exposing records to an unverified contact. The same approach applies to OVO, GoPay and bank transfer references.

Yes. Sign in, open the support route shown in your account area and state whether you want access to a record or a correction. We verify the registered phone before responding, then explain which data can be provided, changed or retained for a stated legal or security reason.

Our mobile browser pages may use cookies for sessions, browser choices and page performance. You can adjust them in your browser settings. Removing session cookies may sign you out, so you may need to complete phone or account access checks again before opening the lobby.

We keep each category for the period needed for account operation, security, transaction matching, dispute handling and applicable legal duties. The period can differ for sign-in details, cookie records and payment references. You can ask support how a specific record is treated after account verification.

Use the support route inside your signed-in account and mention the Privacy Policy section that prompted your question. Include only the details needed to identify the issue. We may confirm your registered phone before discussing personal or payment data, including a GoPay, OVO or virtual account reference.