Sessions, inactivity and shared devices

Temporary clearing is not the deletion of saved Cloud records.

Intended audience: All audiences

Concept prototype. Do not submit sensitive information. Planned instructions describe intended design, not an activated service.

Content owner: Program content reviewer (proposed; CHI assignment pending)
Review: Source-reviewed documentation; organizational and professional validation pending.
History: V5.8: public reference foundation · V6.0: enterprise specifications and linked registers

Different session boundaries

Public practice is temporary memory. Account sessions are separate and include source-designed server leases. Ending a session does not delete saved Cloud information.

Designed behavior

Full /demo walkthrough clears on exit, refresh/remount or sixty-second inactivity.
Impact practice clears on exit, refresh or sixty-second inactivity.
AI and human-support conversation state is local and clears on exit/inactivity; pending replies are cancelled.
Personal account sessions have a warning/extension path and reauthentication requirements.
Kiosk expiry fully clears personal content and does not offer an extend option.
A PIN is never the sole remote account credential.

Safe shared-device use

Start anonymously; never inherit another visitor’s fictional profile.
Use fictional non-sensitive data in practice.
End and clear practice before leaving.
Do not assume saved account data has been deleted by signing out.

Expired practice

A fictional project or goal disappears when the session clears. This is intended temporary behavior, not a recovery failure.

Verification and limitations

Local-memory clearing tests do not establish every published account lease or MFA lifecycle. Saved-account and kiosk positive-session security requires separately authorized testing.

Source and review limits

src/lib/youth-session.ts; src/components/covcare/useDemoWalkthrough.ts; docs/covcare-v56-production-development-readiness.md

This is a source review, not clinical, legal, safeguarding or formal CHI approval. See the completion report for actual runtime checks.