50/100

Moderate evidence

ProblemPublished recordHealthProblem Space

The Role of Biological Rhythms in Generative AI Addiction: Associations with Chronotype and Sleep Quality

Truvace record
TRV-2026-2592raw data (JSON)
Version
v1Published
First published
Evidence type
Survey
Sources
1 sourcePeer-reviewed
sha256
457f255f64ed…check it

Abstract The rapid diffusion of Generative Artificial Intelligence (GenAI) technologies among university students has introduced a novel domain of technology-related behavioral risk. Although prior research on digital addiction has predominantly focused on psychological determinants of internet and smartphone overuse, the potential role of circadian preference and sleep in problematic GenAI use remains underexplored. This study examined associations between chronotype, sleep quality, and GenAI addiction. Using a…

The problem

In a survey of 868 undergraduates at a public university, evening-type students scored higher on generative AI addiction than morning and intermediate types, and poorer sleep went with higher scores.

What this doesn’t fix

The cross-sectional design at a single public university shows associations only, and the authors say longitudinal and multi-method research is still needed.

Sources

1 on file
  1. Peer-reviewed2026-06-04

Cite this record

v1

Truvace Impact Record TRV-2026-2592, v1: “The Role of Biological Rhythms in Generative AI Addiction: Associations with Chronotype and Sleep Quality.” Truvace, 2026-11-12. /record/TRV-2026-2592 (accessed on the day you copy it). sha256 457f255f64ed3d4b…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv1457f255f64ed…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2592 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.