Understand where session information goes

Source audit draft. This is not a HIPAA-compliance certification, legal review, or verification of hosting-provider retention and logging policies.

In the clinician’s page memory

Optional first name, target details, and set notes are held in browser memory by the session documentation component. They are not intentionally submitted by that component to the room API or saved in browser storage. Refreshing, leaving, or closing the page can clear them.

In temporary server-side room state

Room controls include shared scale prompts, numeric responses, and selected feelings, body-map selections, and shared negative/desired-belief selections, including custom belief text. They are transmitted between the clinician and participant through authenticated room APIs and persisted in the existing room database, linked to a room and clinician account. They may be clinically sensitive even without a participant name.

Source code expires rooms and performs deletion during later API activity. Expiration is not verified immediate deletion, and this audit does not establish backup or infrastructure-log retention.

In downloaded files

The existing CSV and graph export can include ratings and, where enabled, target details, notes, and the optional first name. The existing end-session dialog offers a download choice. Review what you intend to export, use an approved practice system, and protect the downloaded copy. This release does not add field-by-field export selection or change the export format.

Account and learning data

Clinician authentication is unchanged. Signed-in Academy progress is stored against the account. Tool preferences can be remembered locally when that option is enabled. Anonymous participant access does not mean no data is transmitted.

Platform usage analytics

Signed-in visits record the account ID, a broad page area (such as Solo Tool or Resources), timestamps, and estimated visible-tab time. Administrators can see this account-level activity. Remote-link reporting records the clinician account, a room reference, creation time, successful link opens, and estimated participant connection time. It does not copy notes, ratings, participant identities, link tokens, or clinical responses into analytics. Usage data is retained for up to 90 days and deleted during subsequent activity. Duration estimates can be incomplete when a browser closes or a connection drops. Anonymous participant pages do not create account-level page-visit records.

New preparation tools

Educational checkboxes and scale examples are transient component state. The technical test creates no remote room and collects no clinical content. Ordinary page requests still reach the hosting service. Preparation examples do not submit their answers to usage analytics.

Before clinical use

Confirm whether the existing room data flow, contracts, logging, retention, security controls, and export workflow meet your practice requirements. Keep exact locations, emergency contacts, and completed planning worksheets in appropriately protected practice systems. Do not enter identifiers into shared feelings, custom belief selections, or URLs.