Sports / Slots
At a688, your account data and payment activity — including bKash and Upay transactions — are handled with clear purpose and limited scope. This policy explains what we collect, why we collect it, and what choices you have, subject to your local law and eligible regions.
This privacy policy applies to all activity on a688, including account registration, login sessions, deposit and withdrawal requests, and support interactions. When you use bKash or Upay to fund your account, the transaction reference and amount are recorded against your account wallet to confirm receipt and support any dispute you raise. We collect the minimum data needed to operate your account: your registered contact detail, device session identifiers, and payment confirmation records. We do not sell your personal data to third parties. Data shared with payment processors like bKash and Upay is limited to what those processors require to complete your transaction — we do not pass browsing history or game activity to them. Cookies and local storage are used to keep your session active across page loads and to remember your preferred language setting. You can clear these through your browser at any time, though doing so will end your active session. Retention periods vary by data type: active account data is held while your account remains open; transaction logs are kept for the period required under applicable financial record rules in your eligible region. If you close your account, we will delete or anonymise personal data within the timeframe set out in the account closure process, except where retention is required by law.
Deposit and withdrawal references tied to your bKash wallet are stored in your account transaction log. You can view these from the account history section after login.
Upay transaction confirmations are matched to your account wallet in the same way. If a transfer does not reflect, the reference number in your Upay app is the fastest way to raise a query with our support team.
We use session cookies to keep you logged in while you navigate between the lobby, account, and payment pages. These expire when you close your browser or log out manually.
Messages sent through our support channel are retained to track the resolution of your query. They are not used for marketing and are not shared outside the support function.
Not every service you reach from a688 falls under this policy. Understanding the boundary helps you know who to contact when a question arises about your data.
Login activity, session tokens, and account preference settings are fully within scope. We control this data and you can request a review or correction through the account settings page.
The record of a bKash or Upay transfer that lands in your a688 wallet is within scope. The data held by bKash or Upay on their own systems is governed by their own privacy terms, not ours.
Pages, game lobbies, and promotional notices served from a688 are within scope. Game content delivered by studio providers operates under their own data handling, which we do not control.
Links to external sites, payment processor portals, or identity verification services fall outside this policy the moment you leave a688. Check the privacy notice of each external service directly.
You have practical options for managing the data a688 holds about you. To review the personal details on your account — your registered contact information and linked wallet identifiers — log in and open the account profile section. If any detail is incorrect, you can update it directly from that page or contact support with the correction. To request a copy of your transaction history, use the account history export available after login; this covers all bKash and Upay deposit and withdrawal records tied to your account. If you want to raise a question about how your data is used, or if you believe data is being held incorrectly, you can contact us through the support channel listed on the site. For account closure and the deletion of personal data, submit a request through support and we will follow the process set out in our account terms, subject to any retention obligations under applicable law in your eligible region.
Log in and open the account profile or history section to see the personal data and transaction records we hold against your account.
Update your registered contact detail directly in account settings, or send the correction to our support team if the field is not editable from your end.
Contact support through the published channel on a688 if you believe data is held incorrectly or want to understand how a specific piece of information is used.
Submit a closure request through support. Personal data will be deleted or anonymised within the timeframe in our account terms, except where local law requires retention.
If you have a question about this privacy policy or want to act on any of the rights described above, use the contact routes published on a688. We do not list channels or hours we cannot verify.
Open the support widget on a688 while logged in to send a message directly tied to your account. This is the fastest route for data correction or transaction queries.
The account help section covers common data and privacy questions, including how to export your transaction history and how to update your registered details.
For a written data access or deletion request, use the contact form on the support page and mark your message as a privacy request. We will respond through the same channel.
We apply access controls so that your account data is reachable only through authenticated sessions. Payment references from bKash and Upay are stored in encrypted form and are not exposed in plain text outside your account view. Cookie use is limited to session management and language preference — we do not use tracking cookies to build advertising profiles. If you want to limit cookies, your browser settings give you full control, though session cookies are required for the account area to function. For any change to how your data is used beyond what this policy describes, we will update this page and note the change date at the top of the policy.
bKash and Upay transaction references are stored in encrypted form. They are visible to you in your account history and to our support team when resolving a query you have raised.
Cookies on a688 are used to maintain your login session and remember your language setting. No third-party advertising cookies are set from our pages.
Account data is accessible only through an authenticated session. Support staff access is logged and limited to what is needed to resolve your open query.
When this policy changes, the updated version is published on this page with a revision note. Continued use of your account after a change means you have seen the updated terms.
These are the questions we hear most often about how a688 handles your data.
We collect your registered contact detail, a device session identifier, and the payment references from bKash or Upay transactions you make. We do not collect more than is needed to operate your account and process your payments.
Yes. Log in and open the account profile and history sections to view your personal details and full transaction log. If you need a formal export, contact support through the published channel on a688 and request an account data copy.
We share only the transaction data that bKash or Upay need to process your deposit or withdrawal — typically the amount and a reference. We do not pass your browsing activity, game history, or account preferences to payment processors.
Personal data is deleted or anonymised within the timeframe set out in the account closure process. Transaction logs may be retained longer where applicable financial record rules in your eligible region require it.
Open account settings after login and update the field directly. If the field is locked, contact support with the correct information and we will update it. Availability of self-service editing depends on the type of detail and your account status.
Use the support contact form on a688 and mark your message as a privacy request. We will review the concern and respond through the same channel. Access and eligibility for formal data rights depend on your local law and eligible region.