Cookie and local-storage overview for DueKit

• Essential session cookies may keep sign-in state and verification continuity available on the current controlled recovery surfaces.
• Local browser storage may keep guest drafts, return-state signals, and lightweight continuation helpers available before account value is required.
• Operational safeguards may use short-lived technical state to reduce abuse, protect routes, and keep the product available.

This page is scoped to the live root product: guest-first local drafts, magic-link sign-in where verification is active, and the safeguards that keep those flows working.

• Keep the workflow recoverable so local quote and invoice drafts, plus controlled recovery prompts, do not force people to start over.
• Protect sign-in, rate-limited routes, and other operational boundaries needed to run the current release safely.
• Preserve low-friction product behavior rather than build a broad behavioral-advertising profile.

• Browser controls may clear local drafts, sign-in state, or continuity helpers that the current workflow relies on.
• Some essential cookies are required for sign-in continuity, workspace recovery, or service protection and should not be described as optional preference tracking.
• If cookie or local-state behavior changes materially, the new behavior should appear here before the live product depends on it.

This page describes the current product state in plain language rather than jurisdiction-specific compliance obligations.

• It does not promise an advertising, affiliate-tracking, or personalization system that the current root surface does not ship.
• Questions about actual browser-state behavior should be routed through support so the shipped behavior can be confirmed against the live product.