Local worksheet
The worksheet does not upload or silently transmit entries. It writes a procedure draft only after “Save draft” is activated. It writes the reusable environment profile only after “Save environment profile” is activated. JSON download occurs only after “Export JSON” is activated. “Clear saved worksheet” and “Clear environment profile” remain separate confirmed actions under Data management. Browser storage remains available to people and scripts with access to the same browser profile and origin.
Data minimisation
Use engagement IDs and evidence references. Do not enter passwords, access tokens, session cookies, private keys, client secrets, unnecessary personal data, medical details or unconsented participant information. Redact screenshots, speech history and DOM extracts before they leave the controlled assessment environment.
Website analytics
The public storefront may offer optional Google Analytics only when Source/site-config.json records an active Google Analytics 4 measurement ID. The Google tag must load only after the visitor allows optional analytics through the on-page analytics choice. Analytics must stay disabled while the measurement ID is unknown, the Google property is not confirmed or the visitor keeps analytics off. Analytics is for aggregate storefront traffic and product-page journey measurement only; it must not collect worksheet entries, exported execution records, client evidence, payment details or personal accessibility observations.
Checkout and protected-download analytics are controlled by the merchant-of-record platform. Review that platform's reporting and privacy controls before live sales.
Evidence storage
Keep sensitive evidence in the organisation’s approved access-controlled system. The execution record should reference it. Apply least privilege, log access where required and preserve checksums for immutable files. Do not commit client evidence to this repository.
The specialist browser agent embeds page title, bounded focus text and diagnostic findings in its JSON execution record. Use it only on authorised targets, review the record for secrets and unnecessary personal data, and move approved evidence to the engagement’s controlled store. First-blocker messages are local standard-error output and local JSON records; no external notification destination is configured.
Clear and delete
Export required work before clearing browser storage. Clear local data when the engagement retention schedule no longer permits it. Deleting a browser draft does not delete separately exported files or referenced evidence.
User studies
Record the recruitment and consent basis, safeguarding process, permitted use, retention period and deletion process before collecting participant data. Store identity separately from observations when practical. Report only participant characteristics relevant to interpreting the study.
Security-sensitive testing
Use authorised test accounts and synthetic data. Do not weaken production security controls, expose recovery information or publish exploit details merely to create accessibility evidence. Record security constraints as limitations and arrange an authorised environment when they prevent testing.