Help Center

Expected behavior

Understand trusted devices, single-active-device sessions, offline work, application lock, Trash and lapsed access in SovaSpace.

Devices and sessions

SovaSpace uses trusted-device records and signs in one device at a time. Opening the app on another device ends the previous session, and it stays ended — that device does not quietly resume in the background. Two reasons: a machine left unlocked in an office is still a trusted device, and two devices editing the same Entry produce conflicts that no merge resolves correctly. It is an account-control measure, not a promise that every locally cached byte is erased remotely the instant another device becomes active; the earlier device’s data stays encrypted on that device until it is opened again or removed.

Use recognizable device names, review unexpected session messages and contact support if a device you do not recognize appears.

Offline work

Locally available Standard Space content is intended to open offline. Actions that require authentication, a Drive object not yet on the device, subscription verification, device changes or Secret Space preflight may wait for connectivity. Pending durable tasks resume when their requirements return.

Application lock

The app lock covers the SovaSpace interface and clears sensitive state at defined boundaries. On supported Windows configurations, Standard Space can restore a trusted session using operating-system-protected secure storage. Treat Windows account security, disk protection and physical control as part of the security model.

Trash

Deleting an Entry normally moves it to Trash before permanent deletion. Restore it from Trash while it remains available. Permanent deletion is intentionally harder to reverse and can propagate to encrypted cloud objects.

Trial or subscription ends

The trial begins with the first Entry, lasts 7 days and allows up to 14 active Entries. When a trial or paid entitlement lapses, SovaSpace restricts creation and modification actions tied to paid access. Existing work is not intentionally blocked from viewing, export or sync solely because payment ended. Platform, authorization and local-availability requirements still apply.