How secure is my data in the f111 App?
Data is transmitted with SSL encryption, and vendor access is restricted; login and payment sections are secured separately
Effective date October 2026 this page shows which third-party vendors the f111 App uses, and what information may be shared.
We only collect the necessary data for login security, device verification and payment processing.
| Vendor | Purpose | Shared information | Region |
|---|---|---|---|
| Cloudflare | SSL protection and traffic filtering | IP, browser data, session signals | Global |
| Google Analytics | View Usage Type | Page visits, device type, referrer | Global |
| SMS Gateway | Sending OTP | Mobile number, delivery status | Asia-Pacific |
| Email Service | Account Notification | Email address, Event log | EU |
| Identity Verification | Account Security | Name, Date of Birth, Document Match | Global |
| Payment Processor | bKash, Nagad, Rocket Transactions | Transaction ID, Time, Amount | Bangladesh |
A small note: we select vendors only based on their policies, encryption and data restrictions.
| 4.6/5 | 65,331 | 8.8M+ | 99.6% |
| Rating | Review | Active User | Uptime |
Since 2018, f111 has been running, and active services are available in 7 countries; we review security updates step by step.
Paths like f111 Login, f111 Register, and f111 APK do not bring separate risks, because everything runs at the same security level; another thing we noticed: even on slow networks the SSL check remains the same.
Before choosing a vendor, we look at three things: their policies, data minimization and technical security come first.
If a vendor requests unnecessary data, it is skipped, so security and privacy go hand in hand in the f111 App.
Only vendors with a clear data usage policy are eligible
If data is requested twice for the same task, it is reduced
Vendors do not see the entire database; they work in separate sections
This method keeps the f111 App's privacy policy simple and easy for users to understand
Each vendor has a data processing agreement detailing what will be seen, how long it will be kept, and when it will be erased
We view login tokens, sessions, and payment events separately; information related to bKash, Nagad, and Rocket is used only for transaction verification
Whether you use it from Dhaka or Chittagong, your account is protected under the same rules, with a note: no vendor can sell data as their own
Sometimes for security or performance, a vendor change is needed, and before launching a new service, both old and new are reviewed
Your primary account information remains the same; only the backend processing path changes, and that is done without downtime
We regularly verify that SSL certificates, log retention, and permissions are correct; these steps are usually divided into three checklists
In the images below you will see how data protection works in the f111 App, with each scene separate to keep things clear
Data is transmitted with SSL encryption, and vendor access is restricted; login and payment sections are secured separately
Yes, only the information needed for transaction verification is sent; full account details are not exposed to the payment vendor
When a new device is detected, additional verification may occur, making the account more secure against unauthorized access
The same security rules apply to the APK as well; only use official sources and proper verification
If you have privacy questions, you can contact the help team; Dhaka users also typically contact first about account security, login and file verification
See more instructions f111 Help Center And f111 Terms and For new users New user guideWill also be useful
Register Login