Build Pipeline Health Check Privacy

This reference defines the browser-local privacy contract for the build pipeline health check. The assessment is designed to support a private planning conversation in the current browser tab, not to collect or transmit assessment responses.

Data boundary#

The health check uses React in-memory state only. Selected answers, the calculated result, and action priorities exist only while the current page instance remains open. The assessment does not submit answers over the network.

It does not persist answers through cookies, localStorage, sessionStorage, or another browser persistence mechanism. It does not create an analytics answer payload. It does not encode answers in the URL, generate a share URL, or use URL fragments or query parameters to restore an assessment.

The assessment does not collect free-text input. Responses use only the defined score choices and fixed dimension labels. It does not ask for names, contact details, project details, notes, explanations, or attachments.

Reset and tab behavior#

Reset replaces the current React in-memory assessment state with an unanswered state. After reset, no prior selection, result, or action priority remains available in the tool.

Closing the tab discards the in-memory state. Reloading or navigating away also starts a new unanswered assessment because there is no persistence or URL-based restoration. A user who wants to keep a completed result must use print or local download before closing or resetting the tab.

Print and local download#

Print and local download are browser-local outputs. They do not submit an answer payload or create a share URL. They are available only after the required assessment answers are complete.

The print view and local download contain the completed assessment values: the six dimension labels and selected scores, calculated total and percentage, result band, and the two action-priority dimensions. They do not contain free text, hidden browser identifiers, tracking fields, cookies, or stored response history.

Printing sends the visible result to the browser's normal print flow. Local download creates the assessment output in the browser for the user to save locally. Neither operation sends the assessment answers to an application endpoint.

Verification steps#

Verify the contract in a browser with developer tools available:

1. Open the Network panel, preserve its log, complete the assessment, reset it, print it, and create a local download. Confirm that these actions produce no answer-submission request.
2. Inspect browser storage for the assessment origin before and after selecting answers. Confirm that the tool does not write cookies, localStorage, or sessionStorage entries for answers.
3. Select several answers and inspect the address bar. Confirm that the URL, query string, and fragment contain no answer values and that no share URL appears.
4. Reload the page or close and reopen the tab. Confirm that all answers are unanswered and no result is restored.
5. Inspect the print preview and downloaded output. Confirm that they contain only the stated completed assessment values and no free-text, tracking, or hidden response fields.

Limitations#

Browser-local handling does not make a printed page or downloaded file private after the user saves, shares, prints, or stores it. The browser, operating system, print destination, download location, extensions, and device access controls are outside the assessment's in-memory state contract.

The same boundary also means there is no cross-device recovery, collaborative editing, history, or automatic backup. Users who need to retain a result must manage the local print or download output according to their own handling requirements. This privacy contract describes the assessment's data behavior; it does not replace browser, device, or organizational security controls.