Security
Industry-leading security standards built into every device. Your data is always protected.
Hardened Malloc
Protection against heap corruption attacks via custom memory allocator. Active by default.
Sandbox Isolation
Each app runs in its own sandbox. Hardened with SELinux and seccomp-bpf.
Multiple Profile Support
Work and personal data in fully isolated profiles. No cross-profile data leakage.
Automatic Restart / BFU
A device not unlocked for a period auto-restarts into BFU (Before First Unlock) mode — the strongest encryption state.
Lock Screen Notification Hiding
Notifications show no content on the lock screen. Sensitive info is hidden.
Per-App Encryption
Each app can be protected with a separate PIN/fingerprint.
Scrambled PIN Keypad
PIN digits are in different positions each time. Shoulder-surfing protection.
USB Lockdown
While the device is locked, USB connection is fully disabled. Protection against forensic tools.
Lockdown Mode
When a threat is detected, cuts all connections and disables fingerprint.
Kill PIN
In an emergency, entering a special PIN fakes a normal boot but silently wipes all data.
Sensor Privacy
Camera, microphone and location sensors can be individually disabled.
Top 5 Differences
Titan M2 security chip
Special security operating system
No phone number required
Onion routing hides the IP address
Swiss privacy laws (FADP/GDPR)
Hardware and Software Security Features
Review your device's security layers in detail. Hardware-based protections and software-based encryption methods are listed separately.
Hardware Security Features
| Feature | Description |
|---|---|
| Titan M2 Security Chip | Dedicated security chip found in all Pixel 8/9/10 models. Physically protects encryption keys; even if the OS is fully compromised, the keys remain safe. |
| Verified Boot | OS and firmware integrity is cryptographically verified at every boot. Rollback protection prevents reverting to older/insecure versions. |
| Hardware-Based Encryption | UFS inline storage encryption (Pixel 9: Tensor G4, Pixel 10: Tensor G5). Data is encrypted at the hardware level. |
| Memory Tagging Extension (MTE) | ARMv9 hardware feature on Pixel 8 and later. Hardware-level protection against memory overflow and use-after-free attacks. |
| StrongBox (Secure Key Store) | Secure area running on the Titan M2. Payment apps and FIDO authentication keys are stored here. |
| 1-Year Update Guarantee | Minimum 1 year of security updates for Pixel 8/9/10 (Pixel 8: ~2030, Pixel 9: ~2031, Pixel 10: ~2032). |
Software Security Features
| Feature | Description |
|---|---|
| Hardened Malloc | Protection against heap corruption attacks via custom memory allocator. Active by default. |
| Sandbox Isolation | Each app runs in its own sandbox. Hardened with SELinux and seccomp-bpf. |
| Multiple Profile Support | Work and personal data in fully isolated profiles. No cross-profile data leakage. |
| Automatic Restart | A device not unlocked for a period auto-restarts into BFU (Before First Unlock) mode — the strongest encryption state. |
| Lock Screen Notification Hiding | Notifications show no content on the lock screen. Sensitive info is hidden. |
| Per-App Encryption | Each app can be protected with a separate PIN/fingerprint. |
| Scrambled PIN Keypad | PIN digits are in different positions each time. Shoulder-surfing protection. |
| USB Lockdown | While the device is locked, USB connection is fully disabled. Protection against forensic tools. |
| Lockdown Mode | When a threat is detected, cuts all connections and disables fingerprint. |
| Kill PIN | In an emergency, entering a special PIN fakes a normal boot but silently wipes all data. |
| Sensor Privacy | Camera, microphone and location sensors can be individually disabled. |
| 5G → LTE Forcing | 5G can be disabled for protection against rogue base stations (IMSI catcher). |
| Special Security Operating System | Security-focused special security operating system, a hardened Android distribution. |
Q-PWA Secure Messaging Features
| Feature | Description |
|---|---|
| Secure encryption (E2EE) | Messages are encrypted between sender and receiver devices. Servers cannot see the content. |
| No Central Server | Messages are not stored on a central server. Distributed network architecture. |
| No Phone Number Required | No phone number or email requested for registration. Anonymous account creation. |
| Onion Routing | Messages are routed via 3 nodes with onion routing. IP address is hidden. |
| Metadata Protection | Who messaged whom and when is not collected. |
| Swiss Privacy Law Compliance | Operated under FADP and GDPR. |
Session Messaging Features
| Feature | Description |
|---|---|
| Secure encryption (E2EE) | 1-1 messages are encrypted with Secure encryption (E2EE). |
| No Central Server | Distributed network called Session Nodes. No single entity can read or censor traffic. |
| No Phone Number Required | No personal info requested for registration. Identity via Secure identity authentication. |
| Onion Routing | 3-hop onion routing hides the IP address. No node knows both sender and receiver. |
| Forward Secrecy | Rotating keys with Forward Secrecy. Even if the device is compromised, old messages cannot be decrypted. |
| Open Source | Fully open source, independently auditable. |
Security Standards
QMOBILE devices are built on Google Pixel 8/9/10 hardware. Hardware security is provided by the Titan M2 chip and verified boot. Software security is provided by a special security operating system. Messaging security is provided by Secure encryption (E2EE) for messaging. Note: Hardware security features belong to Pixel devices. Software security features belong to the special security operating system. Messaging features are provided by the Q-PWA and Session apps. We have no official affiliation with Google. The entire system complies with Swiss privacy laws (FADP) and GDPR.