Legal boundary wording

Before wording review

Use this page before public report sharing, PDF export, ticket export, remediation handoff or monitoring summaries leave the private workspace. Legal boundary wording keeps WebRiskOps output tied to observed technical evidence and product workflow guidance. The report can describe what the scanner observed, what evidence is missing and which automated next action is available. It must not become legal advice, a compliance certification, a security certification or a guarantee that every issue has been found.

Review legal boundary wording

Follow the path `Reports → Private report → Legal boundary → Public report or export → Next action`.

1. Open /reports/{report} before public sharing, PDF export or remediation handoff. Result: report summary, findings, publication state and legal disclaimer are visible.
2. Read the legal-boundary disclaimer near the report summary or export controls. Result: the report states technical findings and recommendations, not legal advice, certification or a complete risk guarantee.
3. Check that severity, confidence, evidence and recommendations stay tied to observed scanner facts. Result: technical evidence does not become legal or compliance conclusions.
4. Review public report and PDF or print wording before external sharing. Result: tokenized and static outputs keep the same boundary language.
5. Remove wording that says certified, guaranteed compliant, legally approved, vulnerability-free or every issue found. Result: publication gates are not bypassed by unsafe claims.
6. Continue only after boundary wording is safe. Result: remediation, ticket export, monitoring or sharing proceeds with evidence-based language.

Required boundary language

Every external-facing report surface should keep the same meaning.

• Technical findings means the report describes automated checks and observed evidence.
• Workflow guidance means recommended next actions stay tied to product-supported remediation, retest, monitoring or sharing flows.
• Not legal advice means WebRiskOps does not interpret laws, regulations, contracts or buyer requirements.
• Not certification means the report is not an audit opinion, compliance certification, security certification or attestation.
• No completeness guarantee means the report does not promise that every risk, defect or vulnerability has been found.

Unsafe wording states

Stop publication, export or handoff when unsafe wording appears.

• Certification claim means revise the text before using [Publication gates](/docs/reports/publication-gates).
• Guarantee claim means remove language that promises compliance, security, buyer acceptance or complete coverage.
• Legal advice claim means remove interpretation of laws, contracts, regulatory duties or compliance obligations.
• Unsupported scope claim means return to evidence and accepted scope before describing pages or domains the scanner did not inspect.
• Sensitive evidence claim means use [Privacy redaction](/docs/projects/privacy-redaction) before public, static or ticket-based sharing.

Continue to remediation or monitoring

Continue to [Fix tasks](/docs/remediation/fix-tasks), ticket export or monitoring only after the wording is safe. Use [Public reports](/docs/reports/public-reports) and [PDF and print export](/docs/reports/pdf-and-print-export) when the recipient needs a shareable or static copy with the same boundary language.