Platform continuity
Some storage keeps sessions, security, and navigation functioning in ways users expect.
Cookie Policy
A draft explanation of the browser-side storage and tracking mechanisms used around the web experience.
This page is intended to explain the essential, preference, analytics, and communication-related storage that may support the Craeftmann experience.
Draft legal scaffold
Cookie and local-storage descriptions should be reviewed against the final web implementation, analytics stack, and consent posture before launch.
- session and security related storage
- Essential
- settings that make repeat visits smoother
- Preference
- signals used to understand site quality
- Measurement
Useful preferences
Theme and install-prompt preferences are examples of storage that improves usability without changing account rights.
Consent discipline
Anything beyond essential operation should be reviewed against the right consent and disclosure standards.
Section 01
Essential storage
The web app may use cookies or equivalent browser storage for authentication continuity, security, routing, and other basic platform behavior that would be difficult to operate without.
Section 02
Preference and product storage
Preference data may be stored for themes, install-prompt dismissal, onboarding progress, or similar product-state features that make repeat use less frustrating.
Section 03
Measurement and disclosure
Analytics or campaign-related tooling should be documented precisely once the production stack is finalized. This draft route exists so the footer destination is live while those specifics are confirmed.
Next move
Need the wider privacy view?
The privacy policy explains how storage fits into the broader data posture of the platform.