AI & ML
From One Query to Many: A Critical Survey of Privacy Accounting in RAG
arXiv cs.CR0 views
arXiv:2610.21245v1 Announce Type: new Abstract: Retrieval-augmented generation (RAG) enables large language models to leverage external knowledge but introduces privacy risks when the retrieved corpus contains sensitive information. Differential privacy (DP) offers formal protection, yet interpreting and comparing privacy guarantees across existing DP-RAG methods remains challenging. In particular, a privacy budget reported for a single response does not directly characterize privacy loss over repeated queries, and even identical values of $\varepsilon$ may represent different guarantees depending on the protected data unit, accounting horizon, and observable outputs. This survey critically examines how privacy accounting evolves from single-query generation to multi-query RAG systems. We categorize existing approaches into query-time privatization, multi-query accounting, and one-time corpus privatization. We analyze their underlying assumptions and privacy--utility trade-offs. Rather than ranking methods by $\varepsilon$ alone, we propose a framework that interprets a DP-RAG guarantee along three dimensions: privacy granularity, accounting scope, and release boundaries. We conclude that an $\eps$ is a claim only together with the three slots: the protected unit, the accounting scope, and the release boundary.
Source:https://arxiv.org/abs/2610.21245PreviousOn the Complexity of Symmetric Boolean Functions in Multiparty Private Simultaneous MessagesNextTrigger Value Selection in Clean-Label Malware Backdoors: An Effectiveness-Detectability Analysis
Related posts

Behavioral Design Unpacked: Nudges, Funnels & Persuasion | UX Unpacked #3
0dev.to UX
National Grid buys Teesside land for UK largest substation to power AI data center
0dev.to News

Leonardo AI Alternative in 2026
0dev.to Discuss

This is my first HacktoberFest, and I don't know what to feel.
0dev.to Discuss

12% of the Economy: The Benchmark That Grades AI Agents Like Employees
0dev.to Machine Learning
A headline said the CMB killed huge black holes. I read the two papers.
0dev.to Career