Purpose
A Secret Space is an optional, separately protected area for more sensitive Entries. It reduces accidental exposure through independent credentials, explicit unlock state and stricter behavior when SovaSpace loses focus. It does not replace operating-system security or physical control of the device.
Create and unlock
Use the Secret Space setup provided in the current app and follow its credential instructions exactly. Unlock only through the in-app flow. Do not send a Secret Space credential or recovery information to support; NURSOVA cannot usefully verify or recover a credential it never receives.
Behavior differences
| Capability | Standard Space | Secret Space |
|---|---|---|
| Daily offline work | Designed for locally available content. | May require stricter preflight or unlock conditions. |
| Links and backlinks | Links and backlinks can connect Standard Entries. | No backlinks across the protected boundary. |
| Background media | Allowed where the platform supports it. | Secret media does not continue as a normal background session. |
| Focus changes | Follows normal application-lock policy. | Uses stricter key and visibility handling. |
Credentials and recovery
Choose a credential you can protect and remember. A neutral reminder should not reveal the secret itself. Save and test the Recovery Key path; the current design also provides a protected delayed reset when no Recovery Key is available. Support still cannot retrieve the original password or bypass correctly applied encryption.
Safe use
- Lock the operating-system account when leaving the device.
- Keep screen capture, clipboard and exported plaintext risks in mind.
- Do not assume a Secret Space hides account, device, timing or object-size metadata.
- Maintain an independent encrypted recovery copy for important material.
- Verify the destination carefully before moving an Entry between spaces.