Cookie & Local Storage Policy
v1.4 · 2026-11-11
1. Scope and Legal Status of This Policy
This Cookie & Local Storage Policy (the "Policy") explains how Mozen ("Mozen," "we," or "the Service") sets, reads, writes to, and accesses Cookies and browser local storage and caching technologies including localStorage, sessionStorage, and IndexedDB (collectively, "storage technologies") on your device when you access, register for, or use the Mozen website, web application, desktop or mobile applications, AI features, whiteboard, documents, reader, resource library, sharing and public pages, and related services.
This Policy forms part of, and is a specific supplement to, Mozen's Privacy Policy. It is consistent with the "Cookies, Local Storage, and Offline Cache" section of the Privacy Policy; where this Policy provides more detailed technical explanation, this Policy governs the technical details; where the overall principles of personal data processing, your data rights, or dispute resolution are concerned, the Privacy Policy and Terms of Service govern. Terms not separately defined here have the meanings given in the Terms of Service and Privacy Policy.
Mozen is a service brand operated by MOZEN LABS LLC, a Wyoming limited liability company. Its corporate contact and service-of-process address is 30 N Gould St, Sheridan, WY 82801, United States. For privacy requests, contact [email protected]; for legal notices, contact [email protected]; support and billing contacts are listed in this document.
2. Applicable Legal Framework
Within its scope, this Policy follows the legal frameworks below, subject in each case to the mandatory provisions of the relevant jurisdiction:
- Article 5(3) of the EU ePrivacy Directive and national implementing laws: sets the rules for storing information on, or accessing information already stored in, a user's terminal equipment, including Cookies as well as any form of local storage and access such as localStorage, sessionStorage, and IndexedDB. Except for the "strictly necessary" exemption, any such storage or access requires your prior, informed, freely given consent after clear and complete information is provided.
- Article 7 of the EU General Data Protection Regulation (GDPR) and UK GDPR: sets the standards for valid consent (freely given, specific, informed, unambiguous, demonstrable, and withdrawable as easily as it was given). Where storage technologies involve the processing of personal data, that processing is also subject to the GDPR / UK GDPR.
- Other applicable laws: including, without limitation, U.S. state privacy laws (such as the "sale/share" opt-out and recognized-browser-signal obligations under the California CCPA/CPRA), China's Personal Information Protection Law, and other data protection and electronic communications laws of your jurisdiction.
The term "strictly necessary / necessary" in this Policy is construed by reference to the exemption in Article 5(3) of the ePrivacy Directive, meaning only those storage technologies absolutely necessary to provide a service you have actively requested, and does not include analytics, attribution, or advertising purposes.
3. What Cookies and Local Storage Technologies Are
To help you make an informed decision, the principal technologies covered by this Policy are as follows:
- Cookies: small text files set by a website in your browser and returned on subsequent requests. By duration they are session cookies (expire when the browser closes) or persistent cookies (retained until a set expiry); by setter they are first-party (set by mozen.ai and its subdomains) or third-party (set by another domain).
- localStorage: browser key-value persistent storage with no built-in expiry, retained across sessions until cleared by code, by you, or by the browser. Mozen uses it for interface preferences and certain session credentials (see the key table).
- sessionStorage: key-value storage similar to localStorage but valid only within the current tab session and cleared when the tab closes.
- IndexedDB: a structured in-browser database used to persist larger data. Mozen primarily uses it to store local Y.Doc copies of documents and whiteboards, the offline edit queue, media Blob caches, and dictionary shards, to support offline use, recovery after network loss, and fast opening.
- HTTP cache, Service Worker cache, and similar mechanisms: caches of static assets, modules, and resource files used by the browser and the application to improve load speed.
Regardless of the name of the above technologies, where they constitute "storing information on, or accessing information already stored in, your terminal equipment," they fall within the consent/exemption rules of Article 5(3) of the ePrivacy Directive, and this Policy applies to them uniformly — this Policy is not limited to Cookies.
4. Categories in Which We Use Storage Technologies
Regional scope: the prior-consent rules in this policy apply to users visiting from the European Economic Area, the United Kingdom and Switzerland (determined by the IP address at the time of the visit; if it cannot be determined, these rules apply as well). In other regions, preference and analytics storage is enabled by default and you can turn it off at any time in Settings → Privacy, Security & Permissions. When your browser sends a DNT or GPC signal, we do not enable analytics in any region.
We categorize storage technologies by purpose into the following three categories, applying a different legal basis to each:
- (A) Strictly necessary (no consent required): absolutely necessary to provide a service you have actively requested, including the authentication session, CSRF and security state, Y.Doc local persistence, offline editing cache, current-workspace memory, upload and error recovery, and load and availability safeguards. This category is exempt under Article 5(3) of the ePrivacy Directive and requires no prior consent; where personal data is involved, the basis is performance of a contract or our legitimate interest in providing and securing the Service. Disabling this category may prevent the Service from functioning properly.
- (B) Preference (subject to your choice): remembering theme (light/dark), interface language, layout, panel and tool preferences, and recently used items, to restore your settings on your next visit. In jurisdictions where consent is required, we set these only when you write or adjust the corresponding preference (i.e., you actively request that the preference be remembered), and you can clear them at any time via in-app controls or your browser.
- (C) Analytics and attribution (explicit prior consent required): the visitor identifier (client_id), session metrics, and source attribution (UTM parameters) used by our first-party, self-built site analytics. This category is set or written only after you give explicit, affirmative consent via the consent banner or preference center; before you consent, we do not set this category for analytics purposes or read the relevant identifiers. You may withdraw consent at any time.
We currently do not serve advertising cookies, do not use third-party cross-site tracking SDKs, do not engage in cross-context behavioral advertising, and do not sell or "share" for targeted-advertising purposes any identifiers obtained from storage technologies. If we introduce such uses in the future, we will update this Policy, place them in a category requiring prior consent, and provide corresponding opt-out and withdrawal mechanisms.
5. Named Key Table (Cookie and Local Storage Inventory)
The table below lists the principal storage items Mozen may set or write during normal use. Key names may change due to version iteration, third-party service updates, or security-policy adjustments; the table is a representative inventory reflecting each item's category, purpose, duration, and setter, but does not constitute an exhaustive commitment as to every specific key name.
(A) Strictly necessary
- Refresh token cookie (httpOnly cookie, name such as
mz_rt/mz_rt_admin) | Category: necessary | Purpose: store the refresh token in a secure httpOnly, SameSite=Strict cookie to renew the session and resist XSS theft | Duration: persistent within the session-renewal period | First-party. - CSRF / security state (cookie / sessionStorage) | Category: necessary | Purpose: cross-site request forgery protection, Origin validation, and login-flow security | Duration: session | First-party.
- Current workspace and interface state (localStorage) | Category: necessary | Purpose: remember the current workspace and prevent loss of context after refresh | Duration: persistent, until you switch or clear | First-party.
- Y.Doc local persistence (IndexedDB, y-indexeddb library) | Category: necessary | Purpose: a local CRDT copy of document and whiteboard content, supporting offline editing, recovery after network loss, cross-tab sync, and fast opening | Duration: persistent, until the document is deleted or you clear it | First-party.
- Offline edit queue and upload recovery (IndexedDB / localStorage) | Category: necessary | Purpose: cache unsynchronized edits and upload tasks to resume after the network recovers and prevent data loss | Duration: persistent, until successfully synced or cleared | First-party.
- Media Blob and dictionary-shard cache (IndexedDB) | Category: necessary/performance | Purpose: cache media and read-only static data for offline availability and to reduce repeated requests | Duration: persistent, managed by cache policy | First-party.
(B) Preference
- Interface language (localStorage,
i18nextLng) | Category: preference | Purpose: remember your chosen interface language (zh/en/ja/de/fr/es/pt-BR/ko/zh-Hant) | Duration: persistent, until you change or clear | First-party. - Theme (light/dark) and layout preferences (localStorage) | Category: preference | Purpose: remember light/dark mode, panel layout, and tool and view preferences | Duration: persistent | First-party.
- Recently used items / experience optimization (localStorage / sessionStorage) | Category: preference | Purpose: restore recently opened items, onboarding progress, and similar non-essential experience data | Duration: persistent or session | First-party.
- Storage consent state (localStorage) | Category: necessary (to record your choice) | Purpose: store your accept/reject decision for each category so that we can respect your choice and load or refuse to load the corresponding storage accordingly | Duration: typically 6–12 months, after which we re-request | First-party.
(C) Analytics and attribution (consent required)
- First-party analytics browser identifier (localStorage,
mozen_analytics_client_id) | Category: analytics | Purpose: recognize repeat visits from the same browser and continue the same visit when you go from our website into the app (see Section 6) | Duration: persistent with no fixed expiry, until you clear site data | First-party | Written only when analytics storage is on. - Sign-up source token (localStorage,
mozen_acquisition_context_token, app only) | Category: analytics/attribution | Purpose: a server-signed token recording where this visit came from (such as UTM parameters in the landing link and the referring site), used after sign-up to measure channel effectiveness | Duration: the token expires 7 days after issue and is deleted once onboarding is complete; when analytics storage is off it is kept only in the memory of the current page | First-party | Written only when analytics storage is on.
Payment and checkout are handled by Paddle as the Merchant of Record / authorized reseller. When you enter checkout or the customer portal, Paddle may set its own payment, risk-control, and anti-fraud storage items on its own domains, governed by Paddle's own cookie and privacy policies and not directly within the control of this Policy; that category is necessary to complete payment.
6. First-Party, Self-Built Analytics Statement
Mozen's site analytics is a first-party, self-built implementation: our website and our app share the same collection code, data is sent only to Mozen's own servers, and we do not use third-party analytics or tracking SDKs or embed third-party advertising or behavioral-analytics scripts. Analytics data is used to understand overall traffic, source channels, and feature usage.
- What we record: the pages you visit (IDs in links, such as note or share IDs, are replaced with placeholders), clicks on main buttons, key steps in the product (such as starting sign-up, finishing onboarding, or viewing and choosing a plan), presence heartbeats while a page is open (to measure time on page), the referring site's domain, campaign parameters in the link (UTM), the type of ad click identifier (only the parameter name, such as gclid; its value is never read), and the interface language. Our server also derives your approximate location (country, state/province, city) from your IP address and classifies your device type, browser, and operating system from your browser's User-Agent. Raw IP addresses and full User-Agent strings are not written to analytics data.
- Browser identifier (only when analytics storage is on): once analytics storage is on (you consented, or you are in a region where it is on by default), we keep a randomly generated identifier (
mozen_analytics_client_id) in your browser's localStorage to recognize repeat visits from the same browser. It is first-party storage, not a cookie, and is not sent automatically with requests; our website and app domains each keep their own copy. In prior-consent regions we neither write nor read it before you consent; after you refuse or withdraw consent, we no longer read or send it. - Daily anonymous fingerprint: to group consecutive visits on the same day into one visit, our server computes a one-way hash from your IP address and User-Agent plus a random key generated each day (UTC). The key is destroyed after about 2 days, after which the same hash can no longer be computed, so visits on different days cannot be linked through it, except for a single visit still in progress across midnight. Nothing is written to your device for this; when analytics storage is off, it is the only way we tell visits apart.
- From our website into the app: when you click a link on our website to the Mozen app (app.mozen.ai, mozenai.com) or another Mozen domain, we temporarily add parameters to that one navigation only:
mz_ref(the referring site's domain for this visit),mz_clk(the type of ad click identifier),mz_ts(the time of the click), and the UTM parameters you arrived with; when analytics storage is on, we also addmz_cid(the browser identifier above), but not in a prior-consent region before you consent. The receiving page accepts these internal parameters only within about 2 minutes of the click; in an expired link (for example, one copied or forwarded and opened later) they are ignored.mz_ref,mz_clk,mz_ts, andmz_cidare removed from the address bar once used (within about 2 minutes at the latest); UTM parameters stay. The link on the page reverts to its original form right after the click. These parameters are passed only between Mozen's own domains. - When you are signed in: after you sign in to the app, analytics events are associated with your account. If the browser holds the identifier above, we map it to the first account that signed in with it, so that visits before sign-in (including website visits linked through
mz_cid) are attributed to the same visitor. - Privacy signals: when your browser sends a DNT or Global Privacy Control (GPC) signal, we send no analytics data at all and do not write the browser identifier, in every region.
- No cross-site tracking: we do not use this analytics to identify or track you on websites other than Mozen, do not build cross-site behavioral profiles, and do not sell or "share" the relevant identifiers with ad networks for targeted advertising.
- Retention: analytics events and visit records are kept on our servers for 400 days and then deleted; the daily key used for the daily fingerprint is destroyed after about 2 days. The browser identifier stays in your browser with no fixed expiry; you can delete it at any time by clearing this site's data.
This statement does not change the Privacy Policy's description of other necessary logs (such as server security and anti-abuse logs); such logs are necessary for the operation and security of the Service and are not the optional analytics described in this section.
7. Consent, Withdrawal, and Preference Management
Regional scope: the prior-consent rules in this policy apply to users visiting from the European Economic Area, the United Kingdom and Switzerland (determined by the IP address at the time of the visit; if it cannot be determined, these rules apply as well). In other regions, preference and analytics storage is enabled by default and you can turn it off at any time in Settings → Privacy, Security & Permissions. When your browser sends a DNT or GPC signal, we do not enable analytics in any region.
We obtain and manage your consent to non-essential storage technologies as follows:
- Prior consent: for the analytics and attribution category (Category C) and for the preference category (Category B) where consent is required in the applicable jurisdiction, we request your consent before setting or writing them. By default, the relevant categories are off; they are enabled only after you make an affirmative choice (such as clicking "Accept analytics") via the consent banner or preference center. Pre-ticked boxes or continued browsing do not constitute valid consent.
- Category-level choice: the consent controls let you accept or reject by category (necessary / preference / analytics). The necessary category cannot be turned off because it is required for the Service to operate; we clearly explain its purpose.
- Withdrawal as easy as consent: you may at any time reopen the consent panel via the storage/cookie preference controls in "Settings → Privacy, Security & Permissions" within the app to adjust or withdraw consent for any optional category. Withdrawal is as easy as giving consent, and withdrawal does not affect the lawfulness of processing carried out on the basis of consent before its withdrawal.
- Browser-level controls: you may also use your browser settings to delete or restrict cookies, clear localStorage/sessionStorage/IndexedDB, block third-party storage, or use private mode. Note that clearing necessary storage may result in loss of login state, current workspace, offline content, unsynchronized edits, or preferences.
- Consent validity and re-request: we record your choices and re-request after a reasonable period (typically 6–12 months) or upon material changes, to ensure consent remains valid.
8. Respecting Global Privacy Control (GPC) and Do-Not-Track (DNT)
We respect privacy preference signals sent by browsers and devices:
- Global Privacy Control (GPC): when we detect a valid GPC signal from your browser or an extension, to the extent applicable law (such as the California CCPA/CPRA) treats it as a valid opt-out request, we treat it as a request to opt out of and refuse consent to "sale/share" and to non-essential analytics/attribution storage technologies, and accordingly do not set or read the corresponding identifiers for analytics purposes.
- Do-Not-Track (DNT): when your browser sends a DNT signal, we treat it as a preference to refuse non-essential analytics/attribution storage technologies. Given the lack of a uniform DNT standard, our handling defaults to refusing non-essential storage.
- Signal priority: where a GPC/DNT signal conflicts with the consent-banner state, we apply the outcome more protective of your privacy, i.e., the relevant optional storage technologies remain disabled by default.
- No effect on the necessary category: GPC/DNT will not disable strictly necessary storage technologies, as those are required for the service you have actively requested; however, we will not use this as a basis to expand our collection.
9. Relationship to Personal Data and International Transfers
Some storage technologies (particularly sign-in sessions and analytics identifiers) may involve personal data. For such processing:
- Our processing of personal data and your rights of access, correction, deletion, objection, and portability are governed by the Privacy Policy.
- Data residency and transfers: browser storage stays on your device. When data is synchronized or processed by our services, it may be transferred across borders: our primary database is hosted in Singapore, object storage and content delivery use global edge locations, and AI processing may take place in mainland China, the United States, or other regions depending on the feature used. We use safeguards such as Standard Contractual Clauses as required by law. See the Privacy Policy and the Subprocessors list.
- Security: data is encrypted in transit and at rest by our providers. Mozen does not offer end-to-end encryption, and we do not claim any security certification we have not obtained.
10. Storage Arising from Third Parties and External Connections
- Payment: when you use the checkout or customer portal of a payment provider (Paddle, Stripe, or, on the mainland China storefront, Alipay), that provider may set its own payment, risk-control, and anti-fraud storage on its domains under its own policies.
- External storage and third-party accounts: when you connect Google Drive, OneDrive, Baidu, WebDAV, or other external services, those third parties may set their own storage as you interact with them, under their own policies.
- Research and retrieval sources: research, web search, and academic retrieval make server-side requests to external sites and do not set third-party cookies in your browser under Mozen's name.
- Sharing and public pages: when you open someone's share link or public page, our first-party storage under this Policy still applies; externally embedded resources are the responsibility of their sources.
We do not control storage set by third parties on their own domains; please review their cookie and privacy policies.
11. Children and Minors
You must be at least 16 years old to use Mozen. Mozen is not directed to children, and we do not knowingly set non-essential storage for, or collect analytics data from, anyone under 16. Users under the age of majority where they live may use the Service only with the permission of a parent or legal guardian, who may also manage their optional-storage choices. If we learn that non-essential storage was set for, or personal data collected from, a child without the necessary consent, we will delete it.
12. Policy Updates
We may update this Policy due to changes in features, sub-processors, storage technologies, law, or operations. For material changes (for example, adding a storage category that requires consent or introducing a new analytics mechanism), we will provide notice through reasonable means such as in-app notifications, the consent banner, email, or website announcements, and will re-request your consent where applicable law requires. The version and effective date are noted at the top of this Policy. Continued use indicates your acceptance of the updated Policy, except where applicable law requires that consent be separately obtained.
13. Contact Us
For questions, requests, or complaints regarding Cookies, local storage, or consent management, please contact: [email protected]. For legal notices or formal service-of-process information requests, please contact: [email protected]. For refunds and billing matters, please contact: [email protected]. For general support, please contact: [email protected]. To protect your account security, we may need to verify your identity before processing the relevant request. You also have the right to lodge a complaint with the data protection authority in your jurisdiction.