Privacy Policy
Last updated 21 November 2026.
The short version
Minerals has no visitor accounts. The personal details it holds are the ones you enter in the Supply form, and what a listing shows about its maker: name, handle and portrait, as the maker publishes them. A maker page also records when it was opened and what its maker answered. The Supply form takes the link, what it is, best for, skip if, the registry or install address, the licence and what is free, whether you made it or are suggesting it, and your email address. A request can also be sent by an agent through the Minerals MCP. It carries an email address only if you give one. These details are used only to judge the request and to reply to you. They are kept until the request is answered and then deleted on request. To ask, write to hello@minerals.dev. It keeps a log of how the marketplace is used, so listings can be judged on whether they work. The log holds no name and no address. One exception: a request sent with an email keeps that email beside the install key it came through. Log entries are kept until you ask us to remove them.
What is logged
- Searches: the words of the need, the filters, which listings were shown, the number of refs the project already has, and which path asked (for example, the install guide’s first run).
- Site search: the words typed into the site’s own search box, and which listings matched.
- Handoffs: which listing an agent asked the pull for, and the client name it gave.
- Offers: which listing or item was offered, the answer, and the install key if there was one.
- Click-outs: which listing was clicked through to, and the page it came from.
- Reports: that an agent said it did not use a listing, and its reason if it gave one.
- Pulls: which item was pulled, the client or tool that fetched it, and the install key if there was one.
- Requests: the host of a suggested link. The request itself is kept apart from the log.
- Arrivals: that the server’s address was opened by a plain request. Nothing else.
- Guide reads: that the install guide was read, and the install key if its address carried one.
- Quiet failures: that a call was answered late or failed, and which tool it was.
- Failed sign-ins to the back office: the time only.
- Project labels: the stack names, project type and stage an agent sent.
- An install key, if the server was added with one, with the time of its first and its last call. It is a random string made without sign-up.
Minerals’ own log stores no IP address. The host, Vercel, sees the address of each request to serve it and to limit abuse. Code, file contents and repo names are not stored.
A maker page stores the answer its maker gives and any note they write. They are used only to update or remove the listing.
What is not stored
The words of a search are stored as written, so do not put personal or confidential details in a search.
In your browser
- Your choice of light or dark mode, and the install key made for this browser, are kept in the browser’s own storage. Neither is a tracking cookie.
- The curator’s back office uses a sign-in cookie. Visitors never receive it.
Who processes the data
The site is hosted by Vercel and the database is hosted by Neon, in Frankfurt. Both act as processors for Minerals. Clicking through to a supplier takes you to their site, under their privacy policy.
Your requests
If you believe the log holds something about you, or you want an install key and its events removed, write to hello@minerals.dev. More on what is logged and why: About.