App / Mobile
At ibosprot, your account data and payment details — including records tied to OVO, LinkAja, and QRIS transactions — are handled with a clear set of rules you can read, question, and act on. This page lays out exactly what we collect, why we hold it, and what you can do if you want to review or update your records.
This policy applies to personal data we process when you use ibosprot — covering account registration, login activity, and payment interactions through local channels such as OVO, LinkAja, and QRIS. We collect the information needed to operate your account: your contact details, device identifiers, and transaction records. We do not sell your personal data to third parties. Data is stored on secured infrastructure and accessed only by staff with a legitimate operational reason. Where data is shared — for example, to process a payment through a local wallet provider — it is limited to what that provider needs to complete the transaction. Cookies and similar tracking tools are used to keep your session active and to understand how the site is navigated; you can manage cookie preferences through your browser settings. Retention periods depend on the category of data: account records are kept while your account remains active, transaction logs are held for the period required under applicable rules, and support correspondence is retained for a reasonable operational window. Access to this platform and its services depends on local law and is available only where local regulations permit. If you have a question about a specific data category or want to know who processed a particular record, our support team can direct you to the right answer.
Payment records tied to your OVO wallet are logged against your account and held for the retention period applicable to financial transaction data under relevant local rules.
When you use LinkAja to fund your account, the transaction reference is stored on our side. The wallet provider receives only the data needed to complete the transfer.
QRIS payments generate a transaction reference and timestamp in your account history. We do not store QR codes or raw scan data beyond what is needed to confirm the transaction.
Login timestamps, device type, and session tokens are retained to support account security and to help you identify unrecognised access through your account activity log.
This policy covers data processed directly by ibosprot. Understanding what falls inside and outside its scope helps you know who to contact when a question arises — and where to look for the answer.
Registration details, login records, and session activity on ibosprot fall fully within this policy. You can request a summary of this data through the support channels listed below.
Deposits and withdrawals processed through OVO, LinkAja, or QRIS generate records on both our system and the wallet provider's system. Our policy covers the record on our side; the wallet provider's own policy governs their copy.
Game activity, bet history, and lobby navigation data collected while you use the platform are covered here. This includes session logs from titles across studios such as PG Soft, Pragmatic Play, and Spadegaming.
External links, wallet apps, and payment provider interfaces operate under their own privacy policies. ibosprot does not control how those third parties handle data once a transaction leaves our system.
You have concrete actions available to you under this policy — not just a list of abstract entitlements. If you want to see what data ibosprot holds on your account, open a support request and specify which category you are asking about (account records, transaction history, or communication logs). For corrections — a wrong contact detail or an outdated email address — the fastest path is the account settings page after login, where most profile fields are editable directly. If a field is locked or you believe a record is inaccurate, raise it with support and we will review it. Availability of specific rights may depend on local law and the eligible region your account falls under. Every request is acknowledged and handled by a real support agent, not an automated rejection. If your concern relates to how a specific OVO or QRIS transaction was recorded, include the transaction reference from your account history so the agent can locate the record without delay.
Submit a data access request through our support contact to receive a summary of the personal data held on your ibosprot account, including transaction references and login history.
Most profile fields — email, contact number, preferred language — are editable directly in account settings after login. For locked fields, contact support with the correction you need.
If you are unsure how a specific data category is used or retained, send us a message through the support channels on this page. We will identify the right answer rather than redirect you to a generic FAQ.
Where local law grants a right to deletion, you can request it through support. We will confirm what can be removed, what must be retained for regulatory reasons, and the expected timeline for each category.
For privacy-related questions or to exercise any of the rights described on this page, use the contact paths below. Include your account email and a brief description of your request so our team can route it to the right person without a follow-up round.
Open the chat widget on ibosprot while logged in. Privacy requests submitted through chat are flagged to our account team and handled separately from general support queues.
Send your privacy request by email to the address shown in your account dashboard under Contact Us. Include your account reference and the specific data category your request concerns.
The Help Centre on ibosprot carries answers to common privacy questions — including how to read your transaction history and how to update account details — before you need to open a ticket.
The practical measures behind this policy are built around your account and the payment routes you use. Here is how each area works in practice.
We use session cookies to keep you logged in and analytics cookies to understand navigation patterns. You can clear or block cookies through your browser. Blocking session cookies will end your login session and may affect account functionality.
Transaction references from OVO, LinkAja, and QRIS are stored against your account ID. We do not store full wallet credentials or payment card numbers — those remain with the payment provider.
Your account password is stored in hashed form. If you suspect unauthorised access, change your password immediately from account settings and contact support with the login timestamps you can see in your activity log.
Account data is held while your account is active. After closure, data is retained only for the period required under applicable rules. To ask about the retention window for a specific category, contact support with your account reference.
These are the questions we hear most often from people reading this policy. If your question is not covered here, the support paths above will get you a direct answer.
We collect the contact details you enter during registration, your device type and browser session data, and transaction references from payment activity through channels like OVO, LinkAja, and QRIS. We collect what is needed to operate your account — not a wider set.
Submit a data access request through live chat or the email address in your account dashboard. Include your account email and specify which category you want — transaction history, login records, or profile data — so the team can respond with the right records.
Data is shared only where necessary to complete a service — for example, passing a transaction reference to OVO or QRIS to process a payment. We do not sell personal data. Each third party receives only the minimum needed for that specific operation.
Where local law permits a deletion request, you can raise it through support with your account reference. We will confirm which data can be removed, which must be retained under applicable rules, and the expected window for completing each part of the request.
Most fields — email address, contact number, display name — are editable directly in account settings after login. If a field is locked or the change does not save, contact support with the correction and your account reference and the team will update it.
Transaction logs are held for the period required under applicable local rules. The exact window depends on the data category and the jurisdiction your account falls under. Contact support if you need confirmation of the retention period for a specific record type.