Privacy

Using the directory requires no account, no email address and no personal information. It is a public index and you can read all of it anonymously.

What we don't collect

• No accounts, logins or profiles.
• No advertising trackers or third-party analytics scripts.
• No personal information, and nothing typed into the search box is tied to you.
• No cookies for tracking. There is nothing to consent to, which is why there is no cookie banner.

What we do record

We look at aggregate usage to work out what the catalogue is missing and what is broken: which searches return nothing, which filters get used, which categories and publishers get visited, and which endpoint links get clicked. This is measured in totals, not per person, and it is served by the same infrastructure that serves the site — Cloudflare — using its privacy-oriented analytics.

Server logs necessarily include IP addresses and user agents as part of handling a request. Those are retained briefly for security and operations, and searches are kept only in aggregate form. We do not build profiles, sell data, or share it with advertisers.

Search terms

Search terms can reveal what someone is researching, which is worth taking seriously. We keep aggregate counts of terms and of zero-result searches so the catalogue can be improved. We do not keep a log that ties a search to a person.

Outbound links

Every endpoint link opens the publisher's own website. Once you are there, their privacy policy applies, not ours — they may set their own cookies and log your visit. We do not add trackers to outbound links and we do not disguise where they go.

Contributions

Contributions happen through GitHub. If you submit an issue or a pull request, your GitHub identity and whatever you write there are public, and GitHub's own privacy terms apply. That is intentional: catalogue changes should be reviewable by anyone.

Contact

Privacy questions, corrections or takedown requests can go to the maintainers through the repository's issue tracker. For security reports, please follow SECURITY.md instead of opening a public issue.