Privacy

Draft

For Product Owner review. Not approved; no effective date has been set. This describes the reviewed source snapshot and available testing boundaries, not legal commitments for a finished release.

1. Scope

NetScope is a WABISC Android application. This draft separately covers local DNS processing, external requests, history, diagnostics and the website. A public APK has not been published.

2. DNS and external services

Domain rules are applied on the device. A blocked query receives a local response; an allowed DNS query is sent to Cloudflare over HTTPS. Not all processed data therefore stays on the device.

Updating rules contacts AdAway over HTTPS. In the experimental proxy scenario, the selected external provider participates in TCP transfer. Their own processing and retention policies require separate review.

3. History and preferences

The local SQLite database stores domains, timestamps, categories, blocking decisions, rule sources and app information when identified: UID, package and label. Policies, allowed domains and preferences are also stored; experimental builds retain routing configuration.

The history target is 50,000 events. Pruning runs when the database opens and periodically after inserts, so the count can temporarily exceed that threshold. There is no fixed retention period in days. History can be cleared in settings while rules and preferences remain.

4. Diagnostic files

Single-app inspection and experimental routing may record a diagnostic session in the app cache. Metadata includes app version and build type, Android, device model, network type, a carrier in some scenarios, the selected app and event times.

Export applies redaction to domains, IP addresses, URLs and sensitive fields. This is not a promise of file anonymity. Scheduled pruning retains up to three stored sessions, each bounded to 2,000 events. Copies already shared with a recipient are not deleted by this mechanism.

5. Sharing diagnostics and system logs

Users share diagnostic files through the Android system chooser and select the recipient. No automatic uploader of these files to a WABISC server was found in the reviewed code. Review the content before sharing.

The app writes operational messages to Android logcat, with additional network messages in Debug. It would be inaccurate to claim there are no logs.

6. Analytics and telemetry

No analytics SDK, Crashlytics/Sentry or WABISC telemetry collection service was found in the reviewed dependencies and main source. Activity figures in the interface are calculated locally. This is a source audit, not a complete network audit of a distributed APK and every native component.

7. Android permissions

The manifest declares internet and network-state access, foreground service and its special-use type, and notifications. Android VPN consent is requested separately. BIND_VPN_SERVICE protects the VPN service; it is not a separate user permission prompt.

App visibility is limited to launcher apps; QUERY_ALL_PACKAGES is not declared. The manifest sets allowBackup=false. This does not guarantee that no system or exported copies exist.

8. Website data

The website stores your theme preference locally in the browser. It currently has no analytics, submission forms or server-side diagnostic uploads. Fonts and images are hosted with the site. Future hosting-log policies have not been set.

9. Items requiring approval

Before publication, the owner must confirm the legal operator and contact, final APK and dependency inventory, processing purposes and rules, hosting retention, how user requests are handled and the effective date. This draft does not replace that review.