1. Data Collected by beawa
beawa stores player data in two separate categories —
Data you provide directly
- Full name, date of birth, and contact information (phone number)
- NRC card or passport copy and selfie photo for KYC
- Deposit/Withdrawal transaction records (KBZPay / Wave Money / AYA Pay / CB Pay)
- Message records submitted when contacting Customer Support
Data collected automatically during platform use
- IP address, browser type, and device information
- Session duration, game type, and bet amount
- Login and logout timestamps
- Behavioral data collected during platform usage via cookies
2. Purposes for Which Data Is Used
beawa uses player data only for the following purposes —
| Purpose | Data We Collect | Legal basis |
|---|---|---|
| Account registration and verification | Full Name, Phone Number, NRC | Contractual obligations |
| Processing deposits and withdrawals | Mobile banking data, transaction records | Contractual obligations |
| Anti-Money Laundering (AML) | Transaction patterns, IP address | Legal Obligations |
| Responsible Gaming tools | Deposit records, session duration | Legitimate interest protection |
| Providing customer support | Message history | Contractual obligations |
| Promotions and bonuses | Game history, deposit records | Consent |
If you no longer wish to receive promotional emails or platform notifications, you can opt out via the Settings section in your account. The opt-out will take effect within 48 hours.
3. KYC and Identity Verification
In accordance with Myanmar law and international AML standards, beawa requires all players to complete KYC verification. How KYC information is handled is explained below —
- 1 NRC copies and selfie photos submitted by players are stored exclusively in encrypted storage and can only be accessed by the beawa KYC Team. All access, including by IT staff, is recorded in an audit log.
- 2 After KYC is complete, the original copy of the identity document is no longer needed for operational purposes, so only a thumbnail-resolution version is retained and the original copy is deleted. This minimizes the volume of data exposed in the event of a data breach.
- 3 KYC data will not be shared with the Myanmar Financial Intelligence Unit (FIU) unless a legal obligation arises from an AML investigation — and only then upon receipt of a Court Order or an official FIU directive.
- 4 Even after account closure, KYC data will be retained for the period prescribed by the relevant regulator (typically 5 years) in accordance with applicable law, after which it will be permanently deleted using a secure deletion method.
5. Data Retention Period
Different types of data are stored for defined retention periods — once a period expires, an automatic deletion process removes the data.
| Data type | Retention period | Reason |
|---|---|---|
| Account data (name, phone number) | 1 year after account closure | To assist with account reactivation requests |
| Transaction records | 5 years after transaction | Retention period in compliance with AML regulations |
| KYC Document | 5 years after KYC completion | For regulatory requests |
| Customer Support records | 2 years after ticket closure | To resolve disputes |
| Cookies / Session Data | 30 days after session end | To improve the platform |
| Game Play Log | 1 year after last play | To ensure fair play |
6. Cookies and Tracking Technologies
beawa uses cookies to keep the platform running smoothly and to improve the player experience. The types of cookies used are —
- Strictly Necessary Cookies: These cookies are strictly necessary for maintaining login sessions and storing security tokens. They cannot be declined — doing so would prevent access to the platform.
- Functional Cookies: Players' language preferences and screen layout settings are saved. The platform remains usable without these cookies, but settings will need to be configured each time.
- Analytics Cookies: Usage duration data for each platform feature is collected in aggregate form only, without identifying individual players. This data is used solely to improve the platform.
You can block cookies through your browser settings and opt out of analytics cookies via the Cookie Preference Panel in your account. beawa does not use third-party advertising cookies — no targeted ad networks are integrated into the platform.
7. Player Rights
Every player registered at beawa has the following rights regarding their personal data —
Right to access data
You can request to view the data beawa holds about you, and a response will be provided within 30 days.
Right to correct data
You may request corrections to inaccurate information through Customer Support. Correcting KYC data requires re-verification.
Right to delete data
Upon account closure, you may request deletion of data that is not subject to legal obligations. Data retained for AML compliance will be deleted once the legally required retention period has elapsed.
Right to export data
You may request an export of your account data in a portable format (JSON/CSV), and it will be provided within 14 days.
Right to restrict processing
During an ongoing dispute, you may request that processing of your data be restricted to purposes other than review of that dispute.
Right to object to profiling
You may object to automated decision-making (such as bonus recommendations) and request a human review.
Rights requests can be submitted through Customer Support and will be processed after identity verification.
8. Data Security Measures
beawa protects player data using a Layered Security Model —
- TLS 1.3 Encryption: All data transmitted between the platform and players' browsers or apps is protected by TLS 1.3, which proactively prevents man-in-the-middle attacks.
- AES-256 Storage Encryption: All data stored on the server is encrypted with AES-256, meaning that even if a server is physically compromised, the data cannot be read.
- Multi-Factor Authentication (MFA): All beawa staff are required to use MFA when accessing the Admin Panel, and players are also encouraged to enable MFA from within their accounts.
- Regular Penetration Testing: Regular penetration tests are conducted by a third-party security firm, and any vulnerabilities identified are remediated within 30 days.
- Access Control: Employees are managed under Role-Based Access Control (RBAC) and cannot access data outside the scope of their responsibilities.
9. Policy Updates
beawa may update this policy to reflect changes in law, platform operations, or improvements to player protection.
- For significant changes (such as updates to the data sharing policy or retention period), players will be notified via their Account at least 14 days in advance.
- The "Last Updated" date of this policy is displayed at the top of the page, so players can see when any changes were made.
- Continuing to use the platform after any changes takes effect constitutes acceptance of the updated policy. If you do not agree, you may close your account and withdraw any remaining balance.
How beawa protects player data
TLS 1.3 End-to-End
All data transmitted from your device to the platform is encrypted with TLS 1.3, making interception virtually impossible — providing bank-level security.
KYC Data Minimization
Once KYC is complete, the original document copy is deleted and only a thumbnail is retained, minimizing potential data loss in the event of a breach.
AES-256 Storage
All data stored on the server is secured with AES-256 encryption, so even if server access is obtained, the data remains unreadable.
RBAC Access Control
Each employee is granted access only to data relevant to their role, proactively guarding against insider threats.
Auto Deletion Schedule
When the data retention period ends, an automatic deletion process removes the data, ensuring no unnecessary data is kept beyond what is required.
Bug Bounty Program
Third-party security researchers can submit vulnerability reports, and beawa rewards submissions and resolves issues within 30 days — protecting the platform through community collaboration.