Opening the stacks
Opening the stacks
Last updated: November 6, 2026
Heads up — you’re early. Tronix Library is in open beta. Things are changing fast: features appear, disappear, and mutate between visits. This privacy policy is our honest attempt to document current practices, but it’s a moving target right now. By using the system during this period, you’re acknowledging that you’re part of an experiment — a willing participant in something that’s still figuring itself out. We’ll settle down eventually. Until then, treat everything here as “accurate as of the last time we remembered to update it.”
The short version: We collect very little, by design. No tracking cookies, no ad networks. We count visits and a few actions without cookies, so we know what’s working. If you sign in, we store your account info, reading ledger, and conversation history so the Librarian can know you over time. Your queries pass through third-party AI providers to generate responses — we’re transparent about all of it below.
Tronix Library is a tool for thinking. It works better when people feel free to explore ideas without wondering who’s watching. So we built the system to know as little about you as possible — except for the things that make the experience genuinely better.
We require a Google sign-in to use the conversational features and personal library. That means we know your email address, name, and profile image from Google. We store your reading ledger and conversation history so the Librarian can remember what you’ve read and discussed. Beyond that, we count visits without cookies (see “Counting Visits” below), we don’t follow you as a person, and we don’t use cookies for anything except authentication. This isn’t a marketing stance — it’s a design decision.
When you sign in with Google, we create a user record in our database containing:
That’s the identity layer. It exists so the system can remember your preferences and reading history across sessions — not so we can market to you.
When you mark a book as “reading,” “want to read,” or “read,” that status is stored in our database linked to your user account. Optional ratings (1–5) are stored the same way. This data is used to:
When you send a message through any conversational interface, here’s what happens:
We store your conversation history. Messages you send and the Librarian’s responses are stored in our database, linked to your user account and organized into sessions. We also generate short AI-written summaries of past conversations. This serves two purposes:
We also maintain a separate operational log (endpoint, email, message, response) for debugging and analytics. This predates the conversation history feature and may be consolidated in the future.
If you want your conversation history or account deleted, contact us at the email below and we will remove everything.
When you browse the archive, knowledge graph, timeline, or concept pages, you’re interacting with static or server-rendered data. No queries are sent to AI providers. Apart from the visit count below, nothing about you is collected or transmitted. It’s just you reading a page.
We count visits and a few actions with PostHog, so we know what’s working: which pages people arrive on, whether they came from our Instagram, and when someone copies a share link or opens a bookstore link. No cookies, nothing stored in your browser, no screen recordings, no clicks captured beyond those few actions. To count you once a day, PostHog hashes your IP address and browser with a salt that changes daily, on its servers, then drops the IP. Page addresses (this one, and the one you came from) are sent without their query strings, except campaign tags (utm_). What we send with an action is a word or two (“amazon”, “work”), never what you typed, a name or an email, and these counts are never tied to your account, even when you’re signed in.
Semantic search queries are sent to Pinecone as vector embeddings and to the configured LLM provider for embedding generation. The same data flow as conversations applies.
Tronix Library relies on the following third-party services to function. When you use conversational features, your queries pass through these systems; when you read a page, only the visit count does:
Both providers offer API terms that generally prohibit using API inputs to train their models. We use these services through their standard APIs, not consumer-facing products. That said, we encourage you to review their policies directly — they’re their policies, not ours.
These providers may change as the project evolves. We’ll keep this list current. The commitment doesn’t change: we’ll always be transparent about where your data flows.
We do not use tracking cookies, advertising cookies, analytics cookies, or any third-party cookie. Counting visits uses no cookie and stores nothing in your browser.
To be explicit about what’s absent:
The data Tronix Library does store and process is about books, not people. The corpus metadata, knowledge graph, semantic embeddings, and chapter-level analysis are all about the texts in the library. This data is stored in JSON files on the server and in a Pinecone vector index.
Tronix Library is not directed at children under 13 and does not knowingly collect any personal information from children. Since we don’t collect personal information from anyone, this is straightforward — but we state it here for completeness and compliance.
If you’re in a jurisdiction with data protection laws (GDPR, CCPA, etc.), you have rights regarding your personal data. We store your account information (email, name, profile image), reading ledger, and conversation history as described above. You can request access to, correction of, or deletion of any of this data at any time.
Deleting your account will remove your user record, reading ledger, conversation history, and all associated data. The operational chat logs (which predate the account system) can be deleted separately on request.
For any privacy-related requests or questions, contact us at librarian@tronixlibrary.org.
Like any web service, Tronix Library’s hosting infrastructure generates standard server logs. These typically include IP addresses, request URLs, timestamps, HTTP status codes, and user agent strings. These are generated automatically by Vercel’s infrastructure and are subject to their retention policies.
We don’t actively mine or analyze these logs. They exist as a byproduct of how the internet works, not as a data collection strategy.
We take reasonable measures to protect the system: admin authentication uses HMAC-SHA256 signed tokens with timing-safe comparison, connections are encrypted via HTTPS, and administrative functions are protected behind authentication.
That said, this is a research project, not a bank. We use industry-standard practices appropriate to the sensitivity of the data involved — which is low, because we store very little.
If our data practices change, this policy will be updated before those changes take effect. The “last updated” date at the top will always reflect the most recent revision.
Since we don’t have your contact information (by design), we can’t notify you directly about changes. We encourage you to review this page periodically if you’re a regular user.