Privacy
What we collect, what we deliberately do not, and the controls you have.
Last updated: 7 July 2026
Who we are and where we run
LLM Torrents (llmtorrents.com) is operated by a single operator. Our application and the file servers that seed torrents run on infrastructure located in the European Union, so we treat the EU General Data Protection Regulation (GDPR) as applying to our processing of personal data.
Analytics
We use a self-hosted, cookieless analytics tool (Umami) to understand aggregate traffic. It is
served same-origin through a proxy on our own domain — there is no third-party analytics origin and
no cross-site request. It sets no cookies and does not build a cross-site profile of you. We honour
the browser Do Not Track (DNT) and Global Privacy Control
(Sec-GPC) signals: when either is set, the analytics script is not even loaded. There
is no Google Analytics or other third-party ad/analytics tracker.
Accounts and the data they hold
Browsing and downloading do not require an account. If you create one, we store the details needed to operate it: your email address and — depending on how you sign in — a hashed password, and, for GitHub or Google sign-in, an identifier from that provider and optionally an avatar URL. Email verification is required. Optional account data includes saved hardware profiles and notification preferences.
Cookies and local storage
- A first-party session cookie is used to keep you signed in and to protect forms against cross-site request forgery.
- If you use the hardware / rig tools without an account, your rig is saved in your browser's
localStorageso it survives reloads. It stays on your device. - For models whose license requires click-through acceptance, we record an acceptance so we can show the download links. For signed-in users this is tied to your account; for guests it is tied to your session and expires after 24 hours. These records may include your IP address and browser user-agent as a legal audit of the acceptance.
We separate transactional email (things you need, like verification and security messages) from marketing email. The weekly digest is a separate, opt-in subscription that uses double opt-in — you confirm via a link before it starts. Every marketing/digest email carries a one-click unsubscribe (RFC 8058) as well as an unsubscribe link, and unsubscribing takes effect immediately. If a message bounces or is marked as spam, we add that address to a suppression list so we stop mailing it.
We use a third-party email-delivery provider to send our mail, which processes recipient addresses and message metadata on our behalf. If you sign in with GitHub or Google, those providers process the sign-in on their own terms. We do not sell your data and do not share it with advertisers or ad networks.
We use a third-party email-delivery provider to send our mail, which processes recipient addresses and message metadata on our behalf. If you sign in with GitHub or Google, those providers process the sign-in on their own terms. We do not sell your data and do not share it with advertisers or ad networks.
Error tracking
To keep the site reliable we use self-hosted error tracking (a GlitchTip instance, via the Sentry
SDK). It is configured not to send personally-identifying request data by default
(send_default_pii is off), and it is inert unless a reporting endpoint is configured.
Your controls: export and deletion
From your privacy settings you can download a JSON export of your own account data, and you can delete your account yourself. Deletion anonymizes your account in place: we scrub identifying fields and remove login artifacts, private preferences, hardware profiles, and pledges. Some records are retained by design in anonymized form — for example, the fact that a license was accepted (kept for legal audit, with the identifying details removed) and aggregate download counts. Public contributions you made may remain, detached from your identity. Your email stays on the suppression list if it was there, so a later re-registration cannot re-mail an address that had bounced or complained.
Downloading over BitTorrent
When you download a listing with a BitTorrent client, your client connects directly to other peers in the swarm and announces to the tracker that coordinates it. As with all BitTorrent use, your IP address is visible to those peers and to the tracker. This is inherent to the protocol and outside our control; if that matters to you, take appropriate network precautions before joining a swarm.
Downloading over BitTorrent
When you download a listing with a BitTorrent client, your client connects directly to other peers in the swarm and announces to the tracker that coordinates it. As with all BitTorrent use, your IP address is visible to those peers and to the tracker. This is inherent to the protocol and outside our control; if that matters to you, take appropriate network precautions before joining a swarm.
Illegal or infringing content
To report content, including copyright complaints, use our takedown / notice-and-action process, which follows the US DMCA (17 U.S.C. §512) and the EU Digital Services Act (Article 16).
Changes and contact
We may update this page from time to time; the "last updated" date above reflects the current version. This page is provided in good faith and is not legal advice. For any privacy question, or to exercise your data rights, you can contact the site operator at [email protected].