Slots / Casino
Your account data stays under clear rules at vip805. We collect only what is needed to run your account, process transactions through DuitNow, Boost, and Bank Transfer, and keep your session records accurate. This policy sets out exactly what we hold, why we hold it, and the steps available to you when you want to review or correct it.
When you open an account, we record the details you provide at registration: your name, contact information, and the payment method you choose to use. For transactions processed through DuitNow or Boost, we log the reference number, the amount, the timestamp, and the status shown in your account wallet. Bank Transfer records follow the same structure. We do not store full card numbers or full bank credentials — only the reference data needed to match a payment to your account and to resolve any dispute you raise through support. Session data — which pages you visited, how long each session ran, and which device type connected — is retained to support account security checks and to let you review your own activity log. Cookies record your login state and your in-session preferences; they do not carry financial data. Where local law and eligible regions permit, your account information may be processed by systems that support the platform. Availability depends on local law and applies only where permitted.
This policy covers the account you hold at vip805 and the data we process directly. It does not extend to third-party services you connect through your own device, nor to payment networks that operate under their own terms once a transfer leaves our system.
Any data tied to your login, your account dashboard, your session history, and your wallet balance falls within this policy. You can review this data after logging in from the account settings page.
Payments made via DuitNow, Boost, or Bank Transfer generate records we hold on our side. Once a payment moves through the network, the payment provider's own policy governs data on their infrastructure.
Pages, game content, and promotional material displayed on vip805 are covered. If you follow a link away from our domain, the destination site operates under its own privacy terms, not ours.
External platforms — including device-level analytics, app store services, or any integration you enable on your own device — are outside our scope. We are not responsible for how those services handle data we do not transmit to them.
You hold practical controls over the information we keep. From your account dashboard, you can view your transaction history — every DuitNow transfer, Boost payment, and Bank Transfer entry is listed with its reference number and status. If a record looks wrong, the correction path starts with a support ticket rather than a self-edit, so a member of the team can verify the change against the payment reference before it is applied. Requests to close your account and delete associated data can be submitted through the same support channel. We will confirm receipt and let you know the outcome. Where local law and eligible regions permit, data portability and access requests are handled in writing via our support contact address. Response times depend on the volume of requests in queue; you will receive an acknowledgment when your request is logged.
Log in and open your transaction history page. Every payment reference, timestamp, and wallet movement linked to your account is listed there in chronological order.
Submit a support ticket naming the field you want corrected and the accurate value. Our team checks the request against your account record and payment references before applying any change.
If you are unsure what information we hold, contact us in writing. We will describe the categories of data linked to your account without exposing records that belong to another party.
Send a closure request through support. We will confirm the steps, settle any open balance to your wallet, and confirm deletion of personally identifiable fields within the period allowed under applicable local requirements.
For any question about how your data is handled, the channels below connect you to the team responsible for account and privacy matters. Include your registered email address and a short description of your request so we can match it to your account quickly.
Open the chat widget from your account dashboard. This is the fastest path for account-specific questions, including transaction record queries and correction requests.
Send a written request to our support address, available on the Contact page after login. Written requests are required for data access, correction, and account closure under this policy.
Your transaction history, session log, and account settings are accessible directly after login. Many record queries can be resolved there without contacting support.
Account security at vip805 relies on session controls you can see: an activity log in your dashboard shows every login event with device type and timestamp. Cookies on vip805 are limited to session management and preference storage — no advertising cookies are set by us, and you can clear them from your browser at any time. Data retention follows the period required to support account history and resolve payment disputes; records are not held beyond what the account function or applicable local requirements call for. If you want to know more about our approach to a specific data category, contact us through the support channels listed on this page.
We collect registration details, payment references, and session logs. Financial credentials are not stored in full — only the reference data needed to match and verify a transaction against your wallet.
Session cookies keep you logged in. Preference cookies remember in-session settings. Neither type carries financial data, and both can be cleared from your browser's storage controls without affecting your account balance.
Your activity log, accessible after login, records each session's device type and start time. If a session you do not recognise appears, raise it through live chat so the team can review and act on it.
Records are kept for the period needed to support your account and meet applicable local requirements. Submit a written request through support to ask about retention periods for a specific data category.
These questions cover the areas members ask about most when reading through this policy. If your question is not covered here, the support channels on this page are the right next step.
At registration we collect your name, contact details, and the payment method you choose — for example DuitNow or Boost. We also log the device type used at login. We do not collect payment credentials in full; only the reference data needed to process and match transactions.
Yes. Log in and open the transaction history and activity log in your account dashboard. Those pages show every payment reference, session timestamp, and wallet movement linked to your account. For a broader data summary, submit a written request through email support.
Raise a support ticket naming the field and the correct value. We verify the change against your account record and any relevant payment reference before applying it. Self-editing of certain fields is not available directly in the dashboard for security reasons.
We do not sell your personal data. Payment networks such as DuitNow and Boost receive only the reference data needed to process a transaction. Where local law requires disclosure to regulatory bodies, we comply. No advertising or analytics companies receive your account data from us.
Retention after account closure follows the period required by applicable local requirements and the time needed to settle any open payment disputes. Once that period passes, personally identifiable fields are deleted. Contact support in writing if you want the specific period that applies to your account.
Send a written deletion request through the email support channel listed on the Contact page after login. Include your registered email address. We confirm receipt, settle any open wallet balance, and advise on the timeline for deletion of identifiable fields under this policy.