Recovery Key
A distinct path for regaining authorized access.
Q‑Tel is designed around purpose-specific keys, local authorization and recoverability—without treating one credential as the answer to every risk.
A distinct path for regaining authorized access.
Binds an authorized Q‑Tel identity context to a device.
Reserved for explicit, sensitive action authorization.
Purpose-specific protection for conversations and calls.
A separately governed root for protected vault access.
Key architecture
A distinct path for regaining authorized access.
Binds an authorized Q‑Tel identity context to a device.
Reserved for explicit, sensitive action authorization.
Purpose-specific protection for conversations and calls.
A separately governed root for protected vault access.
Device foundation
On iOS, Q‑Tel uses Secure Enclave capabilities. On Android, it uses Keystore and StrongBox where device support is available.
Biometrics can be optional for ordinary use and required by policy for selected sensitive actions.
Your own Q‑Tel code can lock the app in addition to the device passcode.
Raw biometric data is not sent to Q‑Tel; operating-system authorization supplies the result.
Different actions can require different levels of local review and authorization.
Recovery
Q‑Tel's recovery is separated from device identity, communication, verified action and vault key responsibilities.
Establish recovery authority
Review device change
Restore eligible access
Re-establish separated keys
Discuss the Q‑Tel trust model, device policies and integration direction.
Request a security conversation