AI & ML
Measuring Personal Information Exposure in Mental Health-Related Conversations with LLMs
arXiv cs.HC0 views
arXiv:2610.41045v1 Announce Type: new Abstract: Large language models (LLMs) are increasingly used for informal mental health support, yet the privacy implications of conversational interaction remain poorly understood. Prior LLM privacy research has focused largely on model-side risks such as memorization and adversarial extraction, leaving personal information inferred from ordinary conversation understudied. We introduce a profile-recovery framework that measures personal information exposure by comparing user profiles with attributes inferred from conversation alone. We generate 240 synthetic multi-turn mental health conversations from profiles sampled from a nationally representative health survey and validate them against real counseling transcripts, finding comparable overall disclosure volume. Across 21 attributes, 33-41% of each profile is recoverable, with 76.5% first-inference and 94.3% any-of-3 accuracy. 239 of 240 conversations expose at least one sensitive mental health attribute, and 45.0\% expose all six. Our findings reveal a gap between disclosure and inferability, motivating HCI approaches to make inference risks legible and support privacy-aware interaction design.
Source:https://arxiv.org/abs/2610.41045PreviousRobot Navigation and Canine Welfare: A Pilot Study Surfacing Challenges for Cross-Species Legibility and Proxy Validity in Animal-Machine InteractionNextOut of sync: Accommodation, evaluation, and emergence in five weeks with an agentic AI teammate
Related posts
Anthropic Releases Claude Fable 5.2 and Mythos 5.2: Cheaper, Faster, and an RSI Debate
0dev.to AI
70% of Requirements, 26% of Tasks: What Alibaba's Co-Design Bench Teaches About Evaluating Coding Agents
0dev.to AI
Meta Muse Ember: The $0.10 Model Built to Run Your AI Agents' Grunt Work
0dev.to AI
Your Singapore Christmas trip starts at a visa agent, not the fare sale
0dev.to AI
I built 60 free developer tools that run entirely in your browser - what should I add next?
0dev.to WebDev
Role-Based Access vs Blanket Bans for AI Coding Agents: What Goldman Sachs Shows
0dev.to Security