Sports / Slots
This page sets out exactly what data sogoslo collects when you use your account, how that data is held, and the steps you can take to review or correct it. Availability of this service depends on local law and is accessible where local law permits.
When you open an account with us, we collect the details you submit during registration — your name, contact address, and the e-wallet identifiers you use to connect DANA, OVO, or GoPay to your account wallet. We also log session activity, device type, and the pages you navigate inside the platform. This data serves one purpose: keeping your account accurate, your transactions traceable, and your session history accessible to you on request. We do not sell account data to third-party marketing lists. Data shared with payment processors — including the rails that handle DANA, OVO, and GoPay transfers — is limited to what those processors need to complete a transaction. We retain session and transaction records for as long as your account remains open and for a period afterward as required by applicable rules in the regions we serve. Where local law in Indonesia requires a specific retention standard, we follow that standard. If you close your account, you may request confirmation of what data remains held and for how long. Send that request through the contact path listed in the Support section below.
Not every part of your account experience falls under the same policy rules. The table below distinguishes the four areas this policy addresses, so you can navigate to the right section when a question comes up.
Login credentials, session tokens, and account verification data are covered fully by this policy. We control how this data is stored and who inside our support team can view it, within the limits that apply in eligible regions.
Payment records connected to DANA, OVO, or GoPay transfers are held by us and by the payment processor handling the transfer. Our policy governs the copy we hold; the processor's own policy governs the copy on their side.
Pages, game lobbies, and navigation elements you browse on this site do not generate personal data records. Aggregate, non-identified usage signals may be used to improve navigation clarity — no individual account is attached to these signals.
Links or integrations that take you outside the sogoslo domain fall outside this policy. Once you leave our pages, the destination site's own data rules apply. We have no control over what those external pages collect.
Your account record is not locked away. There are four concrete things you can do at any time — review what we hold, correct details that are wrong, raise a question about how your data is being used, or ask for support if you cannot find an answer in this page. To review your account record, log in and open the account settings page; the profile and contact fields shown there reflect what we hold. If a detail is wrong — a name spelling, a contact address, or an e-wallet reference — you can edit it directly in those fields, or contact support if the field is locked. For questions about data use that go beyond what this page covers, send a written query through the support channel listed below; we will respond to the specific point you raise. Where local law in Indonesia grants you a formal right to request deletion or portability of personal data, that request is handled through the same support channel, and we will confirm in writing what steps apply in your eligible region.
Open account settings after login. The profile fields visible there are the data points we hold on your account. What you see is what we have — no hidden fields behind that screen.
Edit your name, contact address, or linked e-wallet reference directly in the account settings fields. If a field is locked for security reasons, contact support and we will guide you through the verification step required.
Send your question in writing through the support contact path on this page. Include your account reference so we can locate your record. We respond to the specific question you ask, not a generic policy summary.
Where local law in your eligible region allows it, you may request that we delete or export your personal data. Submit this through support with your account reference. We will confirm in writing what is possible under applicable rules.
If this page does not answer your question, use one of the three contact paths below. Include your account reference in every message so we can locate your record without asking you to repeat it.
Open the chat widget from any page inside your logged-in account. State your policy question clearly and include your account reference. The support team can view your account record during the session.
Send a written policy query to the support email address shown in your account dashboard after login. Written requests for data review, correction, or deletion must go through this channel to be processed formally.
The Help Centre, accessible from the account menu, contains indexed answers to common policy questions. If your question is listed there, the answer includes the exact account path or form you need to follow.
Handling account data consistently is not a one-time statement — it shows up in the daily operation of the platform. Here are the four areas where our data handling practice is most visible to you as an account holder.
We use cookies to keep your session active and to remember your account preferences across visits. No cookie on this site is sold to an advertising network. You can clear session cookies from your browser settings at any time without losing your account data.
Account credentials are stored in encrypted form. Support staff can see your account reference and transaction history to assist you, but not your login password. If you suspect unauthorised access, change your password immediately from account settings and contact support.
We keep your account data for as long as your account is open and for a period after closure that reflects applicable rules in eligible regions. When the retention window closes, your personal data is removed from active systems. Anonymised aggregate data may be retained for longer.
When this policy changes in a way that affects your rights or our data practices, we will notify you through your registered contact address before the change takes effect. The current version and its effective date are always shown at the bottom of this page.
These questions come up most often from account holders reviewing this policy. Each answer points to the specific account path or contact route you need.
We collect the name, contact address, and e-wallet identifiers — such as your DANA or OVO reference — that you submit during registration. We also log your device type and session activity while you use the platform. We do not collect data beyond what your account operation requires.
Yes. Log in and open account settings. The profile and contact fields shown there reflect the personal data we hold. If you want a more complete export, submit a written request through the support email shown in your account dashboard and we will respond with the available record.
We hold the e-wallet reference you connected to your account wallet. The full payment transaction data is also held by the processor handling that rail — DANA, OVO, or GoPay — under their own policies. Our copy covers what happened on the sogoslo side of the transfer.
Support staff can view your account reference, transaction history, and contact details to assist you. Your password is stored in encrypted form and is not visible to anyone on the team. Access to account records is limited to staff who need it to respond to your request.
Open account settings after login and edit the relevant field directly. If the field is locked — for example, after identity verification — contact support through live chat or the support email in your dashboard. Include your account reference and describe the correction needed.
When a material change is made to this policy — one that affects your rights or our data practices — we will notify you at the contact address registered to your account before the change takes effect. The current version and its effective date are shown at the bottom of this page.