Can I trust BLOKK: Privacy VPN & Blocker?
This app did not meet two or more trust checks, has a critical issue in one, or has a red flag.
- Avoid if
- Relying on it for sensitive activity on public Wi-Fi
- What it means for you
- Call and text number blocking runs entirely on the device without a network lookup, and the build includes code to send analytics data only to the developer's own server rather than a third-party analytics vendor. The build also includes code to send usage data to several other analytics and advertising services, including Firebase, Google, Microsoft Clarity, and OneSignal. Some activity may be exposed with less protection than expected on public Wi-Fi.
- Main concern
- The app includes code to send domain browsing logs and login credentials to an unsecured development server
- The developer's description
- All-in-one VPN and privacy blocker offering tracker and ad blocking, scam protection, secure browsing, and call/SMS screening with no account required.
- Third-party services
- 15
- Findings rated low or higher
- 12
Open on Google PlayOpens the app's listing on Google Play in a new tab.
Full findings
Open this scan in your dashboardThe account that ran this scan sees every finding and the Rescan button there.
Trust checks
Secure by Design
One criterion not metSecurity gaps detected
Why this result
This check looks for security issues at high severity or above in the code of this build, and at least one was recorded. Issues of this kind include a credential or token another app on the device can reach, sensitive data stored without protection, and network paths that expose information in transit.
Data Minimization
One criterion not metTracking lacks clear disclosure
Why this result
This build contains analytics or attribution code written to send data to companies other than the developer. No consent step was found before that code runs, and the app's disclosures do not describe the collection in full. Tracking by itself is ordinary; what this check reports is the combination of collection, recipient and absent disclosure.
Manifest Mismatch
An item rated high or above is openDisclosure incomplete or contradicted
Why this result
The check compares the app's privacy disclosures against what the code does, and at least one claim did not match in this build. Mismatches of this kind include a data category collected but not disclosed, a recipient the disclosure omits, and an identifier attached to data the disclosure describes as anonymous.
User Control
StrongNo lock-in
Why this result
The check looks for a way to export the data an account has accumulated and a way to delete the account itself. In this build, either both were found, or the app has no account of its own and keeps its data on the device. For an app without an account, the developer has no server-side copy to export or delete, and deleting the app removes the data in its own storage.
The app uses standard platform billing through Google Play and RevenueCat for subscription management, with no proprietary purchase formats. Local databases and user data are contained within the app's own storage and are removed on uninstall. No server-held user content was identified that would require a separate deletion or export request, and no artificial barriers to cancelling or switching were found.
Red flags
The app's privacy declarations do not match its code
Why this result
The privacy declarations shipped in this build, or the ones on the store listing, state less than the code does. Declarations of this kind are what a store, a regulator and a person comparing two apps rely on.
Strengths
- Android backup is disabled, preventing ADB extraction of the locally stored traffic, call, and SMS databases
- Call and SMS number blocking against known entries can run entirely on-device via a Bloom filter without a network lookup
- Countly analytics code names only the developer's own server as its destination rather than a third-party analytics vendor
What the app contains
15 services
Third-party services the scan names in the build:
- Firebase Analytics
- Firebase Cloud Messaging
- Google App Measurement
- Microsoft Clarity
- Countly
- OneSignal
- RevenueCat
- Adyen
- Cash App Pay
- Google Play Billing
- Amazon IAP
- Microsoft MSAL
- Google AdServices
- CallerAPI
- MaxMind
Libraries
| Library | Version | Advisory |
|---|---|---|
| Room | not recorded | none confirmed |
| Google Play Billing | not recorded | none confirmed |
| Fresco | not recorded | none confirmed |
| Shimmer | not recorded | none confirmed |
| Jackson | not recorded | none confirmed |
| Datatransport | not recorded | none confirmed |
| Google Advertising ID client | 12451000 | none confirmed |
| Google Sign-In | 12451000 | none confirmed |
| Google Play Services | 12451000 | none confirmed |
| Google Play Services Location | 12451000 | none confirmed |
Show all 30 librariesShow fewer
Changes since the previous scan
- Version 1.3.24 (versionCode 1030024), score 32.
- Score 42 before, 32 after.
- Score change since version 1.3.24 (versionCode 1030024): -10 points.
- Since the previous scan: 13 findings added, 10 removed.
- Version 1.3.24 (versionCode 1030024), score 42.
- Score 39 before, 42 after.
- Version 1.3.24 (versionCode 1030024), score 39.
- Score 30 before, 39 after.
- Version 1.1.40 before, 1.3.24 (versionCode 1030024) after.
- Version 1.1.40, score 30.
- First public scan of this app.
Method and limits
Static analysis: the decompiled code, manifest and resources of this build, read file by file. Network traffic at run time is established by a capture of the running app.
- Build SHA-256
- 636781e5cb196611e602252fd5774025db9626cd5b237a6e74c34e8e66f38fe7
- Rule pack
- citt-ruleset-2026-08-v1
- Files decompiled
- 29,733
- Scan date
- 14 August 2026
Corrections
No correction is published for this app.
Developer response
No response is published for this app.
Report an error Opens an email to [email protected] that names this app and this scan.