Visitor analytics
Every page loads a script from Umami, hosted at cloud.umami.is. It records the page you opened, the site you arrived from, your browser, operating system, device class and country. It sets no cookies and does not store your IP address, which is used only to derive the country and then discarded. Because the site sends a strict-origin-when-cross-origin referrer policy, Umami sees the referring site, not the full referring page.
This is the only third party that receives anything about you. Their own terms are at umami.is/privacy. To opt out, block that script: any content blocker does it, and the site works exactly the same without it.
What this site records itself
Two actions on a mod's page send a single message to this site: copying an install command, and clicking through to the source repository. The message carries the mod's numeric id and which of the two happened. Nothing else.
It is stored in a table called events, which has four columns: the mod id, the kind of event, the date, and a counter. There is no row per person. There is no IP address, no user agent, no session, no identifier of any sort, and no way to reconstruct one visit from another. Requests that look like a crawler are dropped before they are counted.
It exists because how many people actually take a mod is ten points of the ranking on this site, and a catalogue that ranks mods without that signal ranks them on popularity of the repository alone.
The stack is different again: the mods you add to it live in your browser's local storage and are never sent anywhere. The page asks this site for the cards to display, and that request carries mod ids, not you.
The command-line tool
When npx agentmods add installs a mod it reports the mod's slug and the word "install" to the same counter. It sends no path, no project name, no machine or user identifier, and nothing about your configuration. If the report fails it is dropped silently, because telemetry is never worth failing an install over.
Three ways to turn it off, any one of which is enough:
npx agentmods add <slug> --no-telemetry
DO_NOT_TRACK=1 npx agentmods add <slug>
AGENTMODS_NO_TELEMETRY=1 npx agentmods add <slug>DO_NOT_TRACK is honoured because it is the standard way to say this once, for every tool on the machine.
Watching a mod by email
This is the only place an address is stored, and it is stored only if you type one in. Asking to watch a mod records your email address, the date, and which mods you watch. Nothing more: no name, no IP address, no browser.
Your address is used for one thing, the digest telling you that a mod you watch changed. It is sent through Amazon Simple Email Service from [email protected], so that service handles the message in transit. Nothing is sold, and nothing is shared with anyone else.
Your IP address is looked at when you submit the form, to stop one machine from signing up thousands of addresses. It is held in memory for a few minutes and never written to the database.
Every mail carries two unsubscribe links. One stops a single mod. The other deletes your address and every watch attached to it, immediately and without asking anything further. Until you use one, the address is kept, because that is what makes the digests possible.
Repositories in the catalogue
The catalogue is built from public GitHub repositories. If you are the author of one, what is stored about it, and how to have it taken out, is on the crawler page.
Contact
agentmods is run by one person. Anything about this page, an address you want removed, or data you want a copy of: open an issue at github.com/iOSDevSK/agentmods/issues, or reply to any mail the site has sent you.