3 types of device IDs
App ID, ad ID and session ID are used; these help identify separate devices
This page clearly explains how the Viptaka App collects device identifiers, cookies and usage data, and you will also easily see what information remains for Dhaka users on bKash, Nagad and Rocket-based accounts, and for how long.
Download Viptaka APK
Effective date: September 2026
Three things are the main point here: what is collected, why, and how long it lasts
App ID, ad ID and session ID are used; these help identify separate devices
Screen size, OS version, language and network type are checked; old phones load settings correctly
Traffic indications at country and city levels distinguish Dhaka and Chattogram users
These are not personal identifiers but are very useful for login, support and security checks
The session is inferred by matching font, timezone, language, GPU, and cookies; this reduces fake logins
Issues are detected by load time and scroll behavior; crashes usually take less than a minute
Browser fingerprinting here prioritizes security and stability over limited profiling
Clearing the browser may change the session, so Viptaka Login may require login again
Controlled from 3 places
Cookies are needed to retain preferences, language and session; if you want, you can disable third-party cookies from the browser
This may require entering some settings again, but pages load without issue on Dhaka's slow network
Camera, storage and notification permissions can be controlled separately; not granting unnecessary permissions reduces data usage
On Android 8+ phones this setting is very easy to change in 2 minutes from the menu
Clearing cache, cookies and history ends the old session; you may be asked to re-authenticate on next login
This helps quickly detect issues, especially shared-phone users like it
From settings, email, language, and notifications can be changed; keeping personal data low reduces trouble
Keeping names matching on bKash, Nagad or Rocket linked profiles helps Dhaka support verify quickly
Crash reports and usage patterns do not read personal chats or passwords
Some session SDKs only keep language and preferences; separate tracking lists are reviewed every 30 days
Tools not needed are not kept; this reduces data leakage risk
If you want Privacy Help You'll also see clearer guidance on the page
Normal login data stays briefly, then old records are rotated and deleted
Temporary logs are kept to detect unusual access; this helps troubleshoot support issues
When the account is closed, unnecessary data is deleted; only required records remain as usual
This is the real data retention limit in the Viptaka App; once it expires, data is reduced
There are 4 simple rights
Many users in Bangladesh want to save mobile data, so controls are kept in small steps
If you need to change information after registering with Viptaka, you can write to support
If questions come from Dhaka, support usually asks for a single clear list
Email, user ID and time of issue, include them to speed verification
Which device, which version and on which page the issue occurred, these are checked
Questions related to bKash, Nagad or Rocket can also be sent from the mobile
For more information Viptaka contact page See
Viptaka Download APK
Here tracking and device sessions can be viewed together
If the same account is on multiple phones, differences are easy to spot