App / Slots
This page sets out how rajacusn collects, uses and protects the personal data you share when you open an account, make a transaction or contact our support team. Every practice described here applies to your use of the site where local law and eligible regions permit access.
When you create an account, we collect the registration details you enter — name, contact address and login credentials. When you move funds through OVO, Bank Transfer or QRIS, the transaction reference, amount and timestamp are recorded in your account wallet history. We do not store full payment credentials on our servers; the payment rail itself handles authentication at the point of transfer. We also collect the device type and browser session data needed to keep your account session secure and to detect unusual access patterns. Usage data — which sections of the site you navigate, how long a session runs — helps us understand how the lobby performs and where account flows can be clarified. We keep this data only for as long as it serves the purpose it was collected for, or for as long as applicable law in eligible regions requires us to retain it. You can view your own transaction records at any time from the account dashboard after login. If a record appears incorrect, the correction path is described in the Rights section of this page.
OVO transaction references are logged in your wallet history the moment a transfer is confirmed. You can check the entry from the account dashboard without contacting support.
Bank Transfer records show the originating account reference and confirmation timestamp. These entries are read-only; disputes go through the support contact path.
QRIS payment confirmations appear under transaction history alongside the scan timestamp. We retain these records in line with applicable retention requirements for eligible regions.
This policy covers four distinct areas of your relationship with the site. Understanding which area a situation falls into tells you exactly where to look — and what we are and are not responsible for.
Covers data collected at login, registration and session management. This includes login credentials, device fingerprint and session tokens. We control this data directly and it is subject to all rights described on this page.
Covers deposit and withdrawal records processed through OVO, Bank Transfer and QRIS. Transaction data is shared with the relevant payment rail to complete the transfer; we retain the reference log on our side.
Covers how we track which game categories, live dealer rooms or account utility pages you visit. This is session-level usage data, not personally identifiable browsing history sold to third parties.
Links or tools that take you outside rajacusn — including external wallet apps and game studio platforms — fall outside this policy. Their own privacy terms apply once you leave our site environment.
You have concrete actions available to you under this policy, and each one has a clear path inside your account. Start with the account dashboard after login — that is where your transaction history, registered contact details and session activity are visible. If you find a detail that needs correcting, such as a contact address entered incorrectly at registration, you can update it directly from the account settings page without raising a support ticket. For questions about what data we hold or how a specific record was generated — a QRIS entry that looks unfamiliar, for example — the support contact form is the right route. We aim to acknowledge data queries through the same channel you used to send them. If you want to request deletion of account data that is no longer needed for an active account, that request also goes through support, and we will respond with confirmation of what can be removed under applicable retention rules.
Log in and open the transaction history tab in your account dashboard. Every OVO, Bank Transfer and QRIS entry is listed there with a reference and timestamp you can cross-check against your own wallet app.
Account settings lets you update your registered contact information directly. Changes take effect on the next login session; no support ticket is needed for standard field edits.
If you have a question about a specific record — what data it contains, why it exists or how long it is kept — send it through our support contact form. Name the transaction reference or date so we can locate the record quickly.
For removal of data tied to a closed or inactive account, submit a written request through the support channel. We confirm which data can be deleted and which must be retained under applicable law before acting.
Privacy questions are handled through the same support paths as account queries. Choose the channel that suits your situation — live chat for quick clarifications, the contact form for requests that need a written record, and email for formal data queries that require a documented response.
Open the chat widget from any page while logged in. State that your question is about account data or this policy so the agent routes it correctly from the start.
The contact form is available from the support section of the site. Include your account username and a brief description of the data concern so we can locate the relevant record.
For formal written requests — data correction, deletion or a question about retention — email our support address. We respond in writing and keep a record of the exchange on file.
We apply session-level security to every authenticated page, which means your account details and transaction history are not accessible without a valid login token. Cookies on this site serve two purposes: keeping your session active while you navigate between the lobby, account wallet and support pages, and recording anonymous usage signals that help us improve the site layout. We do not use cookies to build a marketing profile that is sold to advertisers. Retention periods for personal data depend on the type of record — transaction logs linked to OVO, Bank Transfer or QRIS payments are kept for the period required by applicable financial record rules in eligible regions; purely technical session data is cleared on logout or expiry. If this policy is updated, the revised version is published on this page with the update date noted at the top.
Every account session uses a secure token that expires on logout or after a period of inactivity. This limits the window in which an unattended device could be used to access your account.
We use session cookies to maintain your login state and preference cookies to remember display settings. No third-party advertising cookies are placed without your awareness; you can clear them from your browser settings at any time.
Transaction records — including QRIS and OVO payment references — are retained for the period required under applicable rules in eligible regions. Account data tied to a closed account is reviewed and removed once the retention period has passed.
When we update this policy, the new version replaces the previous one on this page. The date at the top of the page reflects the most recent revision. Continued use of the account after an update constitutes acknowledgement of the revised terms.
These are the questions we hear most often about how data is handled on this site. If your question is not answered here, the support contact paths in the section above are the right next step.
We collect the registration details you enter — name, contact information and login credentials. Once you transact, payment references from OVO, Bank Transfer or QRIS are added to your account history. Session and device data is collected to secure your login.
Your transaction history, registered contact details and session records are visible from the account dashboard after login. If you need a broader summary of what we hold, send the request through the support contact form and we will compile it for you.
Open account settings after login and edit the relevant field directly. Most contact details can be updated there without raising a support ticket. For fields that are locked — such as a registered identity document — contact support with the correction and supporting detail.
Payment data is shared only with the payment rail you use — OVO, Bank Transfer or QRIS — to complete the transaction. We do not sell personal data to advertisers. Game studio platforms handle their own session data inside the game window; their terms apply there.
Transaction logs are retained for the period required under applicable financial record rules in eligible regions. Once that period passes and your account is no longer active, records are reviewed for deletion. The exact duration depends on local law where access is permitted.
Check the entry in your account dashboard first — it will show the payment rail, reference and timestamp. If you cannot match it to a transfer you made, contact support through live chat or the contact form with the reference number so we can investigate the record.