Key data security metrics in the hexa66 App
4.7 / 5
Average Rating
Users have a consistent experience
79,883
Reviews
Feedback from Dhaka and other cities nationwide
308K+
Active users
Many return to the same account
99.2%
Uptime
Less hassle when a session stops midway
How the hexa66 App privacy policy works
Tokenized data
Card number is not stored directly; the sensitive part is replaced with a separate token, reducing transaction risk
Limited storage
Only necessary information is kept; session, device, and verification records stay on separate layers
Local usage
For Dhaka, Chattogram, and other locations, payment history is short and clear
Quick review
On any request, logs can be checked quickly to reconcile, reducing misunderstandings
The information shown after you log in to the hexa66 App is also governed by the same rules; a quick glance will show why each data is collected
Card data tokenization
Sensitive numbers are kept separate
The full card number, CVV, and authentication data are not stored together; the system keeps them on separate layers so nothing is visible from one place
This keeps the payment screen small and clean; inside the hexa66 App only the necessary data appears, while the rest is controlled in the backend
- Token is used only for specific transactions
- The same token is not used repeatedly
- Manual copy-paste risk reduced
PCI scope and system controls
Payment section is kept separate
Card-related parts are on restricted access; those in support do not see all information at once
This keeps scope small, and compliance is easier; using bKash or Nagad for top-ups applies the same control policy
- Access permissions are granted in steps
- Logs are kept separate for auditing
- Suspicious sessions can be identified
Processor list and local payments
Specific partners, specific tasks
hexa66 App uses only the required processors; for Bangladesh, well-known channels like bKash, Nagad, and Rocket are given greater priority
Many Dhaka users prefer quick verification, so processing steps are kept short, reducing unnecessary waiting for deposits or account verification
- Processor tasks are clearly defined in advance
- Third-party access is limited
- Transaction records are kept separate
How chargeback data is stored
Documents are clear in case of disputes
Any chargeback or erroneous charge is kept with relevant documents separately; this shows time, amount, and source of the transaction at a glance
There is no need to keep such data scattered for long; only minimal records are kept in the hexa66 App to make reviews easier
- Date, reference, and status remain
- Unnecessary personal notes are not kept
- Only the necessary parts are shown on specific requests
Crypto wallet data
Wallet addresses are treated separately
When using a crypto wallet, addresses and transfer history are stored on separate levels, so outsiders cannot view the entire profile at once
Users who register with hexa66 to open a new account will find data control easier, and nothing extra is taken without user consent
- Wallet address shown to a limited extent
- Transfer history opened on specific requests
- Preferences can be changed from account settings
Cookies, permissions, and controls
Cookie preference
Necessary cookies stay enabled; you may reduce analytical cookies
You can view information
It is easy to understand what is kept in this summary of your stored data.
Right to rectify
If information is incorrect, you can request an update; name, contact, and identity verification stay on the same page.
Delete request
Requests to delete applicable parts can also be made, but some records may have to be retained for legal reasons.
For more details Help Center There are short answers about the hexa66 APK, sign-in, and account settings.
Your rights and contact
If you have any questions, you can send a message on the hexa66 Contact page; help is provided separately for policy, data protection, and account information.
One thing is clear at the end: in the hexa66 App your privacy, cookie preferences, and data control are kept under the same umbrella.
Register Log in
