Moderate evidence
Published recordLifestyleProblem Space
More
A Meta-Analysis of Artificial Intelligence Technologies Use and Loneliness: Examining the Influence of Physical Embodiment, Age Differences, and Effect Direction
- Truvace record
- TRV-2026-2746raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Systematic review or meta-analysis
- Sources
- 1 sourcePeer-reviewed
- sha256
- 0899ab4cd115…check it
Recent research has investigated the connection between artificial intelligence (AI) utilization and feelings of loneliness, yielding inconsistent outcomes. This meta-analysis aims to clarify this relationship by synthesizing data from 47 relevant studies across 21 publications. Findings indicate a generally significant positive correlation between AI use and loneliness ( r = 0.163, p < 0.05). Specifically, interactions with physically embodied AI are marginally significantly associated with decreased loneliness…
The problem
A meta-analysis of 47 studies across 21 publications found AI use positively correlated with loneliness (r = 0.163), with disembodied AI (r = 0.352) and adults aged 60 and above (r = 0.352) showing the strongest links.
What this doesn’t fix
The associations are correlational, and the analysis found both directions of effect significant, so it cannot establish whether AI use causes loneliness or lonely people use AI more.
Sources
1 on file- Cyberpsychology, Behavior, and Social Networkingdoi:10.1089/cyber.2024.0468
Cite this record
v1Truvace Impact Record TRV-2026-2746, v1: “A Meta-Analysis of Artificial Intelligence Technologies Use and Loneliness: Examining the Influence of Physical Embodiment, Age Differences, and Effect Direction.” Truvace, 2026-11-12. /record/TRV-2026-2746 (accessed on the day you copy it). sha256 0899ab4cd1156e84…
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-2746 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.
ace