02
What Laver keeps in your browser
All of it is local storage, not cookies, which means it stays on your device and is never sent automatically with a request the way a cookie is.
Signing in
token— your session, as a signed token. This is what keeps you logged in. Removing it signs you out.laver.pending_verification— set only between signing up and verifying your email, so the "resend" button knows where to send it. Cleared when the tab closes.
Unsent work
laver.offline-queue— edits you made while your connection was down, held until they can be sent. Only ordinary content edits are ever queued: never a password, never a payment, and never a deletion. Each entry is stamped with the account that made it and is only ever replayed for that account.laver:wiki-draft:…— a local draft of a wiki page you are editing, so closing the tab by accident does not lose it.
Remembering how you left things
dark_mode,laver.theme— light or dark, and which palette.current_workspace_uuid— the workspace you were last in.laver.sidebar-collapsed— whether the sidebar is collapsed.laver.board_scroll— where you were on a board, so returning to it does not jump to the top.laver.task-detail-mode,laver.task-detail.modal.geometry,laver.task-detail.panel.geometry,laver.task-detail.comments-open,laver.task-comments-width,laver.sprint-dialog.geometry,laver.wiki-history-dialog.geometry— the size, position and layout you last gave each panel and dialog.
None of the entries in that last group identifies you. They are interface preferences, and the worst that happens if you clear them is that windows go back to their default size.
03
How we count visits without a cookie
We do count page views on our public pages, and we do it without storing anything on your device. Each view records the path, the host of the referring site, a campaign source if the link carried one, and a hash.
The hash is built from the current date, a server-side secret, your IP address and your browser's user-agent. It lets us see two views on the same day as one browser; it changes at midnight, so views on different days cannot be joined, and it cannot be turned back into an IP address. There is no third-party analytics service involved. Our Privacy Policy covers this in more detail.
04
Other people's cookies
When you pay for a subscription you are sent to Stripe's own checkout to enter your card details. Stripe sets its own cookies there, under its own policy, to process the payment and prevent fraud. That happens on Stripe's pages, not ours.
Links out of Laver — to documentation you have written, or a site somebody has referenced in a ticket — go to sites with their own rules. We have no control over those.
05
Clearing it
Your browser's "clear site data" for laver.app removes everything above. You will be signed out, the interface returns
to its defaults, and any edits still waiting in the offline queue
are lost — so reconnect and let them send before you clear it.
Signing out clears your session and cached data but deliberately keeps unsent offline edits, because they are your work and signing out is not a reason to bin it. They are stamped with your account and will not be replayed for anyone else.
Blocking local storage entirely will stop Laver working: there would be nowhere to keep your session, so you could not stay signed in.
06
Changes, and how to reach us
If this changes — particularly if we ever introduce anything that would need your consent — we will update the effective date above and say so plainly before it takes effect.
Developyn Ltd, 42 Kittiwake Drive, Brierley Hill, DY5 2QJ. support@developyn.com.