Mobile / App
Every piece of information connected to your a00 account — from login activity to payment records linked to DuitNow, Boost or GrabPay — is handled according to this policy. We set out exactly what we collect, why we hold it, and the steps available to you when you want to review or correct it.
This policy applies to all data processed when you access a00, create or maintain an account, and carry out transactions through payment channels including DuitNow, Boost and GrabPay where those channels are available under local law. We collect the information that is reasonably necessary to operate your account: login credentials, contact details, device identifiers and payment references. We do not sell this data to third parties. Transaction references tied to DuitNow or Boost transfers are retained only as long as required for account reconciliation and any dispute resolution process. Cookies and session tokens are used to keep your login state consistent across devices — device continuity means your account status carries over without requiring you to re-authenticate each time you switch between mobile and a desktop session. The current data retention period and cookie settings applicable to your account are shown in the privacy preferences section after you log in. This policy is subject to the laws of the jurisdiction in which access is permitted; applicability depends on local law and eligible regions. Where any local regulation imposes a different standard, we follow the more protective requirement.
Not every interaction with a00 falls under a single set of rules. Knowing what this policy covers — and where it hands off to another party's terms — helps you understand exactly who holds your data at each step.
Login events, session history and account settings are fully within scope. We hold these records and you can request access to them through the account support route described in this policy.
When you transact via DuitNow or Boost, the payment processor holds its own record under its own privacy terms. We receive only the reference and status; the underlying financial data sits with the processor.
Pages you browse, game lobbies you open and session duration are logged at account level. This data is used for account continuity and service improvement; it is not shared for advertising purposes.
Links to external providers or payment platforms leave our policy scope the moment you follow them. We recommend reviewing the privacy terms of any third-party service before submitting information there.
Your account data is not static — you have practical options at each stage. Start by logging in and heading to the account settings page, where your profile details, contact information and linked payment references are displayed. From there, you can correct any entry that is out of date. If a record looks wrong and the settings page does not give you the field to change it, the correct step is to raise it through our support channel with a short description of the discrepancy. Requests to review what data we hold, or to ask about retention periods tied to a past DuitNow or Boost transaction, are handled the same way — contact support and reference your account. We aim to acknowledge requests and provide a substantive response within a reasonable time, subject to any identity verification steps shown in the support flow at that time.
Log in and open account settings to see the data we hold. Profile details, contact fields and linked payment references are all visible there without needing to contact support first.
Edit your contact information directly in account settings. For fields that are locked — such as registered email or verified identity details — submit a correction request through the support channel.
If something in your account record looks incorrect or you want to understand what a particular data entry relates to, contact support with your account reference and a description of the question.
Questions about how long we keep a specific record — for example, a resolved DuitNow transaction reference — can be directed to the policy contact address listed in the support section below.
If this policy raises a question that the account settings page does not resolve, there are three clear routes to follow. Each route is suited to a different kind of request — routine account edits, formal data enquiries and urgent account concerns each have their own path so your question reaches the right person.
Open the chat widget from any page after logging in to ask a policy question in real time. Suitable for quick clarifications about what data is shown in your account or how a payment reference is stored.
For formal requests — such as asking for a copy of the data we hold or requesting a correction to a locked field — send a written enquiry to our policy contact address. Include your account reference in the subject line.
Many policy actions do not require contacting us at all. Log in, go to account settings, and the current state of your profile, session preferences and linked payment channels is shown there directly.
Data handling at a00 follows a few consistent principles that you can verify through your own account. Session tokens are issued at login and tied to your device profile, which is how the platform keeps your account state consistent when you switch between a phone session and a desktop one — no re-authentication is needed for that continuity to work. Cookies used for this purpose are session-scoped by default; persistent cookies are noted in the cookie preferences panel accessible after login. Payment references from DuitNow, Boost and GrabPay transactions are stored only as reconciliation identifiers — we do not store full card or bank numbers. Retention periods vary by data type and are listed in the privacy preferences section of your account. The policy contact route for formal data requests is the email channel described in the support section.
Session and preference cookies are used to maintain account continuity across devices. The cookie settings panel in your account lets you review which cookie categories are active and adjust preferences where local law permits a choice.
Login events are logged with device and session identifiers. If an access event looks unfamiliar, the account security section lets you review recent sessions and flag any that you did not initiate — the steps are shown there after login.
DuitNow, Boost and GrabPay transaction references are kept for the period needed to resolve any account or payment dispute. The retention period for each transaction type is stated in the privacy preferences section of your account.
When this policy is updated in a material way, the change is noted at the top of this page with the date it took effect. Continued use of the account after a notified change is taken as acknowledgement of the updated terms.
These are the questions we hear most often about how account data, payment records and session information are handled under this policy. If your question is not covered here, the support chat or email route listed above is the right next step.
We collect the information you provide during registration — contact details, login credentials and any identity verification data required by the account opening flow. Device identifiers and session data are also logged from the point of first login onward, as described in this policy.
We receive and store a transaction reference and status from DuitNow and Boost — not the underlying bank or wallet credentials. Those records are held for the period needed to reconcile your account and resolve any dispute. The retention period is listed in your account privacy preferences.
Log in and open account settings to view your profile, contact details and linked payment references. For a fuller data access request — covering session history or transaction records — submit a written request through the email support route with your account reference included.
Fields like your contact email and display name can be edited directly in account settings. If a field is locked — for example, a verified identity detail — contact support through the live chat or email channel and describe the correction needed. We will guide you through the verification steps shown in that flow.
We do not sell your data or share it with third parties for marketing purposes. Payment processors like DuitNow and Boost receive only what is necessary to complete a transaction; they hold that data under their own privacy terms, not ours.
Closing your account triggers the retention schedule described in the privacy preferences section. Some records — such as transaction references tied to DuitNow or Boost payments — are kept for the minimum period required by applicable financial record rules in your eligible region before deletion.
Use the email data enquiry route listed in the support section of this page for formal privacy concerns. Include your account reference and a clear description of the issue. For a quick clarification, the live support chat handles policy questions in real time after you log in.