Effective date: 3 October 2026.
Scope and meaning#
Nuits, the Finnish sole proprietorship operated by Bapusaheb Patil, operates Quire. Contact legal@quirelms.com about this inventory. It covers cookies and other device storage, including localStorage, sessionStorage, IndexedDB and Cache Storage. Our Privacy Policy explains server-side processing and rights.
This is a source-based inventory of the current public static sites, browser-local demo and available application flows, not a claim that every item is set on every visit. Application cookies depend on the host, sign-in method, tenant configuration and function you use. Authentication lifetimes below are defaults or configured limits, not measurements from every production deployment. HTTPS authentication cookie names can have a __Secure- prefix. Cookies are scoped to the relevant host; preferences on one subdomain need not control another.
Public marketing and documentation#
The current marketing pages have no configured advertising or behavioural-analytics cookies. Visiting them still creates network requests to Cloudflare's delivery infrastructure. Infrastructure security behaviour is not a claim of zero request logging or a complete capture of all edge-issued cookies. If you encounter an unlisted security cookie, send its name and site to us without sending its secret value.
The documentation site stores user-interface preferences on your device:
- ui-mode in localStorage remembers light or dark mode. There is no code-set expiry; it remains until changed, removed or evicted by the browser.
- nb-api-code-rail__lang in localStorage remembers the API example language you choose. There is no code-set expiry.
- nb-banner-dismissed-{id}, if a dismissible banner is used, stores its dismissal. A banner may set a number of days; otherwise the stored dismissal has no code-set expiry. It is not an advertising identifier.
- ui-pm-tab in sessionStorage remembers a package-manager tab for the page session. Documentation sidebar state can also use sessionStorage to preserve expanded groups and scroll position. Session storage normally ends with the tab/session, subject to browser session restoration.
These support the interface you use rather than cross-site profiling. You can change theme and code/tab choices through the documentation controls, or remove their storage through browser site settings. Browsers may restrict or clear storage earlier than the periods described here.
Application sign-in and security cookies#
When an actual application flow uses them, the following first-party cookies support authentication and security:
- better-auth.session_token holds the sign-in token. Default authenticated session expiry is seven days, but a deployment can set a different session policy or end a session earlier.
- better-auth.session_data caches session/user information for the deployment's selected short cache duration. better-auth.account_data is an available account-cache cookie whose use and lifetime depend on the enabled flow; it is not asserted to be present on all deployments.
- better-auth.dont_remember records a session-only sign-in choice. Browser session restoration can affect when a session cookie disappears.
- better-auth.state can correlate a database-backed OAuth sign-in state for 300 seconds. With the alternative cookie-state strategy, better-auth.oauth_state lasts 600 seconds. The enabled strategy determines which is used.
- better-auth.two_factor supports an MFA challenge for 600 seconds by default. better-auth.trust_device remembers an approved device for 30 days by default when that option is used.
- better-auth.better-auth-passkey supports a passkey ceremony when used. It is a short-lived challenge cookie; its exact expiry follows the installed passkey flow, not a single duration promised for all deployments.
- quire_guest holds temporary guest authentication and expires with the guest session configured for that flow.
- quire_view_as holds a tenant administrator's read-only impersonation grant and expires according to that grant. quire_platform_impersonation holds a platform support impersonation grant for 1,800 seconds, or 30 minutes.
Authentication and privileged-access cookies are normally HttpOnly and SameSite=Lax and use secure transport on HTTPS. Some client-visible demo or preference cookies differ. Do not give us cookie token values in a support email. Blocking essential cookies can prevent sign-in, guest access, security challenges or other functions you request.
Consent, requested preferences and shopping#
- quire_consent records a visitor identifier, functional and analytics choices, a Global Privacy Control flag and the decision time for one year. It records the choice itself; it is not permission to sell data. The visitor identifier is not a guarantee of irreversible anonymity.
- quire_color_scheme remembers the requested colour scheme. quire_course_index can remember the course drawer choice where that function writes it. The shell cookie serializer defaults to one year; their presence depends on the screen and caller.
- quire_cart is an opaque cart identifier lasting 30 days in a customer storefront flow. It is not evidence that the current Quire pre-release marketing site has a checkout.
- quire-platform-cookie-notice in localStorage records dismissal of the platform's essential-cookie notice. It has no code-set expiry and stays until browser storage is removed or evicted.
Essential storage for a requested function and recording your preference is distinguished from optional functional or analytics categories. On tenant hosts, the current preference controls provide Essential, Functional and Analytics choices. There is no separate advertising/marketing-cookie toggle. Application analytics depend on deployment configuration as well as your applicable choice; optional page statistics are different from educational progress, assessment evidence and security logs.
The browser-local demo#
The public demonstration is not a production institutional account. It loads a fictional snapshot and keeps changes on this device:
- quire-demo-actor in localStorage remembers the selected fictional person with no code-set expiry.
- The IndexedDB database /pglite/quire-demo contains the local application database. quire-demo-meta stores snapshot version metadata. A changed snapshot version or Reset demo data can replace the working database; there is no fixed time-based expiry.
- quire-demo-blobs stores demo-uploaded files and their metadata. quire-demo-collab can store locally edited collaborative documents. They have no fixed time-based expiry and depend on reset, removal and browser eviction.
- Versioned quire-demo-shell- and quire-demo-assets- caches hold demonstration pages and assets. Updating the service worker can replace old versions, but this is not a timed deletion guarantee for all device data.
Use the Reset demo data control to return the working demonstration to its seeded state. Do not assume that this control removes every remembered preference or every separate browser store. For complete device removal, close other demo tabs and clear all site data for demo.quirelms.com in the browser, including cookies, local/session storage, IndexedDB, service workers and caches. Save any work you want first; clearing storage is destructive. The demo is for adults and non-confidential sample data only.
Offline learning and temporary recovery#
Where an institution enables offline learning, IndexedDB quire-offline version 2 has outbox, packages, meta and forumDrafts stores. These can hold downloaded course metadata, personal drafts, session metadata and queued changes. Cache Storage uses quire-shell-{version} for the application shell and quire-offline-{tenant}-{user}-… for downloaded course pages/files. These stores have no universal fixed expiry: they persist until the relevant application cleanup, successful sync/discard, explicit removal or browser eviction. Authentication, payments, administration, reports, search and AI routes are excluded from the offline page cache, but downloaded content and personal work can still be sensitive.
Successful queued changes are removed from the outbox; conflicts or refusals can remain for retry or discard. An account switch clears certain previous-user packages, page caches and forum drafts, but is not a guarantee that every unsynced entry or all local personal data has disappeared. Server-side deletion does not necessarily delete device copies.
Temporary sessionStorage can include quire:aicc-handoff:{activityId} for a learning-activity handoff, quire.wiki.restore.{room} for unsent wiki recovery, and quire.accountMerge.pending for a pending account-merge status. Their ordinary lifetime is the browser tab/session, subject to session restoration. Clearing them may lose unfinished work or interrupt the relevant flow.
Choices and withdrawal#
Read the Cookie Preferences Guide for the working controls and device-removal steps. On a tenant application, its Cookie Preferences link opens the same-host choices. Reject optional categories or withdraw a previous grant there. Account → Privacy also exposes applicable communications and personal-purpose controls. Browser Global Privacy Control turns off optional functional and analytics choices in the application's consent state; it is not an instruction to delete essential records.
The static marketing and documentation sites do not offer an imaginary marketing toggle or record a choice for an advertising system that is not present. Browser controls can delete or block storage, but blocking necessary storage may make the demo, sign-in or offline functions unavailable. Deleting a cookie does not erase consent evidence held by the responsible controller or automatically withdraw a waitlist subscription. Unsubscribe or contact us for that.
A provider-specific challenge or integration can introduce additional storage when actually enabled. The responsible operator must disclose that deployment's real inventory rather than assume every available adapter is used. Ask legal@quirelms.com for operator-side information and the institution for its own deployment.