a17 App privacy policy: data protection, cookies and rights

This page explains clearly how data for the a17 App is collected, stored, and removed when needed; Dhaka and Bangladesh users also receive the same protection for communications related to bKash, Nagad, Rocket

Download a17 APK a17 Login guide
a17 Data Security Dashboard

Effective date and quick summary

Effective date: July 2026; if any issue is detected in the a17 App, it is blocked first, then the user is notified

This explains what data is needed, when cookies are enabled, and where your control lies; if needed, information related to a17 Register and a17 Login is also covered by the same policy

4.4/5 rating

Average user response

214,570 active users

Regular account users

846+ titles

Content library is large, so the policy is clear

99.2% uptime

System status is monitored

How data is captured

1. Logs and security signals

Sign-in, device type, and error logs are kept to quickly detect failed logins

2. Account verification

The same device, new location, or unusual behavior are checked

3. Cookie

Users in Bangladesh can choose cookies to maintain sessions

What you'll see on

Cookie notice is shown compactly, so it's easy to understand if you are on a slow network in Dhaka, though changing preferences takes no more than 2 steps

a17 Cookie Preferences Panel

Preventing loss and keeping data separate

If unauthorized access is detected, the session is ended first, then the risky device is isolated

Not all data is kept open together here; sensitive information, logs, and cookie data are kept in separate layers

End session

If an abnormal sign-in occurs, the old session ends

Separate storage

User data and operational logs are not kept in one place

Risk flag

If there are repeated failed attempts from the same IP, a warning is

  • Two-factor verification is checked first
  • Personal information is not disclosed unless necessary
  • Rocket or bKash-related communications are also limited

How notifications are sent when a breach is

In any data incident, internal verification occurs first, then if needed, an email or account notification is sent

The notice includes what happened, which data was involved, and what you should do - these three items; you will see the same notice format when signing in from Dhaka or opening on a mobile device

What the notice

  1. When an event is detected
  2. Which data was touched
  3. Your actions 1-2 steps
a17 Alert Phone Screen

Risk reduction and assistance

If problems occur, password reset, session refresh, and device verification are performed together to regain control quickly

In Bangladesh, use of bKash, Nagad, Rocket is common, so clear Bengali instructions are kept in the account notes

Password change

If abnormal login occurs, set a new password

Device match

A new phone may require re-verification

Support team

A response comes with context when a message is

If you have doubts about a17 Download or a17 APK, download only the official file from trusted pages

Audit, rights, and contact

You can view, modify, or restrict your data, and you may delete it if necessary

Audit records are kept for 12 months to see who viewed what, to detect irregularities

Your rights

  • You can request a copy of your data
  • You can tell us to correct incorrect
  • You can change cookie preferences.

a17 Login or account-related questions; go to the contact page, and if privacy issues arise, the Data Protection Team will provide an initial reply within 48 hours.

Data Controller

a17 Team

Email support

Submit a policy or access request

Support pages

Terms More Responsible use Read

Log in Registration