How your workspace is isolated

Each account owns exactly one workspace row, keyed to your authenticated user id with a uniqueness constraint. Row-level security policies allow reading, creating, updating and deleting only where that id matches the caller. Signed-out visitors have no access to the table at all.

Every server call that touches your workspace validates your session token first and then queries as you, so the same policies apply on the server as in the browser.

Each save carries the version number the client last read. If the stored version has moved on — another tab, another device — the write is refused and you get an explicit conflict notice with the option to reload the newer copy. A conflicting write never silently overwrites the server copy.

A failed save is reported as a failed save. There is no optimistic interface that shows your change as accepted while the write is being rejected in the background.

Email and password sign-in, with registration open so the product stands on its own. Sessions live in your browser and are validated server-side on every private request. Signing out cancels in-flight requests and clears cached workspace data from the tab.

If you find a way to read or write a workspace that is not yours, report it before using it. Security reports are treated as the highest-priority class of issue.