Software-defined trust anchor
The device that unlocks trust.
Phantom Key is the physical access anchor for the Phantom ecosystem.
It binds vault access to a trusted USB device, creating a real-world boundary around sensitive data. Without the trusted device present, protected vaults stay sealed. Remove the key, and the access path closes.
Access model
Keyfile + Key + Vault.
Keyfile
+
Trusted USB Key (GUID/ID Bound)
+
Encrypted Vault Policy
=
Access Granted
Physical possession becomes part of the security boundary.
Why it exists
Software credentials alone are not enough.
- Cloud trust is not the same as user control — many products rely on accounts, remote systems, and always-on infrastructure, expanding the trust surface.
- Phantom Key narrows the boundary — it introduces a possession requirement so access depends on a device the user physically controls.
- Security becomes tangible — instead of trust living only in software, part of the access model lives in the user's hand.
Core capabilities
Built as the suite-wide trust anchor.
- Device-bound vault unlocking
- Presence-aware session control
- Ecosystem-wide security role across Obscura, Attestor, Recovery, and future Phantom applications
Where it fits
One trusted device. Multiple security layers.
- Phantom Obscura — device-gated access for credentials, files, notes, and private vault data.
- Phantom Attestor — controlled access to authentication assets, TOTP secrets, and identity material.
- Phantom Recovery — protected continuity and recovery artifacts guarded by possession-based access.
Future direction
The software-defined security layer will keep expanding.
- Deeper device policy — future versions can expand how trusted devices participate in access rules, validation, and session enforcement.
- Broader trust workflows — Phantom Key is positioned to become the physical trust boundary across the wider Phantom ecosystem.
- Clearer security story — the goal is simple: digital security with a physical boundary.
Security should require possession.
Join early access for Phantom Key and follow the development of device-bound security across the Phantom ecosystem.