unlose Sign in

unlose docs · Operations

Hosted service boundaries

Learn what unlose.sh stores, how authentication works, and which responsibilities remain local.

View source as Markdown

What it stores

unlose.sh stores encrypted capsules in object storage and keeps account, routing, quota, login, and share metadata in a database. GitHub and Google provider access tokens are not kept as long-lived Unlose credentials.

Boundaries

  • Uploads go through the authenticated Unlose origin; storage credentials are never given to the client.
  • Hosted objects are bounded. Larger sessions can still move with unlose export and unlose import.
  • Account sessions and unclaimed share links can be revoked from the dashboard.
  • Key hosting and title hosting are separate, optional trust choices.

Not a repository backup

The hosted service does not back up your source repository. Keep project files in normal version control and a separate backup system.