Cookie Settings

Session persistence logic for auth flow, workspace continuity, and analytics behavior.

This page now explains what persistence mechanisms exist in the prototype and what they will represent in the final app. It is written to match the product shell and to be directly portable into the real application later.

Essential session storage

Required to preserve login state, sign-up flow progression, generator defaults, and basic navigation continuity while moving between dashboard pages.

Required

Functional preference persistence

Used to remember selected duration, learner level, HPI mode, or similar configuration patterns that improve repeat use of the dashboard and generator experience.

Enabled

Analytics instrumentation

In the final application this would support aggregate behavior tracking, case completion analysis, and insight generation. In the prototype it is represented only at interface level.

Planned

How this maps to the real application

Prototype storage is local and presentation-oriented. It exists to make the flow coherent before migration.
Production storage will move behind authenticated services and should be governed by real server-side controls.
Session continuity should support login redirect to homepage, protected dashboard pages, and reliable logout behavior.
Analytics and insight persistence should be separated from critical auth/session records to keep operational boundaries clear.