Locked storage
Ticket text is stored encrypted
Who can view data
Effective date: October 2026. In the laki55 App, when you submit a support ticket, its subject, time, and account reference are shown first to help provide a quick response, but unnecessary information is not requested.
From Dhaka or another city, the same rule applies; when it involves Bangladeshi methods like bKash, Nagad, Rocket, only the necessary parts for verification are kept.
- Ticket number, time, and issue type
- Basic account session data
- Chat or message history with support
- General device information if needed
How ticket content is stored
When you need help, ticket content is stored with a separate log so the same problem can be answered quickly, and previous conversations are easy to find.
Retention is limited; unnecessary notes older than 30 days are automatically reduced, and sensitive parts are kept with restricted access.
Selected notes
Only the necessary parts can be read
Account match
Ticket matches your profile
Limited time
Old notes are reduced after 30
Who has access
Not everyone can access a ticket; agent access is limited to trained support team, security reviewers, and the required monitoring team.
This rule prevents unnecessary eyes from seeing it, so Dhaka-based users also get the same answer in case of any issue, and the risk of personal data leakage is reduced.
- Access not granted without two-step verification
- Each lookup is logged
- Mobile sessions are identified separately
- Access can be terminated quickly if needed
Quality control and monitoring
Some tickets fall under ticket quality monitoring; incorrect answers, delays, or incomplete resolutions are detected, and later the team fixes it.
Monitoring does not mean spreading conversations; to avoid repeatedly explaining the same question, a service standard like 4.2 out of 5 is maintained.
Regular review
Sample tickets are reviewed
Answer quality
Same question, same answer
Improvement notes
Mistakes detected; process updated.
Secure records
Monitored data remains separate
How long data is kept
Retention is very limited; ticket history, support notes, and quality logs stay only as long as necessary, after which they are deleted or anonymized.
This policy combines GDPR-style controls, access limits, and data minimization; in this system that has been running since 2022, an uptime of around 99.4% is maintained so that the response won't suddenly stop when help is needed.
- No unnecessary data is kept
- Old records are regularly cleaned
- Sensitive parts are kept in a separate layer
- Deletion requests are also reviewed when needed
Short answers to common questions
New users often ask what privacy means and what changes; in simple terms, your data does not circulate unnecessarily, and if you use support, it can be seen by the team.
For more clarity FAQ page And Terms There, access, data, and security rules are written together
Security, cookies, and local usage
Some session cookies are needed so you don't have to log in repeatedly; this is not a personal habit, but to keep the browser session active
Many Bangladesh users access via mobile networks, so lightweight page behavior is kept for busy connections like Dhaka, and pages load quickly even with bKash or Nagad-based account flows
Contact, Help, and Your Rights
If you have questions about your data, write directly to support; our team will review the ticket, and then, if needed, tell you the steps to update or delete the record.
For more account-related actions Help Center And Contact Page Use there is written how to get a quick answer
