App / Slots
This page sets out how a5555 collects, stores and protects the information tied to your account — including details you provide when using Raast or Debit Card for transactions. We keep this policy clear so you know exactly what sits in your account, who can access it, and how to request changes where local law permits.
When you create an account on a5555, we collect the details you enter — name, contact information, and the payment identifiers linked to methods such as Raast or Debit Card. This information is used to verify your account, process your wallet activity and maintain a record of your session history. We do not sell your personal details to third parties, and we do not share them with marketing networks outside the scope of running the platform. Data you provide during wallet top-ups — whether through a bank transfer or a Debit Card — is handled according to the conditions the payment channel applies, and those conditions are shown at the point of the transaction. Cookies and session tokens are used to keep your login state stable across page loads, particularly on mobile. You can review which cookies are active through your browser settings at any time. Retention periods depend on account status and the requirements applicable in eligible regions under local law. Where those requirements change, this policy is updated accordingly. The current version is always the one shown on this page.
Not every part of your digital journey falls under this single policy document. Understanding the boundary between what we govern and what a third-party service governs helps you know where to direct a query.
Login credentials, session tokens and account preferences you set directly on a5555 fall fully within this policy. We control how those details are stored, who can view them and how long they are kept based on your account status and applicable local law.
When you initiate a Raast transfer or use a Debit Card, the payment channel operates under its own terms. We receive a transaction reference to update your wallet; the card or bank network's privacy rules govern what happens on their side of that exchange.
Game content from studios such as CQ9, Pragmatic Play or Habanero is served through their systems. We present the titles in our lobby, but those providers maintain their own data practices for game-engine operation — we are not responsible for data handled within their game clients.
If you follow a link away from a5555 — including any external support tool or identity verification partner — you leave the scope of this policy. Review the privacy terms of any third-party service before submitting information to it.
You hold several practical options regarding the data we keep on your account. Reviewing what we hold is the starting point: log in and open the account settings section, where your registered contact details, linked payment methods and recent wallet activity are displayed. If something looks incorrect — a name spelling, a contact number, or a linked Debit Card reference — you can submit a correction request through the support channel, and we will update the record after verifying your identity through the account login step. Where local law in eligible regions gives you the right to request deletion of certain data, you can raise that as a formal support query, and we will respond with what is and is not possible given any retention obligation that applies. For any question about how a specific piece of data is used, our support team is the direct route — we do not route those questions through automated forms alone.
Log in and navigate to account settings to see your registered details, linked payment identifiers and transaction history. This is the first step before raising any correction or query.
If your name, contact number or payment reference is recorded incorrectly, raise a correction request through support. We verify through your account login before updating any detail.
Any question about how a data point is used — including cookies, session logs or wallet records — can be submitted directly to our support team. We respond with a clear, specific answer, not a templated redirect.
Where local law and account status permit, you may request removal or restriction of certain data. Contact support with the specific record in question; we will confirm what action is possible under the applicable conditions.
For any policy-related question — including data access, correction requests or cookie settings — our support team is the direct contact point. Use whichever channel suits your situation; all three routes connect to the same team handling account and policy queries.
Open the chat widget from the account dashboard after login. State that your query relates to privacy or data, and the team will handle it from there.
Send your query to our support address shown in the account help section. Include your registered contact detail so we can locate the correct account record.
The help section inside your logged-in account lists the current contact routes and response paths for policy, wallet and account queries — check there for the most current details.
We apply access controls to limit who within our operation can view account records. Session data is used only to maintain your login state and is not retained after a session closes unless a persistent login option is active on your device. Cookie settings can be adjusted through your browser at any time without affecting your ability to log in.
Account records — including wallet history and linked payment details like Raast or Debit Card references — are accessible only to the teams that need them to operate your account. We do not expose those records to general staff or external marketing systems.
Cookies keep your login session stable, particularly on mobile where page reloads are frequent. You can review and clear active cookies through your browser settings; this does not delete your account or transaction records.
How long we keep your data depends on account status and the legal requirements applicable in the eligible regions where access is permitted under local law. We do not keep data beyond what those conditions require.
When this policy is updated, the revised version is published on this page. For significant changes that affect how your data is used, we will notify you through the contact detail registered on your account before the change takes effect.
These are the questions we receive most often about account data, cookies and contact rights. If your question is not answered here, reach the support team through the live chat or email route shown in your account help section.
We collect the details you enter during account creation — name, contact information and the payment identifiers you link, such as a Debit Card or Raast reference. We collect only what is needed to operate your account and process wallet activity.
We do not sell your personal details or share them with marketing networks. Data may be passed to a payment channel — such as the bank network behind your Debit Card — only to the extent needed to process a transaction you initiate. Each payment channel operates under its own privacy terms.
Log in and open account settings. Your registered contact details, linked payment identifiers and wallet history are displayed there. If you need a fuller record than what is visible in settings, contact support with the specific data point you want to review.
Yes. Raise a correction request through support and we will update the record after verifying your identity through account login. Deletion requests are assessed against the retention obligations applicable in eligible regions under local law; support will confirm what is possible for your account.
Cookies are used to maintain your login session and keep page state stable, especially on mobile. You can adjust or clear cookies through your browser settings at any time. Doing so does not delete your account or transaction records, though it will end any active login session.
The current version of the policy is always on this page. For changes that affect how your data is used, we will contact you through the address or number registered on your account before the update takes effect. Routine clarifications are updated on the page without individual notification.