aceModerate evidence
Published recordHealthProblem Space
More
Comparing AI chatbot users and non-users in Germany: Reasons for use, addictive AI chatbot use, mental health, and loneliness
- Truvace record
- TRV-2026-2536raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Survey
- Sources
- 1 sourcePeer-reviewed
- sha256
- b632896bea4e…check it
The use of Artificial Intelligence (AI) chatbots is becoming increasingly popular worldwide. To prevent potential negative consequences associated with the use at an early stage, it is crucial to understand its associations with mental health. Therefore, the present study compared people who use AI chatbots with those who do not engage in AI chatbot-interactions in terms of mental health and loneliness. Moreover, we investigated potential mechanisms associated with addictive AI chatbot use. Data of 7,312 persons…
The problem
In an online survey of 7,312 German adults, AI chatbot users reported significantly more loneliness, depressive, anxiety and stress symptoms and lower life satisfaction than non-users, and using chatbots to escape negative emotions went with more addictive use.
What this doesn’t fix
The associations are correlational and most effect sizes were small, so the study cannot show that chatbot use causes worse mental health; the authors say experimental longitudinal research is needed to clarify causal mechanisms.
Sources
1 on file- Computers in Human Behaviordoi:10.1016/j.chb.2026.109199
Cite this record
v1Truvace Impact Record TRV-2026-2536, v1: “Comparing AI chatbot users and non-users in Germany: Reasons for use, addictive AI chatbot use, mental health, and loneliness.” Truvace, 2026-11-12. /record/TRV-2026-2536 (accessed on the day you copy it). sha256 b632896bea4e1994…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2536 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.