DuressDecoy Security

In Sovereign, the server recognizes safeword authentication and hides marked sensitive Spaces for that session. The normal access path can reveal them again. In HighRisk, the corresponding LifeSafe response deletes marked sensitive Spaces instead.

Boundaries

The server applies the selected response; the client displays the resulting permitted view. This is not a separate decoy Safe, a silent alert, or a guarantee that a compromised endpoint cannot distinguish the two views. Prior access, retained plaintext, screenshots, and other copies remain outside this control.

Normal Safe authentication still requires the registered access key. A safeword PIN is not a substitute for that key. Users must configure both the safeword and the sensitive-Space selection before relying on the feature.

Shared Spaces

Sovereign's hiding response applies to the acting Safe's view. It does not remove other participants' access. In HighRisk, deleting an owned sensitive Space affects participants, while removing a non-owned Space from the acting Safe does not delete the owner's data. Neither response erases independently retained copies.

Choosing a mode

Use Sovereign when the marked content must remain available after normal access resumes. Choose HighRisk only when the permanent deletion of marked sensitive Spaces matches your needs. Keep independent backups of information whose loss you cannot accept.

See DuressDecoy, LifeSafe, and Sovereign vs. HighRisk.