weeb.ltd
Legal

Privacy policy

Last updated 2026-11-16

Who we are

This is the single privacy policy for all of StoryHoard: the weeb.ltd website and account, the StoryHoard browser extension, and the StoryHoard mobile app. The two app sections below describe what each app does with data; everything else applies across all three.

The data controller is weeb.ltd, operated by the site owner (Ryuu3rs). The postal address is available on request. For anything about your data write to privacy@weeb.ltd. Other addresses are on the contact page.

What we collect and why

You can read everything on weeb.ltd without an account, and the extension works without one. Account data only exists once you sign up. Visit statistics and app usage counts described below can include visitors without an account.

  • Account. Your email address, a username, and which provider you signed in with (email and password, AniList, Google or Discord). If you sign in with Google or Discord, we also store the name and profile picture address that provider gives us, and its sign-in tokens (stored encrypted). That name is never shown on your profile; if you become a supporter it is passed to Stripe with your email. Passwords are stored as scrypt hashes. We also keep a record of which version of the terms and this policy you accepted at sign-up. Basis: contract, to run your account.
  • Birth year. A year only, never a full date, and never shown on your profile. We use it to set age-appropriate safety defaults: under-18 accounts are friends-only by default, are not indexed by search engines, show as "A reader" to logged-out visitors on the forum, and have usage analytics and personalised recommendations off. It is needed before you can post. Basis: legal obligation (the Online Safety Act duties to children) and legitimate interests (keeping children safe).
  • Library metadata. Titles, reading status and chapter progress that the extension or app syncs, the source site and link for each title, and the volumes you mark as owned or wanted. The source site name and link, and any private notes you add, are stored encrypted at rest. Never the pages you read, never the sites' content. Basis: contract.
  • Imports from AniList and Goodreads. Only when you start them, from Settings. If you connect AniList, we store the access token AniList gives us, encrypted, and use it for two things only: reading your AniList manga list when you press import, and, if you switch it on, updating an entry on your AniList when you change its status or rating, or add the title, on weeb.ltd. It is never used for anything else, never shared, and is deleted when you disconnect. If you upload a Goodreads export, we read the file once to add those books to your library and keep only the resulting library entries (title, author, shelf as a reading status, your rating); the file itself, and the reviews and notes in it, are not stored. Basis: contract, to provide the import you asked for.
  • Community. Threads, replies, reviews (a review is a thread with the rating you gave the title), votes, follows, friends, blocks, mutes, clubs, reports, appeals and the profile fields you fill in. Basis: contract for the features you use; legitimate interests for keeping the community safe.
  • Community reading statistics. Trending and community picks count reading activity across members in aggregate, so no one can be picked out from them. Leaderboards list only adult members who share their stats publicly; to leave them, turn off "Show reading stats" in Settings, Profile. Basis: legitimate interests.
  • Scales, the Hoard and badges. Scales are an earned-only points currency with no cash value. We keep a ledger of what you earned and spent, your balance, per-title reading high-water marks (so re-reading does not earn twice), daily earning caps, the cosmetic items you own and equip, awards you give, the badges you earn and pin, and flags our anti-farming checks raise for a person to review. Nothing is decided automatically against you from a flag. Basis: contract.
  • Referrals. Who invited whom, and when the invitation was confirmed, so the inviter can be rewarded. When an adult member shares a page with the share buttons, the link carries their handle so a friend can join through their invite. The friend's browser stores nothing unless they choose to join that way. Basis: contract.
  • Sign-up signals. When you sign up we keep a one-way hash of your network (the first three parts of your IP address) and of your browser type, never the raw values, for 90 days. They catch referral fraud and waves of fake accounts. Basis: legitimate interests (preventing abuse).
  • Automated moderation. Every thread and reply is screened when it is posted: for slurs, links, contact details (always refused when aimed at an under-18), grooming patterns, piracy, duplicates and spam, with rate limits per account. Screening can refuse a post, hold it for a moderator, or open a moderation case. Moderator decisions and some blocked attempts add strike points, and a points ladder can apply a warning or a 24-hour posting mute on its own; anything stronger needs a moderator, and bans need an admin. Each member has a trust level from 0 to 3, recomputed daily from account age, approved posts, helpful votes, upheld reports, strikes and sanctions; it sets posting limits and how strictly links are checked. We keep which rule matched (not a copy of your post), and a one-way fingerprint of post text for 30 days to spot the same text posted across accounts. No outside moderation service or machine-learning classifier is used. Every outcome comes with a reason and an appeal route. The rules and tools are set out in the community guidelines. Basis: legitimate interests (a safe community) and legal obligation (Online Safety Act duties).
  • Discord. If you sign in with Discord, your Discord account id is linked to your account. If you also switch on Discord role sharing in Settings (off by default), our Discord bot can look up your username, staff role, supporter status and your Aura, reader and Hoard levels to give you matching roles on our Discord server. Turn the switch off and those lookups stop; the bot can still learn whether a Discord account is linked to a weeb.ltd account at all, which it needs for invite rewards. For safety, a sanction on weeb.ltd can be applied to a linked Discord account. When staff confirm or fix a bug you reported on our Discord, the bot sends your Discord id, the bug reference and the bounty amount so we can pay the bounty in Scales to your linked account. During a Discord invite contest, the bot sends the inviter's Discord id, the invited member's Discord id and the reward amount so we can pay the inviter in Scales; if the invited member came through the inviter's weeb.ltd referral link, we check that so one signup is not rewarded twice. Basis: consent for role sharing; legitimate interests for safety and for paying bug bounties and invite rewards.
  • Usage analytics. How you use the apps and site: screen and feature views, taps, app version, platform and coarse locale. It is first-party and self-hosted. Apps send a random install id, which our server discards on arrival; events are counted per day and not stored against you or your account. It is never sold and never shared for anyone else's purposes. It carries no reading content and no free text. This is on by default for adult accounts so a small team can see what to fix and build; it is off for under-18 accounts. Basis: legitimate interests (Article 6(1)(f)). You can object and turn it off at any time in Settings on weeb.ltd; one switch covers the site, extension and mobile app. Marketing stays strictly opt-in. The Android app also reports its build number and, once each, that it was installed or updated, and once a day that it was used; we keep these only as daily totals per build. Downloading the Android app from this site adds one to a daily total per build. Your IP address is held in memory for a few minutes so a repeat tap is not counted twice, and is not written to the count.
  • Site visit statistics. To count daily and monthly visitors and see where they come from, we run our own copy of Umami on our own server; nobody else receives this data. For each page view on weeb.ltd it records the page address, the referring site, campaign tags, browser, operating system, device type, screen size, language, and the country, region and city worked out from your IP address. Your IP address is not stored: together with your browser details it produces a random visitor id that changes each month and is not linked to your account. It uses no cookies and stores nothing on your device. A visit is only counted once you move the mouse, tap, scroll or type, so automated browsers are left out; nothing about those movements is sent or kept. Private pages such as settings are never recorded, profile addresses are grouped, and if you are signed in your title pages are grouped too, so it holds no reading content for members. Accounts that are under 18, have no birth year, or have turned usage analytics off are not counted, and it stops if your browser sends a Global Privacy Control or Do Not Track signal. Basis: legitimate interests (Article 6(1)(f)).
  • Discover load times. When an adult member opens Discover, we record how long it took to load, whether they were signed in, and whether they were on a phone or desktop. It is not linked to your account. We keep it for 30 days. Your IP address is used in memory only, to limit abuse, and is not stored. We don't collect this from under-18 or unknown-age accounts, anyone who has turned analytics off, or browsers sending Do Not Track or Global Privacy Control.
  • Security records. Session IP addresses (shown masked in your session list, in full in your data export), browser type, sign-in times, and an audit log of moderation and account actions. Basis: legitimate interests in preventing abuse.
  • Supporter payments. Handled by Stripe. We keep your Stripe customer id and subscription state, never card details. Basis: contract.

The browser extension

  • It runs on your own device and reads only the pages of the third-party sites you choose to open. What is on those pages stays on your device and is never sent to us. Your library (which titles you read, where and how far) also stays on your device unless you link an account, as set out below.
  • Checking for new chapters. The extension asks the sites you track directly from your browser, so those sites see your IP address, as they do when you visit them. Some checks open the site in a hidden tab, which uses your own cookies for that site. Covers and downloads come from those sites or their image hosts.
  • Title lookups. To fill in covers, genres and status, the extension automatically looks up the titles in your library on AniList. Each lookup sends only the title. It carries no account, reading progress or anything else about you. This runs for every library and has no switch.
  • Covers in search and suggestions load straight from the catalogue image servers (AniList and MyAnimeList), which see your IP address with each image request, and nothing else about you.
  • Detect on all sites is an optional setting, off unless you turn it on. When on, the extension may run on any site, but only looks at pages whose address looks like a chapter. It reads the page title, links and image sizes on your device to decide whether the page is a reader. On a page it does not recognise as a reader, nothing it read is sent anywhere or kept. On a page it recognises as a reader, the panel appears and, while "Auto-add manga" is on (the default), the title, the page address and your progress are saved to your library like any title you read: on your device, and synced only if you have linked an account. Turn Auto-add manga off to save a title only when you press Track. The site itself is only followed (checked for new chapters) when you press Track, or when you have switched on "Follow recognised sites automatically". You can turn Detect on all sites off in the extension's settings or in your browser's extension permissions.
  • Without an account it keeps your library, reading progress and settings locally only.
  • If you link a weeb.ltd account, it uploads library metadata (titles, source links, AniList ids, reading status, chapter progress and when you last read) and the per-title fields you set (notes, tags, content flags, ratings, reader preferences) so they sync across your devices. On our server the source links, the site name and your notes are stored encrypted at rest. Removals are synced too, so a title you delete disappears on your other devices. It never uploads page images or the content you read. The device's name is the one you give it on weeb.ltd when you link it.
  • Backups you set up yourself. Both are off until you add your own token. GitHub backup saves your full library export (titles, chapter links, history, bookmarks, added sites, and your source names and their order) to a secret gist on your own GitHub account. A secret gist is unlisted, but anyone who has its link can open it. AniList list sync uses your own AniList token to update your AniList list: progress, status, and adding or removing entries.
  • Usage analytics (which screens and features you use) are first-party and self-hosted. On Chrome they start only after you make the choice shown when the extension first runs. On Firefox they are off unless you allow them when installing, or later in the browser's add-on permissions. If your extension is linked to an account, analytics requests carry the device's link so we can apply that account's choices: your weeb.ltd opt-out, and no analytics for under-18 accounts.
  • Community stats are off until you agree on the card the extension shows you. When on, it sends our community server your reading activity (the title, its genres, the site it was read on as a short name, not a link, the chapter number or a short id, and the day) and the ratings you give, under a username you pick or an anonymous one it makes up, plus a random install id with the browser and version. The server works out your achievements from your reads. These feed the community's trending, genre and top-rated lists and a weekly leaderboard. Members we know are under 18 never appear on the leaderboard. Opening a title's community stats sends that title with nothing about you. We keep this data until you delete it, from the extension's community settings, or by deleting your weeb.ltd account if you linked the extension to it. If you linked it, your weeb.ltd data export includes it. Basis: consent.
  • On weeb.ltd pages, the extension tells the page its version and whether it is linked, so the site can show the right buttons.
  • It checks GitHub for updates and fetches the official-sites list from weeb.ltd once a day. Those requests carry only what any web request does (an IP address and the version), and are not used to profile you.

The mobile app

  • The StoryHoard mobile app stores your library, tracking and ownership in your account so they sync with the extension and the website, and keeps a few app preferences (such as the genres you picked when you started) with your settings. It talks only to weeb.ltd for your account data. Usage analytics are on by default for adult accounts, on the same legitimate-interest basis, and the same weeb.ltd account opt-out switches them off here too; anything an under-18 account sends is discarded on arrival.
  • When it looks up a book, the app asks Open Library directly from your phone, which sees your IP address and the title. If you allow notifications, your phone gets a push address from Expo, the app platform; we do not store it.

Our Discord server

  • Levels. Our Discord bot counts your messages, voice minutes and streaks on our server to give you XP and levels. It keeps a daily XP breakdown for 400 days and the record of each XP award for 30 days. Your level is kept while you are on the server and deleted 90 days after you leave. Basis: legitimate interests.
  • Moderation. When a message is edited or deleted, the bot posts a copy of its text in a channel only our moderators can see, and those copies are removed after 90 days. Strikes and escalations are kept 180 days; warnings are kept. Basis: legitimate interests (a safe server).
  • Bug reports you post in our bug channel are saved with their replies and screenshots, and deleted 90 days after the bug is closed.
  • Ko-fi. When you support us on Ko-fi, Ko-fi tells the bot the amount, currency, tier and time, and the name and message only if you chose to make them public on Ko-fi. We never receive your email or payment details. The public name and message are deleted after 30 days; your Discord id, once matched to a payment, is deleted after 730 days unless you are still a supporter.
  • Forget me. The bot's /privacy forget-me command deletes your levels, XP history, bug reports and their screenshots, and everything else the bot keeps about you, straight away. Your Ko-fi payments stay only as amount, currency, tier and time, with your Discord id, name and message removed, so nothing links them to you. Two things stay: moderation records, kept for the server's safety for the times above, and the moderators' copies of edited or deleted messages, which the command cannot reach and which are removed on the 90-day schedule.
  • The bot keeps 14 daily backups of its own data, so anything deleted is gone from them within 14 days.

How long we keep it

DataKept for
Account (email, username, sign-in provider)Until you delete the account, plus a 7-day undo window
Birth year and settingsUntil you delete the account
AniList link (the access token, stored encrypted)Until you disconnect AniList in Settings or delete the account. AniList itself expires the token after a year
Goodreads export file you uploadNot kept: read once during the import, then discarded
Synced library and collectionUntil you delete the item or the account; the marker that tells your other devices an item was deleted is kept 90 days
Discord server levels and XPWhile you are on the server; deleted 90 days after you leave. Daily XP breakdown 400 days, XP award records 30 days
Discord moderators' copies of edited or deleted messages90 days
Discord bug reports and screenshots90 days after the bug is closed
Ko-fi supporter recordsPublic name and message 30 days; your matched Discord id 730 days unless you are still a supporter
Extension community stats (reading activity, ratings, achievements, install pings)Until you delete them in the extension, or delete the weeb.ltd account they are linked to
Forum threads, replies and reviewsKept while you have an account. When the account is purged, the title, text and author become [deleted] and earlier versions are deleted
Removed threads and repliesThe text is deleted 90 days after removal, unless an appeal or a moderation case about it is still open
Earlier versions of edited posts400 days, or sooner if the post is removed or the account is purged
Sessions30 days of inactivity, then removed
Device (extension and app) tokensUntil revoked; revoked tokens are removed after 90 days
Notifications90 days
Reports, moderation cases and appeals400 days after they are closed; open ones are kept until they are decided
Audit log of moderation and account actions400 days
Automated moderation signals400 days
Strikes180 days (they count for 30 days)
Text fingerprints (one-way hashes of post text)30 days
Rate-limit countersAn hour to a day; any network address in them is a salted hash
Trust levelRecomputed daily while you have an account
SanctionsKept with the account; after deletion, a hash of a banned email and the ban reason are kept until the ban ends, or permanently for a permanent ban
Previous usernames90 days, so old links redirect and nobody can squat the name
Sign-up signals (hashed network and browser)90 days
Server logs (errors and events; can include an account id or IP address)Rotated out by size (about 50 MB per service), not by a fixed date
Browsers you have signed in from (a hashed device marker, the browser and system name, a hashed network)400 days after that browser last signs in
Scales, Hoard items, badges and referralsWhile you have an account
Wallet review flags400 days after they are reviewed
Supporter paymentsYour Stripe customer and subscription ids while you have an account; Stripe keeps its own payment records for as long as tax and accounting law requires
Profile pictures (when uploads are switched on)While you have an account. A picture removed as suspected child sexual abuse material is kept, staff-only, as evidence for a report to the authorities, with a record of who uploaded it and why it was removed; that record is kept for 2 years, even after the account is deleted
Usage analyticsAggregated on collection (counts per day, app, version, build and feature, and Android APK downloads per day and build); no per-install rows are kept, and aggregates are held up to 12 months
Site visit statistics12 months, then deleted. The visitor id inside them changes each month and is not linked to an account
Discover load times30 days, then deleted. Not linked to your account
Trending and news snapshots14 to 30 days; they contain no personal data
Database backupsDaily copies 14 days, weekly 8 weeks, monthly about 3 months, on the same server. The last 14 daily copies are also kept, encrypted with a key only the owner holds, in a private GitHub repository. Every backup copy rolls off within 92 days, so deleted data is gone from backups by then

Daily jobs enforce these windows; the console shows the owner when one has not run.

Who else sees it

  • Resend sends our email (account, security and the optional emails described above). It also receives email sent to any @weeb.ltd address, including privacy requests, and we forward each message, with its attachments, to the owner's private inbox.
  • Stripe processes supporter payments.
  • Google, Discord and AniList handle sign-in when you choose them, and receive what any sign-in needs. If you connect AniList for importing, AniList also sees our requests for your list and, only with the push switch on, the status, rating or new entry we write to it for you. Our Discord bot reads the role information described above only if you switch role sharing on.
  • Title and news sources (AniList, MangaDex, MangaUpdates, MyAnimeList through Jikan, Google Books, Google Play, Open Library, WorldCat, Anime News Network and Crunchyroll news) provide title, volume, cover and news information. Our server asks them about titles, never about you. The browser extension also asks AniList about the titles in your library, directly from your browser, so AniList sees your IP address with those title lookups. Covers are fetched by our server and served from weeb.ltd, so those sites do not see your address; for a cover that came from a reading site, our server may also open that title's page on the reading site to find the cover. When the extension finds no cover for a title in your library, it can ask weeb.ltd, and our server may then look that title up on MangaUpdates: only the title is sent, never anything that links it to you or your account. One exception: the plain list view of your library loads covers directly from the site they came from, with no referrer, so that site sees a request from your browser.
  • GitHub answers the browser extension's update checks, and stores your library backup only if you set up GitHub backup with your own token.
  • Retailers and official readers receive nothing from us. A buy link takes you to their site; some links carry an affiliate tag, as the affiliate disclosure explains.

The server is in the European Union. We do not sell your personal data, and we do not share it with anyone not listed here unless the law requires it. If we add a new partner, it is named on this page before it receives anything.

International transfers

Resend, Stripe, Google, Discord, AniList, GitHub and Expo are based in, or process data in, the United States or other countries outside the UK and the European Economic Area. When your data goes to them, the transfer relies on an adequacy decision (for the US, the UK Extension to the EU-US Data Privacy Framework where the company is certified) or on the company's standard contractual clauses together with the UK International Data Transfer Addendum or the UK International Data Transfer Agreement. Write to privacy@weeb.ltd for a copy of the safeguard that applies.

Advertising and marketing

Today: weeb.ltd and the apps show no ads, and we place no advertising cookies or tracking pixels on the site. We do promote StoryHoard on other platforms, such as social networks and search engines.

  • Ads you see elsewhere. When you see or click one of our ads on another platform, that platform handles your data under its own privacy policy. We receive only aggregated campaign reports from them (for example, how many people clicked), not who you are.
  • Campaign links. Links from our ads and posts can carry campaign tags (such as utm_source) so we can count which campaigns bring visitors. These are recorded in the site visit statistics described above and follow the same rules.
  • If we add advertising or measurement partners later (for example Google Ads or Meta), we will name them here before they go live; load them only after you agree, wherever the law requires consent (including the UK and EU); give you a cookie settings control to change that choice at any time; and treat a Global Privacy Control signal from your browser as an opt-out.
  • What we will not do. Your reading history and library are never used to target ads without your separate, opt-in consent. Accounts of people under 18 are never used for ad targeting or shared with advertising partners.
  • Optional and marketing email. A few optional emails are about your own account on weeb.ltd: a welcome, Scales rewards, and an occasional nudge after a few weeks away. Adults get them unless they turn them off; members under 18 or who have not given a birth year get them only if they turn them on. Every one has a one-click unsubscribe, and you can change this any time in Settings. Any other marketing email is sent only if you opt in. Account email (verification, security, sign-in alerts, deletion notices) is not marketing.
  • US state privacy laws. We do not "sell" personal data or "share" it for cross-context behavioural advertising as those laws define the terms. If that ever changes, a "Your privacy choices" link will let you opt out, and browser opt-out signals will be honoured.

Cookies and similar technologies

  • Strictly necessary (always on). Your session, a short session cache, the sign-in state during a provider login, a two-factor step, a random device marker that lets us warn you when your account is signed in from a browser you have not used before, your theme, your chosen language (kept for a year), your chosen region for buy links, and an invite you chose to follow (kept for 30 days, or until you have an account). The site cannot work without these, so they do not need consent.
  • Analytics. The usage analytics and site visit statistics described above are first-party. They do not use cookies, and you can turn them off for your account in Settings.
  • Advertising and marketing. None today. If we ever use them, they stay off until you agree, and you can change your choice at any time from a cookie settings link at the bottom of every page.

Because only strictly necessary cookies are used today, there is no cookie banner. If we add anything that needs your consent, we will ask before it runs.

Children

The service is all-ages and readable without an account. Accounts are for people aged 13 or over, or older where your country sets a higher minimum age for digital consent; creating one confirms that. Under-18 accounts get the safety defaults described under Birth year. If a parent or guardian tells us a younger child has an account, we delete it. Write to privacy@weeb.ltd.

Your rights

  • Access and portability. Settings has an "Export my data" button that downloads everything we hold about you as one JSON file: account, settings, library, collection, posts and their earlier versions, social connections, notifications, Scales, badges, referrals, supporter status, moderation records about your own posts (strikes, cases, appeals), sessions with their full IP addresses, and your sign-up signal. It leaves out passwords and other secrets, and other people's identities (such as who reported you).
  • Correction. Profile and settings are yours to edit at any time.
  • Erasure. Settings has "Delete my account". Deletion is scheduled 7 days out: you are signed out everywhere, your profile and posts are hidden, and signing in again within that window cancels it. After the window your account, library and everything linked to it are removed. Your threads and replies stay as anonymous "[deleted]" entries (title and text included, earlier versions deleted) so other people's conversations keep their shape, and moderation cases about your posts no longer name you. What we keep: the audit log and reports or cases other members filed about your account, for their 400-day window; a hash of a banned email, so a ban cannot be cleared by deleting and re-registering; and a picture removed as suspected child sexual abuse material, with the record of who uploaded it, as evidence for 2 years. Stripe keeps its own payment records. Backup copies roll off within 92 days.
  • Objection and withdrawal. Every optional processing has a switch in Settings. Turn it off and the processing stops.
  • Complaints. Write to privacy@weeb.ltd first. You can also complain to your local data protection authority; in the UK that is the Information Commissioner's Office.

Security

Passwords are hashed and checked against known breaches at sign-up. Staff accounts require two-factor authentication. Sessions can be reviewed and revoked from Settings. The source links and site names in your library, and your private notes, are encrypted at rest with a key held outside the database. Cover image links are not encrypted. Report a vulnerability through security.txt.

Changes

When this page changes in a way that matters, the date at the top moves and the change is listed below. For significant changes to how your data is used, we also tell account holders by email or a notice on the site before the change takes effect. Where a change needs your consent, we ask for it rather than assume it.

  • 16 November 2026. Covers: when the browser extension finds no cover for a title, our server may look the title up on MangaUpdates. Only the title is sent, never anything about you. Browser extension section corrected: on a page Detect on all sites recognises as a reader, the title, page address and progress are saved to your library while Auto-add manga is on; covers in search and suggestions load from AniList and MyAnimeList; your GitHub backup also holds your source names and their order.
  • 15 November 2026. Share buttons: an adult member's shared links carry their handle so friends can join through their invite, and the invite cookie a friend sets by choosing to join that way is now listed with the other necessary cookies.
  • 8 November 2026. The record of who uploaded a picture removed as suspected child sexual abuse material is now kept for 2 years as evidence, even after the account is deleted.
  • 8 November 2026 (evening). New section on our Discord server: what the bot keeps for levels, moderation, bug reports and Ko-fi support, how long, and what the forget-me command clears.
  • 7 November 2026 (evening). The source links and site names in your library, and your private notes, are now stored encrypted at rest; a per-site code that reveals no site name lets features that group by site keep working. Nothing new is collected. Backups made before this change still hold the plain values until they roll off, within 92 days. Added the extension's community stats: what they send, that known under-18s never appear on the leaderboard, and that deleting a linked weeb.ltd account now deletes them too.
  • 7 November 2026. A full check of this page against what our code does. The browser extension section now covers chapter checks, automatic title lookups, the optional Detect on all sites setting, backups you set up yourself, and how analytics work on each browser. Added the encrypted off-site backup copies on GitHub, email we receive, the name and picture a sign-in provider gives us, the full list of title sources, server logs and the language cookie. Corrected the mobile app section, how covers load, what the Discord bot can see with role sharing off, and how analytics ids are handled.
  • 6 November 2026. Added the new sign-in alert: the device marker cookie, the browsers we remember for it and how long. Added the one-click unsubscribe to the weekly digest. Set out which optional emails adults get unless they turn them off, now including a nudge after a few weeks away.
  • 29 October 2026. Added imports from AniList and Goodreads: what the AniList link stores and does, that an uploaded Goodreads file is not kept, and how long each is kept. Sign-in tokens are now stored encrypted.
  • 9 October 2026. Named the controller. Added birth year, automated moderation, Scales, the Hoard, badges, referrals, reviews, sign-up signals, Discord role sharing and international transfers, which were in use but not described here. Set out a retention period for every kind of data, including backups, and described what the data export contains and what erasure keeps. Leaderboards now list only adult members who share their stats publicly.
  • 28 September 2026. Added the Advertising and marketing section and set out cookie categories, so the rules are clear before any advertising partner is ever used. Nothing we collect today changed.