Live / Sports
This policy explains what data sbobetr collects when you access your account, how it is stored, and what choices you have over it. Your account details, transaction records, and session activity are handled with clear purpose — nothing collected without a reason, nothing kept longer than necessary.
When you open an account on sbobetr and use services available in Indonesia under applicable local law, we collect the data needed to run your account. This includes your registration details, login activity, wallet transactions through ShopeePay and LinkAja, and any records tied to support requests you raise. We do not collect data beyond what your account activity generates. Data is stored on secured infrastructure and is not sold or transferred to third parties for marketing purposes. Retention periods follow what is reasonably necessary to maintain accurate records and respond to account queries — when data is no longer needed for those purposes, it is removed from active systems. Access to your stored data is restricted to account and support functions. If local law in Indonesia requires us to adjust how data is handled, those requirements take priority. Availability of specific data services depends on eligible regions and local regulatory conditions. We do not make representations about data handling that go beyond what we can operationally verify on your account.
Understanding the boundary of this policy helps you know where to direct questions and what protections apply to different parts of your experience on sbobetr.
This policy covers data generated when you log in, manage your account settings, update wallet details, or change session preferences. All activity tied directly to your sbobetr account falls within this policy's scope.
Deposits and withdrawals processed through ShopeePay and LinkAja generate transaction records covered here. We retain those records for account reconciliation and to support any queries you raise about your balance or payment history.
Game session data — such as rounds played in titles available in the lobby — is recorded at the account level for history and support purposes. Game content itself is supplied by studios; their own data practices are separate from this policy.
Links or services that take you outside sbobetr's platform are not covered here. Once you leave our account environment — for example, completing a payment on a wallet provider's own app — that provider's privacy terms apply, not ours.
You have concrete actions available under this policy. Your account dashboard, accessible after login, shows the transaction and session records we hold. If any detail looks incorrect — a name, contact address, or linked wallet — you can update it directly in account settings or ask our support team to correct it on your behalf. For questions about what specific data we hold, or to request that records be reviewed, contact our support channel and include your account reference. We aim to respond to data queries within a reasonable time and will confirm what records exist, what they are used for, and how long they are kept. If you want to close your account and request data removal, that path runs through the same support route — the current process and any conditions that apply are shown when you raise the request. No step in this process requires you to contact anyone outside sbobetr's own support team.
Log in and open your account dashboard. Transaction history, session activity, and linked wallet records are displayed there. If a record is missing or looks wrong, note the date and amount before contacting support.
Name, contact information, and wallet details can be updated in account settings. For fields that are locked after verification, contact support with the corrected information and your account reference.
Use the support contact route listed on this page to ask what data we hold about your account. Include your account ID so we can locate the relevant records and respond accurately.
If you want your account closed and data removed, submit the request through support. The conditions and timeline for data removal following closure are confirmed at the time you make the request.
Privacy and data questions are handled through our account support team. Use the route that works for your situation — live chat for quick clarifications, or email if you need a written record of the response.
Open the chat window from your account dashboard after login. For policy questions, describe your query and include your account reference so the team can locate your records without delay.
Send your data or privacy question to our support address available in the account help section. Include your account ID and a clear description of what you are asking about — we respond in writing so you have a record.
The account help section, accessible after login, lists current contact methods and the expected handling time for data requests. Check there first to confirm which route is active for your query type.
Our approach to data security is built around limiting what we collect, controlling who can access it, and removing it when it no longer serves a clear purpose tied to your account.
Account data is stored on secured servers with access controls limited to the functions that need it — account management and support. We do not use open or shared storage environments for records tied to individual accounts. Security practices are reviewed as part of ongoing platform maintenance.
We use cookies to maintain your login session and remember account preferences across visits on mobile and desktop. No marketing or cross-site tracking cookies are set by sbobetr. You can review cookie settings in your browser, though disabling session cookies will affect your ability to stay logged in.
We keep account records for as long as your account is active and for a period after closure sufficient to resolve any outstanding queries or comply with applicable local requirements in Indonesia. When retention conditions are met, records are removed from active systems. Specific retention periods for your account type are confirmed on request through support.
When this policy changes in a way that affects your rights or how your data is used, we update the page and note the revision. The current version is always the one shown here. To ask about a specific change or confirm how it affects your account, contact support with your account reference.
These are the questions our account holders ask most often about how their data is handled, what choices they have, and how to act on them.
We collect the details you provide at registration — name, contact information, and linked wallet details — along with login activity, session records, and transaction history generated when you use ShopeePay or LinkAja. We do not collect data unrelated to your account activity.
Yes. Your account dashboard shows transaction history, session activity, and wallet records after login. For a fuller picture of what we hold, contact support with your account reference and we will confirm the records and what they are used for.
Most fields — contact details and wallet information — can be updated directly in account settings. If a field is locked after verification, raise a correction request through support and include your account ID along with the correct information. We will update it and confirm when done.
We do not sell or transfer your data to third parties for marketing. Data shared with payment processors like ShopeePay and LinkAja is limited to what those transactions require. When you use a third-party service outside our platform, their own privacy terms apply from that point.
Records are kept while your account is active and for a reasonable period after closure to handle any outstanding queries or meet local requirements in Indonesia. When those conditions are satisfied, data is removed from active systems. You can ask support for the retention terms that apply to your specific account type.
When you request account closure through support, we confirm the data removal process and timeline at that point. Records are retained only for the period needed to resolve open queries or satisfy applicable local regulatory requirements, then removed. The conditions are confirmed in writing when you submit the closure request.