05 Data collection by app
In brief: Each app collects only what it functionally needs. Here you can see endpoints, collected data, and purpose in detail.
Below is a transparent overview of all our apps, their specific data collection practices, the respective endpoints, their purpose, and the restricted permissions involved.
1) Firewall AI & DNS Changer
Note for both apps: Firewall AI and DNS Changer route the traffic of allowed connections directly through the Android VPN service to its destination — without an external VPN server.
Operating modes
- IP filtering disabled: All blocked internet traffic is routed into the local VPN service and discarded there (sinkhole).
- IP filtering enabled: Both blocked and allowed traffic is routed into the local VPN service, but only allowed traffic is forwarded to the destination. No traffic is sent to a remote VPN server.
The Android VPNService is used to route all internet traffic locally to Firewall AI. This means no root access is required.
Data collection & use
- Endpoint:
https://api.protectstar.com/api/get-blocklists-info
Data collected: App package name
Purpose: Download current filter blocklists. - Endpoint:
https://api.protectstar.com/api/whois
Data collected: The IP address or domain selected by the user in the WhoIs view, as well as derived technical network and Geo-IP information. No GPS location of your device is transferred. We do not collect complete browser history, permanently stored domain histories, or browsing profiles.
Purpose: Provide WhoIs and Geo-IP information for an IP address or domain selected by the user. - Endpoint:
https://tile.openstreetmap.org (third party)
Data collected: When map tiles are requested, OpenStreetMap technically receives at least your IP address and a User-Agent that identifies the app (app package name, app version, developer email).
Purpose: Load map tiles for the WhoIs display. We use this feature exclusively for map display and not for profiling.
Restricted permissions
android.permission.READ_PHONE_STATE (required, except DNS Changer) — read-only access to phone status, including cellular network information. android.permission.QUERY_ALL_PACKAGES (required) — lists installed apps to control app blocking in the firewall. - VPNService — routes network traffic locally through the app for security reasons.
2) Anti Spy & Antivirus AI
Data collection & use
- Endpoint:
https://api.protectstar.com/api/get-deep-detective-packages-shas-info
Data collected: SHA-256, MD5, package name
Purpose: Identify potential security threats during manual and real-time scans. - Endpoint:
https://api.protectstar.com/api/add-statistic-item, https://api.protectstar.com/api/add-file-statistic-item
Data collected: SHA-256, MD5, package name, file path/name, installation source, app version/code, device metadata (OS version, manufacturer, model), in each case only to the extent required for security analysis and threat assessment.
Purpose: Analyze detected threats and create aggregated security statistics.
Note on threat statistics: Only aggregated or anonymized security information is stored permanently; it does not contain file paths, file names, or device-related identifiers. File paths and file names, where required for security analysis, are processed only briefly and are not stored in permanent threat aggregates.
Restricted permissions
android.permission.SCHEDULE_EXACT_ALARM (optional) — enables scan times to be scheduled. android.permission.QUERY_ALL_PACKAGES (required) — scans installed apps for threats. android.permission.SYSTEM_ALERT_WINDOW (optional) — protection against screen-capture malware. android.permission.PACKAGE_USAGE_STATS (optional) — detects foreground apps to activate the Screen Protector. MANAGE_EXTERNAL_STORAGE, READ_EXTERNAL_STORAGE, WRITE_EXTERNAL_STORAGE (required) — scans and manages files for threats. All Files Access is a core feature: restricted APIs such as SAF or MediaStore cannot check all relevant file areas of a device for malicious code.
3) Camera Guard & Micro Guard
Camera Guard and Micro Guard monitor locally on your device whether camera or microphone access occurs, and warn you about unwanted access.
What we do not collect
We do not record photos, videos, audio data, conversations, or any other camera/microphone content, and we do not transfer such content to Protectstar. Detection runs exclusively locally through Android permission and usage APIs.
What may be processed
If app or device metadata is processed for notifications, licensing, MY.PROTECTSTAR, or support features, the information described above under Firebase Messaging and MY.PROTECTSTAR applies.
Restricted permissions
android.permission.SYSTEM_ALERT_WINDOW (required) — displays the protection warning over other apps. android.permission.PACKAGE_USAGE_STATS (optional) — detects the foreground app to correctly attribute the triggering access.
4) iShredder Android
The core “secure deletion” feature runs locally on your device. The contents of deleted files, folders, or contacts are not transferred to Protectstar. Personal data is transferred to Protectstar only for optional online features such as MY.PROTECTSTAR, license or purchase verification, in-app purchases, or support.
Restricted permissions
MANAGE_EXTERNAL_STORAGE, READ_EXTERNAL_STORAGE, WRITE_EXTERNAL_STORAGE (required) — reads and writes the bytes of files for secure overwriting. All Files Access is a core feature: secure deletion requires byte-level access that cannot be reliably provided through SAF or MediaStore. READ_CONTACTS, WRITE_CONTACTS (optional) — securely deletes contacts on your device.
Shared feature in all apps: In-app purchases
Data collected: Purchase history — the history of in-app purchases (only in the respective app).
Apps with MY.PROTECTSTAR account integration (optional)
Included apps: Anti Spy, Antivirus AI, Firewall AI, DNS Changer, iShredder, Micro Guard
Endpoint: https://my-api.protectstar.com
Data collected
- User data: User ID, email address, last name, first name, and authentication data. If you use a password, we store no plaintext password. Instead, we store only an iterative PBKDF2-HMAC-SHA256 hash with a random salt that is unique for each password.
- Device type: user-defined device name (for example, “Peter’s Samsung Galaxy S23”), manufacturer, model, industrial design name, board, hardware specifications.
- Product SKU: the app’s own package.
- License information: activation ID, activation key.
Apps with Firebase Messaging integration
Included apps: Anti Spy, Antivirus AI, Firewall AI, DNS Changer, Camera Guard, Micro Guard
Data collected
- Device metadata: OS version, name, model, brand, form factor.
- Installation source: identifies the app used for installation (for example, Play Store).
- App version: collected to manage topic subscriptions.
Purpose: developer communication and app updates.
Settings: Collection and use of analytics data is permanently disabled — in accordance with the Firebase documentation.
The data we collect is used not only for threat detection, but also to tailor our security measures to your device environment. This gives you the most effective protection against evolving digital threats.
06 Firebase Messaging and privacy
In brief: We use Firebase Cloud Messaging solely for the technical delivery of push notifications. No tracking, no analytics, no advertising — but technical delivery data such as FCM tokens is technically necessary.
We use Firebase Cloud Messaging (FCM) solely for the technical delivery of push notifications and for managing topic subscriptions (for example, update notices or threat alerts).
In this context, technical identifiers and metadata may be processed where required for push delivery:
- FCM token or Firebase installation ID — addresses your device as the recipient of a push message.
- App version — used to correctly manage topic subscriptions.
- Firebase User-Agent & device metadata — OS version, model, brand, form factor, installation source. Processed by Google/Firebase for delivery logic.
We do not use Firebase Cloud Messaging for advertising, profiling, app activity tracking, or behavioral analysis. Firebase Analytics and Firebase Crashlytics are not enabled or not integrated in the apps listed — in accordance with the Firebase documentation.
More about data processing by Firebase Cloud Messaging: firebase.google.com/docs/android/play-data-disclosure