A Theta device is a Google Pixel 8, 9, 10, or 11 running ThetaSecurity OS, so that the usual paths into a handset fail closed and attempts on the rest are detected and reported. It is for people whose conversations, location, and contact graph are already treated as sensitive. It is not a consumer skin on an ordinary phone.
What the build is aimed at
- Commercial spywareOne-click and zero-click implants in the class of Pegasus and Predator depend on memory corruption, then on persistence that survives reboot. Memory tagging and an intact verified-boot chain are the controls for that class.
- Carrier correlationA cellular network can see a radio and an identifier. It should not see readable signaling, call audio, or an application identity that matches a legal name.
- IMSI catchersA nearby false base station can still observe that a radio exists. The session it is not supposed to obtain is the encrypted path in front of the baseband.
- Account linkageA vendor account, a cloud backup, and telemetry weld a hardware key to a person. The build does not require them, and it does not ship them.
- Forensic seizureExtraction tools sweep storage. Canary files trip a silent lock when they are touched, and the vault keeps its contents sealed.
- Operator mistakesUnknown networks, sideloaded apps, and files that carry a location. Theta Sentinel warns before they become leaks.
What remains outside the device
Physical seizure of an unlocked screen, a passphrase given up under pressure, a SIM registered to a real identity, and an application the operator installs later are not defeated by silicon. Those are covered in the safety rules. A future bug that has not been modeled is not something this page can pre-defeat. The guarantee is the set of controls on the build we hand over, kept intact by the way the device is used.
Read the safety rules before the handset is used for a real conversation. Most leaks from a careful device are operator actions, not a failure of the boot chain.