Mobile / Slots
This page sets out exactly how babyshark22j handles the personal data tied to your account — from the moment you register through every wallet transaction you complete via Boost or Bank Transfer. Every paragraph here covers a real data practice, not a generic platform description.
When you open an account, we collect the details you enter — name, contact address, and the payment method you choose to link, whether that is Boost, Bank Transfer, Touch 'n Go eWallet or FPX. We hold this data to operate your account, process wallet transactions, and respond to support requests you raise. We do not sell your personal data to third parties. Where we engage processors — such as payment gateway operators who handle Boost or DuitNow routing — those processors act on our instructions and are not permitted to use your data for their own purposes. The same applies to any technical partner that supports account verification or session security. Data we collect at login includes device identifiers and session tokens. These help us detect unusual access patterns and keep your account wallet intact. Cookies used on the site are limited to session management and are not used for cross-site advertising profiling. Retention periods depend on the nature of the data. Transaction records linked to Boost or Bank Transfer activity are kept for as long as required under applicable local law and eligible-region obligations. Account profile data is held while your account remains active and for a reasonable period after closure. Access to this site and its services is subject to local law and available only where permitted in your region.
Not every interaction on the site falls under a single rule set. This section draws a clear line between what this policy governs and what it does not — so there is no confusion about where your data rights apply.
Login sessions, password resets and account verification steps are fully within scope. When you access your account on mobile or desktop, the data generated — session tokens, login timestamps — is governed by this policy.
Deposits and withdrawals made through Boost, Bank Transfer or other supported payment rails generate transaction records we hold. Those records are covered here, though the payment gateway operator's own terms also apply to their handling of payment data.
Game session data — which titles you open, how long a session runs — is collected to support account history and dispute resolution. Content from studios such as Pragmatic Play or PG Soft is delivered via their platforms; their own data practices apply to in-game events.
Links or services that take you off babyshark22j — including external payment pages or partner redirects — are not covered by this policy. Once you leave our domain, the third party's privacy terms govern what happens to any data you submit there.
Your account dashboard is the first place to check the personal details we hold. After login, the profile section displays the name, contact address and linked payment method currently on record. If anything is incorrect — a contact address that has changed, a Boost wallet number that is no longer active — you can submit a correction request directly through the support channel, and the team will update the record on the back end. For questions about what specific data we hold on your account, or to raise a concern about how a piece of data is being used, the support contact path is available at all hours via the Live Chat widget or through the account help email. Response timelines depend on the complexity of the request, but we acknowledge every query and confirm the outcome once the review is complete. Where local law grants additional access or deletion rights, eligibility depends on your region and the applicable rules there.
Open the profile section after login to see the personal data currently linked to your account — name, contact details and the payment method on file, such as Boost or Bank Transfer.
Submit a correction through Live Chat or the help email if any stored detail is outdated. The team verifies the request and updates the record; you will receive confirmation once done.
If there is uncertainty about how a particular piece of data is handled — a transaction record, a session log — send the question via the support channel. We respond with the specific detail once the internal check is complete.
On account closure, retention of transaction data is subject to applicable local-law obligations. Contact support to ask what is held post-closure and for how long, based on your region.
Privacy questions are handled through the same support channels as account queries. Use Live Chat for faster responses, or the help email when you need to attach documentation — for example, a correction request with supporting identity details.
Open the chat widget from any page on babyshark22j. State that the query is privacy-related so it is routed to the correct team member without delay.
Send a written request to the support email address shown in your account dashboard under Contact Us. Attach any documents relevant to a correction or data-access request.
The profile section inside your logged-in account is the starting point for reviewing what data is currently on record before raising a formal query through chat or email.
Security measures applied to account data include session encryption during login and payment activity. When a Boost deposit or Bank Transfer is in progress, the connection between your device and the site runs over an encrypted channel. Account passwords are stored in hashed form — meaning support staff cannot retrieve a plain-text password, only issue a reset link via the contact address on file.
Cookies on babyshark22j are limited to session management and site functionality. No cross-site advertising cookies are set. You can review and clear cookies through your browser settings at any time without affecting your account data.
Login sessions are tied to device identifiers. Unusual access — a new device or location — triggers a verification step visible on your account. If a session looks suspicious, contact support through Live Chat immediately to have the session terminated.
Transaction records linked to Boost, Bank Transfer and other supported payment rails are retained for the period required under applicable local law. Profile data is held while the account is active and for a set period after closure, as disclosed on request.
When this policy changes, the updated version is published on this page with a revised date at the top. Continued use of the account after a policy update constitutes acknowledgement of the revised terms. Where a change is material, we will notify via the contact address on file.
These are the questions most commonly raised about how personal data is handled on babyshark22j. Each answer covers a specific aspect of the policy — from what data is collected at sign-up to how to request a correction.
At registration, we collect the name, contact address and payment method details you enter — for example, a Boost wallet number or Bank Transfer account reference. After that, session data and transaction records are generated each time you log in or complete a wallet transaction.
We share data only with processors directly involved in running the service — payment gateway operators for Boost, DuitNow or FPX routing, and technical partners supporting account security. These processors act on our instructions only and are not permitted to use your data independently.
Records tied to Boost deposits, Bank Transfer activity and other supported payment rails are retained for the period required under applicable local law in eligible regions. You can contact support to ask about the specific retention period for your account records.
Log in and check the profile section first. If the contact address or payment method on record is outdated, raise a correction request via Live Chat or the support email. The team confirms the update once the change is applied on the back end.
Cookies on this site are limited to session management — keeping your login active while you browse. No advertising or cross-site tracking cookies are set. Clear them any time through your browser's cookie settings; this does not affect your account data or wallet balance.
The revised policy is published on this page with an updated date at the top whenever a change is made. For material changes, we send a notification to the contact address on file. Continued use of the account after the update date is taken as acknowledgement of the new version.