Uncontrolled application telemetry
Vault applies deny, redact or app-scoped policy values instead of exposing unrestricted device identifiers.
Device-validated prototype · September 2026
BharatDroid
with Vault.
A privacy-controlled mobile operating system prototype that places a policy boundary between applications and the device's network, identity, sensors and cryptographic services.
BHARATDROIDBD
Privacy control layerNothing Phone (1)Built in India
681smeasured windows
1,143packets examined
0unexpected public packets
152/152sensor attempts denied
0Google service packages
Architecture
Five exposure paths.
Five explicit controls.
The prototype is evaluated by observable controls and bounded test evidence—not by an unqualified “zero telemetry” claim.
Direct network leakage
A controlled network boundary blocks direct DNS, NTP and public egress in the measured test windows.
Sensor and hardware exposure
Camera, microphone, location, motion sensors and hardware interfaces are default-denied unless policy permits access.
Direct hardware-key access
Vault brokers isolated, non-exportable keys and rejects unrestricted hardware attestation paths.
Dependence on Google services
The tested installation contains no GMS, Google Play Services or Google-owned application payloads.
Boot + unlock demonstration
See the installed prototype start.
This short evidence composite uses the installed boot-animation frames and live locked/unlocked device captures.
Test evidence
Measured results, methods and limitations.
The 13-page report records packet, sensor, package and key-broker evidence from the current Nothing Phone (1) prototype.
Open the PDF report ↗