Overview
Local Web and Research Agents keep prompts and retrieved pages away from a cloud provider, but autonomous searches create traces of destinations, order, timing, and volume. The series follows agent attribution, single-session intent recovery, and linked-session trait inference, then compares minimization, blocking, decoys, ECH, Oblivious DoH, and session controls. Evidence shows feasibility under selected agents, proxy traces, synthetic personas, and controlled visibility—not a universal leakage rate or combined protocol result.
Learning outcomes
- Local execution protects prompts and retrieved content from a cloud provider, not necessarily from the surrounding network.
- A WRA trace can support agent attribution, functional prompt recovery, and linked-session trait inference under controlled conditions.
- Minimization, blocking, and decoys change behavior differently and trade privacy against report quality, cost, or latency.
- ECH and Oblivious DoH protect different identifiers; neither proves that application behavior or session linkage is hidden.
Keywords
Preview every chapter · Unlock full text, audio, and video from chapter 4
PlansFAQ
Does running a Local Web and Research Agent protect research privacy?
Not from every observer. Local execution can keep the prompt and retrieved content from a cloud provider, while network observers may still see structured retrieval behavior.
What can a passive observer infer from a WRA network trace?
Under the study's controlled conditions, a passive observer could identify agent-like traffic, recover aspects of a current task, and infer traits from linked sessions.
Which defenses can reduce a WRA's trace while preserving useful reports?
Minimization, blocking, or decoys may reduce exposure while preserving utility, but only under task-specific conditions. Blocking needs safe source substitution; decoys require acceptable extra traffic.
Do ECH and Oblivious DoH hide a WRA's full network behavior?
No. ECH hides sensitive TLS handshake fields and Oblivious DoH separates DNS origin from query content, but endpoints, timing, volume, and session linkage can remain visible.