Security Core

Security through separation.

Qtel is designed around purpose-specific keys, local authorization and recoverability—without treating one credential as the answer to every risk.

Recovery Key

A distinct path for regaining authorized access.

Device Identity Key

Binds an authorized Qtel identity context to a device.

Verified Action Key

Reserved for explicit, sensitive action authorization.

Communication Keys

Purpose-specific protection for conversations and calls.

Vault Master Key

A separately governed root for protected vault access.

Key architecture

Five responsibilities. Five distinct trust boundaries.

Recovery Key

A distinct path for regaining authorized access.

Device Identity Key

Binds an authorized Qtel identity context to a device.

Verified Action Key

Reserved for explicit, sensitive action authorization.

Communication Keys

Purpose-specific protection for conversations and calls.

Vault Master Key

A separately governed root for protected vault access.

Device foundation

Use the strongest device capability available.

On iOS, Qtel can be designed to use Secure Enclave capabilities. On Android, it can use Keystore and StrongBox where device support is available.

Hardware-backed behavior varies by device, operating system and implementation. Qtel should verify capability at runtime rather than imply universal support.

Optional biometrics

Biometrics can be optional for ordinary use and required by policy for selected sensitive actions.

Optional local code

A local code can provide another device-side authorization choice.

No raw biometric upload

Raw biometric data is not intended to be sent to Qtel; operating-system authorization supplies the result.

Policy by action

Different actions can require different levels of local review and authorization.

Recovery

Recovery should restore access—not collapse every key boundary.

Qtel's recovery direction separates the recovery role from device identity, communication, verified action and vault key responsibilities.

01

Establish recovery authority

02

Review device change

03

Restore eligible access

04

Re-establish separated keys

Qtel platform

Security is a system design choice.

Discuss the Qtel trust model, device policies and integration direction.

Request a security conversation