Q1: Why does my AO3 Wrapped show a lower word count than what I actually read in 2025?
A1: AO3 records a work in your history only once per unique work ID, matching the timestamp of your most recent visit. If you read a 100,000-word story in January 2025 and re-read it in November 2025, the script credits those words only once. Additionally, works you read while logged out or in private browsing windows leave no trace in your account history.
Q2: Can using an automated reading parser get my AO3 account banned?
A2: No. Parsing your own reading history does not violate the archive's Terms of Service, provided your script follows standard rate limits. Setting zero delay between pagination requests will cause Cloudflare or AO3's load balancers to temporarily throttle or IP-ban you for spam-like behavior, but your account itself remains safe.
Q3: Is it possible to generate an AO3 Wrapped safely on an iPhone or Android device?
A3: Mobile browsers rarely support secure userscript managers well. The safest approach on mobile is downloading a raw HTML export of your history pages on a desktop computer, or using mobile browsers like Firefox Android that support vetted userscript extensions. Avoid mobile apps from app stores that ask for your AO3 username and password.
