Privacy & Data Handling Architecture
Voodoo Hardware Info is designed from the source code up as an on-demand, local hardware diagnostic utility. We believe technical credibility requires honest, precise explanations of data collection boundaries rather than vague marketing promises.
Core Governance Principles
All 18 hardware categories are inspected entirely in-process on your device. The app operates completely without an internet connection for local discovery.
Your device report, hardware identifiers, and system parameters are never automatically transmitted to any remote server or third-party telemetry platform.
You do not need to register, provide an email address, or create a profile. There are no paywalls, subscriptions, or login gates.
Important Distinction: Hardware Report Privacy vs. Advertising SDKs
We do not claim Voodoo Hardware Info is "ad-free." Advertising may be integrated into future consumer builds to support ongoing engineering and physical device testing. However, we maintain an absolute architectural separation:
- Your hardware report data is isolated: Sensor readings, partition sizes, SoC characteristics, and exported JSON files are never passed to advertising SDKs.
- Standard Ad Network Data: Any future ad network SDK will only collect its standard network-level identifiers (such as Google Advertising ID and IP address for ad serving) subject to Google Play policies.
- No False Claims: We will never falsely promise "zero network activity under all conditions" or "zero third-party SDKs" when ad SDKs are active.
Why Permissions Are Requested
Voodoo Hardware Info requests only the minimum permissions necessary to query hardware subsystems. In accordance with our non-invasive philosophy, all sensitive permissions are optional; the app will continue to inspect all other categories cleanly if a permission is denied.
| Permission | Affected Category | Technical Rationale | If Denied |
|---|---|---|---|
| ACCESS_FINE_LOCATION | Wi-Fi & GNSS | On Android 8.0+, the OS requires location permission to read Wi-Fi SSID/BSSID and active GNSS satellite status. | Field marked PERMISSION_DENIED; basic connection state still displayed. |
| BLUETOOTH_CONNECT / SCAN | Bluetooth | Required on Android 12+ (API 31+) to query Bluetooth adapter state and bonded device names. | Field marked PERMISSION_DENIED; adapter feature flags still reported. |
| CAMERA | Camera (Legacy Only) | Camera2 static characteristics require no CAMERA permission. Legacy Android 2.3–4.4 requires brief camera instantiation. | Modern Android queries CameraManager directly without opening a camera stream. |
Future Online Enrichment Philosophy
Planned future updates (Phase 10) may introduce optional online hardware enrichment (e.g. looking up a commercial SoC marketing name or camera sensor model from a community database). When implemented:
- Explicit User Action: Online lookup will only occur when you explicitly tap a button to request enrichment.
- Minimal Payload: Only the specific hardware identifiers required for lookup (e.g.,
ro.board.platformor camera sensor dimensions) will be transmitted—never full device reports, serials, or MAC addresses. - Offline Fallback: If network connectivity is unavailable, the app will continue to display local OS and kernel values without interruption.