[P2] Audit: Trust Center needs more contextual links inside sensitive workflows

[baixiangcpp]

Imported from the byteflow.tools deep audit on 2026-06-22.

Problem: Trust Center is one of the strongest trust assets on the site, but important tool moments should link to it more directly. Users benefit from seeing local-processing, external-request, storage, and cache explanations near the controls they are using.

Affected components:

• JWT and token tools
• Log and HAR tools
• External-request tools
• Pipeline Builder save/export/share controls
• File import and image upload tools

Reproduction steps:

1. Open representative sensitive-input and external-request tools.
2. Check whether Trust Center is linked near the relevant input or action.
3. Check mobile visibility.
4. Compare trust panel placement with the actual action location.

Expected behavior: relevant trust explanations should be one click away from sensitive inputs, file imports, external requests, and sharing/exporting actions.

Actual behavior: Trust Center is linked, but not always at the most decision-relevant point in the workflow.

Impact: users may miss important privacy and processing explanations.

Proposed fix:

• Add context-specific trust links near sensitive controls.
• Use anchors to link to exact Trust Center sections.
• Add compact mobile trust chips.
• Add a “verify in DevTools” link for local-processing tools.

Acceptance criteria:

• Sensitive workflows expose contextual Trust Center links.
• Links route to relevant anchors.
• Mobile pages keep trust guidance visible without crowding.
• Users can distinguish browser-local and external-request behavior quickly.

[baixiangcpp]

Closed as completed by the canonical BF audit backlog work. This older non-BF audit issue duplicates work now merged through PRs #209-#219, with the BF issues closed and guard/test coverage in place. The remaining non-duplicate follow-up is #7, which stays open because the upstream Next/PostCSS advisory is not fixed yet.