Slots / App
This page sets out the legal terms that govern your use of araslit, including how we handle your account data, what falls within our policy scope, and the steps available to you when questions arise. Access and eligibility depend on local law and are available where local law permits in your region.
Our legal terms are written to be readable, not just formally compliant. Every clause directly affects how your account operates — from how we store your transaction records to how you raise a correction request. When you use araslit through a mobile browser or via a local payment rail such as LinkAja or Bank Transfer, the same policy applies regardless of the channel you chose. We do not apply different terms to different payment methods; your rights under this policy remain consistent across your wallet activity, account history and session controls. Where an action touches a third-party service — for example, a payment network or a game content provider — we describe what we are responsible for and where that responsibility ends. Availability of certain features depends on local law and the eligible regions in which we operate. If any clause is unclear, the support path described in the contact section below is the right place to start. We update these terms when our practices change, and we will communicate material changes through your account notification channel before they take effect.
Transactions processed via LinkAja fall under standard account-wallet policy; records are visible in your transaction history after login.
Bank Transfer activity is logged against your account and subject to the same data-retention terms as all other deposit and withdrawal records.
Your account wallet balance, including any pending and confirmed amounts, is covered by our transaction-record retention clause.
Where DANA is used as a deposit route, the same policy scope applies; availability depends on local law and eligible regions.
Not every interaction on araslit sits inside the same policy boundary. Understanding the scope helps you know exactly where to direct a question — whether it concerns your account access, a transaction record, the content you see on screen, or a service provided by a third party outside our direct control.
Login credentials, session controls, account verification steps and your personal detail records are fully within scope. Any request to review or correct these goes through our account support channel.
Deposit and withdrawal records processed through supported rails — including LinkAja and Bank Transfer — are covered. We retain these records and you can request a copy through your account dashboard after login.
Game lobby content, page text, promotional material visible on araslit pages and session data generated during your play are within our policy scope. RTP figures are shown only where the game provider exposes them in the game interface.
Payment network processing, game content delivery by studios, and external links you follow from this site operate under those third parties' own terms. We describe what we pass to them and are not responsible for their independent practices.
You have concrete actions available at each stage of your relationship with araslit. Reviewing your own records is the most common starting point — your transaction history, session log and account details are all accessible after login through the account dashboard. If you find a detail that needs correcting, such as a contact address or a wallet identifier, the account settings page shows the editable fields directly. For questions that go beyond what the dashboard can resolve — a data-handling query, a request to understand how long your records are kept, or a concern about a specific transaction — our support team is the right next step. You do not need to escalate through a formal process to ask a straightforward question; the live chat and email paths described in the support section below connect you to the same team that handles policy queries.
Log in and open the account dashboard. Transaction history, session records and personal details are shown there; no separate request is needed to view your own data.
Account settings surfaces the fields you can update directly. For changes that require verification — such as a registered phone number or wallet identifier — follow the instructions shown in the relevant field.
If your question is about data handling, record retention or a specific transaction, contact support with your account reference and a clear description. We will respond through the channel you used to reach us.
For unresolved policy matters, ask support to escalate your case. Provide the original contact date and any reference number given. The escalation path is the same regardless of your payment method or device.
Policy questions sometimes need a direct answer rather than a help article. We offer three contact routes for legal and account-related queries, each suited to a different level of urgency. Choose the path that matches the nature of your question — live chat for immediate account concerns, email for formal policy requests, and the account dashboard for self-service record access.
Open the chat icon from any page after login to reach our support team directly. This is the fastest path for account-access questions and transaction clarifications.
For formal policy requests — including data queries, correction requests and record-retention questions — email the address listed in your account contact section. Include your account reference in the subject line.
Your account dashboard after login shows the current state of your records, wallet activity and session history. Most self-service policy actions start and finish here without needing to contact support.
We apply consistent practices across every account — whether you access araslit from a mobile browser using DANA or through a Bank Transfer desktop session. The following points describe our approach to the areas members most commonly ask about when reviewing our legal terms.
We collect account and transaction data only to operate your account, process payments and respond to your support requests. We do not sell your personal data to third parties. The categories of data we hold are described in our full policy document, accessible after login.
We use cookies to keep your session active and remember your account preferences across visits. You can review or adjust cookie settings through your browser. Disabling certain cookies may affect login persistence and session controls.
Transaction records, session logs and account details are retained for the period required by applicable terms and applicable regulations in eligible regions. When a retention period ends, records are deleted or anonymised according to our standard process.
Your account is protected by login credentials you control. We do not store payment credentials like full card numbers or wallet PINs. If you suspect unauthorised access, contact support immediately through live chat and follow the account-recovery steps shown on the login page.
These questions cover what members most frequently ask when reviewing our policy page. If your question is not answered here, use the live chat or email path listed in the support section above.
We hold the information you provided during registration, your transaction history, session records and any communications you sent to support. You can view most of this directly in your account dashboard after login, or request a full summary through our email support channel.
Open account settings after login — editable fields are shown directly on that page. For details that require identity verification before they can be changed, follow the instructions displayed in the relevant field. If you need help, live chat can walk you through the steps.
Yes. The same policy terms apply to all supported payment rails, including LinkAja and Bank Transfer. Transaction records for both are retained under the same conditions and are visible in your account transaction history regardless of which method you used.
Records are retained for the period required under applicable terms and the regulations of eligible regions. After that period, they are deleted or anonymised. If you need a copy of a specific record before it is due to be removed, contact support by email with your account reference.
Start by raising the question through live chat with your account reference and a clear description of the clause in question. If the matter is not resolved at that point, ask support to escalate it. We aim to respond to policy queries through the same channel you used to contact us.
You can submit a deletion request through our email support channel. Note that some records may need to be retained for the duration required by applicable regulations in your eligible region, even after a deletion request. Support will confirm which records fall into this category when they handle your request.