Cookie Policy
Effective date: November 12, 2026
zvena uses only cookies and browser storage that are strictly necessary to sign you in, keep your settings and make the editor work. There are no analytics, advertising or tracking cookies, so there is nothing to opt in or out of, and no consent banner beyond a short notice. An embed someone adds to a page (such as a video or a map), or a picture linked from another site, loads from that site, which may set its own cookies under its own policy.
1. Cookies set by zvena
| Name | Purpose | Duration |
|---|---|---|
__Host-zv_s | Keeps you signed in, also to a trial account made by “Try it now”, which only this cookie opens. Not readable by page scripts (HttpOnly) and sent only over HTTPS. | 30 days, renewed while you use zvena; removed when you sign out |
auth-token (Design) | Keeps you signed in to Design, on its own subdomain. HttpOnly. | 7 days, renewed while you use Design; removed when you sign out |
zv-share-… (Design) | Remembers that you entered the password of a password-protected design link. HttpOnly. | 7 days |
zv_g | A random guest id, so files you upload without an account stay yours and move into your account when you sign in | Up to 400 days, renewed when you visit; removed when you sign in. Guest files are deleted 30 days after upload |
zv_lang | Your interface language (also read by Design on zvena’s own subdomain) | 400 days |
zv_theme | Only once you pick a light or dark theme in Settings: that theme, so Design on zvena’s own subdomain opens in it too | 400 days; removed when you go back to the system theme |
zv_ws | The workspace you had open last | 400 days |
zv_oauth | Set only while you sign in with Google or GitHub: ties the provider’s answer to the browser that started the sign-in, so nobody can sign you in to their account with a link (HttpOnly) | 10 minutes, removed when the sign-in finishes |
zv_sso | Set only while you sign in with your organization’s single sign-on: ties the answer of the identity provider to the browser that started the sign-in (HttpOnly) | 10 minutes, removed when the sign-in finishes |
2. Signing in with Google or GitHub
The sign-in page loads nothing from Google or GitHub. “Continue with Google” and “Continue with GitHub” take you to their own sign-in page, where their cookies and policies apply (Google, GitHub).
3. Browser storage
- localStorage
zvena-settings— theme and editor settings;nt-*— Docs panel layout, views and editor preferences;pj:*— Projects view preferences;zvena-search-recent— your recent searches;zvena-desktop-links— whether links open in the zvena desktop app, if you use it;zv-cookie-ok— that you have seen the cookie notice;zv.rail.folds— which sidebar sections you folded;zvena-device-copies— which offline copies of Calendar, Mail and Projects this device keeps, for browsers that cannot list them, so signing out removes them all. - sessionStorage
zv-tz— that your time zone was sent to our server (used for dates and reminders);zvena-stay-in-browser— that you chose to stay in the browser instead of opening the app;zv-lang-shared— that your language choice was passed on to Design. They go when you close the tab. - IndexedDB
zvena-docs,zvena-docs-…— a local copy of each workspace’s documents you opened (one database per workspace), with their edit history for merging, so they open instantly and keep working offline; edits made offline are sent when the connection is back. If you use Docs without an account, this is the only copy of your documents. Signing out keeps only edits that have not reached our server yet, for your next sign-in. - IndexedDB
zvena-offline-…— changes made without a connection that wait to be sent (for example a file added offline or an Inbox item marked read), and the last Inbox you saw, so it reads offline. Kept per account; sent and removed when the connection is back. - localStorage
zvena-docs-stores,zvena-y-unsaved:…— which workspaces have a local copy (so signing out can clear them all), and edits not yet written to IndexedDB when a tab closed (taken by the next visit). - Offline cache (Cache Storage) — zvena’s own program files, and the app pages and pictures you opened, kept per account so they open without a connection. Pages are never shown to another account, and signing out deletes them.
4. Your choices
You can delete cookies and site data in your browser settings at any time. If you delete the session cookie you will need to sign in again; if you delete guest data, documents you created without an account are lost. Because we only use strictly necessary cookies, blocking them may stop zvena from working.
More about how we handle personal data is in our Privacy Policy. Questions: support@zvena.app.