Privacy
Last updated 2026-08-21.
Omnibus Readers is a comic-collection site: it tracks what you own, what you want, what you have read, and what other members are saying about it. Doing that means holding data about you. This page says what, why, for how long, and who else sees it — in the same detail we hold it.
What we collect
The table below is generated from the site's own list of every place your account id reaches a store, so it cannot quietly fall behind the code: a new kind of data cannot be added without being classified into one of these categories first.
Downloadable means at least part of that category comes down in your data download. The file itself lists what it left out and why.
| Category | What it holds | Why | How long |
|---|---|---|---|
| Account and sign-in Downloadable | Your email address, a hash of your password if you set one, the Google and Discord account identifiers you signed in with, your display name and profile settings, and any API keys you created. | To sign you in, to reach you about your account, and to attribute your activity to you. | Kept while the account exists. Deleting the account clears the email, password hash and both OAuth identifiers from the row, leaving a tombstone that keeps your authored content anonymous rather than orphaned. |
| Collection and wishlist Downloadable | The books on your shelf and wishlist, their state, condition and notes, the history of changes you made to them, and purchase history you chose to import from a retailer. | This is the feature. Your shelf is what the site is for. | Kept until you remove the rows or delete the account. |
| Reading log and progress Downloadable | What you have read and when, ratings and notes you attached, and your position in any reading order you are following. | To show you your own reading history and to drive reading-order progress. | Kept until you remove the entries or delete the account. |
| Follows, friends and notifications Downloadable | Who you follow, block and are friends with, the activity rows behind your public profile, and your notification inbox. | To build your feed, your friends list and the notifications you receive. | Kept until the relationship is removed or the account is deleted, at which point the edges pointing both ways go too. |
| Posts, comments, reviews and forums Downloadable | Everything you have posted publicly: posts, comments, reviews, forum threads, the votes and reactions you cast, and the feedback threads you follow. | To publish what you wrote and to order and rank it for other readers. | Public writing is kept after account deletion so the threads it anchors stay readable, with your identity masked. Your votes and reactions are removed. |
| Direct messages Downloadable | Your conversations with other members, including their contents. | To deliver the messages you send and show you the ones you received. | A conversation is the other member's record too, so it is kept after your account is deleted, with your identity masked. |
| Marketplace and giveaways Downloadable | Your listings and public wants, photographs you uploaded for a listing, completed transactions and the feedback attached to them, and any giveaway entries. | To run the member-to-member marketplace and give both sides a record of a trade. | Live listings and public wants are withdrawn when the account is deleted. A completed transaction and its feedback are the counterparty's record and are kept. |
| Catalog contributions and curation Downloadable | Corrections and additions you suggested, reading orders you curated, and -- if you hold a curator role -- a stamp on each catalog record you changed saying that you changed it. | To review a suggestion, credit a contribution, and let a later reviewer see who set a curated value so it can be re-reviewed or reverted. | Kept as catalog provenance after the account is deleted: a curated value with no provenance cannot be audited. |
| Recommendations and personalization Downloadable | Recommendations computed for you, the feedback you gave on them, your pairwise favourite rankings, puzzle results, and markers recording which feed items you have already seen. | To pick what to show you and to avoid showing you the same thing twice. | Derived rows are recomputed from your shelf and log and are removed when the account is deleted. |
| Usage measurement Downloadable | Searches run and results clicked, clicks on outbound store links, page-performance timings, and the request logs the server writes, which contain IP addresses and user agents. | To find searches that return nothing, to see which retailers are worth keeping, to find slow pages, and to run the site securely. | Search and click rows lose their link to your account when it is deleted; store-click rows otherwise expire after 180 or 365 days. Request logs expire on the log group's own retention. |
| AI assistant Downloadable | The transcript of any chat you had with the reading-log assistant, and a cost ledger recording what each request cost to run. | To answer follow-up questions in a conversation and to keep the feature affordable. | Transcripts are removed when the account is deleted and otherwise expire after 365 days. The cost ledger is kept as accounting, without the conversation. |
| Moderation and staff records | Reports you filed or that name your content, blocks applied to content, and an audit trail of moderator and administrator actions. | To act on reports and to keep staff actions reviewable afterwards. | Kept after account deletion: an audit trail exists precisely to outlive the person whose actions it records. |
Server logs
Every request to the site is logged with its IP address, user agent, path and timing, whether or not you are signed in. That is how the site is kept up and how abuse is spotted. These logs are not joined to your account and expire on their own schedule.
Cookies and measurement
A session cookie keeps you signed in, and a small number of preferences (your theme, for instance) are stored in your browser. Neither is used to track you elsewhere, and there is no advertising network on this site.
Pageviews, searches and clicks on outbound store links are counted with Umami, which measures without cookies and without a cross-site identifier, and which is served through this site's own domain rather than a third-party CDN. It is how we find searches that return nothing and retailers nobody uses.
You can turn that off. The switch below is honoured before the tracker is even fetched, and it is remembered in this browser — so it applies whether or not you have an account, and you will need to set it again on another device. If your browser sends Global Privacy Control or Do Not Track, that is honoured too and this switch will already be off.
Who else sees it
We do not sell your data and we do not share it for advertising. It reaches these companies because the site runs on them:
-
Amazon Web Services
Hosting, databases, file storage and outbound email.
Everything the site stores, because AWS is where it is stored. Server logs held there contain IP addresses and user agents.
-
Cloudflare
Content delivery, TLS and abuse protection at the edge.
Every request's IP address, user agent and URL, as the request passes through on its way to the site.
-
Google
Sign in with Google, and book metadata lookups.
If you sign in with Google: your Google account identifier and email. Metadata lookups send an ISBN or title, never your identity.
-
Discord
Sign in with Discord, role synchronisation and alert DMs.
If you link Discord: your Discord account identifier, and the server roles it grants you. Alerts you asked for are sent to you as Discord messages.
-
Stripe
Payments, if you take out a supporter subscription.
Your payment details go to Stripe directly and never reach this site's servers. We receive back only the fact that a subscription is active.
-
OpenRouter
Routing requests to the AI models behind the reading-log assistant.
The text of the conversation you have with the assistant, plus the parts of your reading log it needs to answer. Only if you use the assistant.
-
Umami
Counting pageviews, searches and outbound store clicks.
The page you are on and the event that fired. Umami measures without cookies and without a cross-site identifier, and the script is served through this site's own analytics gateway rather than from a third-party CDN.
Beyond that, we hand over data only when the law requires it, and where the site publishes something you wrote — a post, a review, a public profile — it is public by design.
Your choices
- Get a copy. Download your data as a JSON file. It names what it could not include and why.
- Correct it. Your profile, shelf, reading log and contributions are editable in the site itself.
- Control what is public. Profile visibility, shelf visibility, who can message you and who can follow you are all in settings.
- Stop being measured. The switch above, or your browser's Do Not Track / Global Privacy Control setting.
- Delete the account. The danger zone in settings. Deleting clears your email, password and linked Google and Discord identifiers, and removes your private data. Things that are somebody else's record too — a conversation, a completed trade, a thread your comment anchors — stay, with your identity masked. The retention column above says which is which, category by category.
Asking us
If you want to know exactly what we hold about you, want something removed that the download or the delete button does not cover, or think this page is wrong, raise it on the feedback board (sign-in required) or in the Discord.
Changes
When this page changes in substance, the date at the top changes with it. The data table changes on its own as the site does, which is the point of generating it.