VoxUnoBot

What VoxUnoBot is

Every request VoxUnoBot makes names it with this User-Agent:

VoxUnoBot/1.0 (+https://voxuno.ai/bot)

Its product token in robots.txt is VoxUnoBot.

Our customers choose words and phrases to look for, each one a Monitor's Match term, and the Communities to look in. Once a day, VoxUnoBot looks in each Community for those terms and keeps the public posts that match, so our customers can read them and, if they choose, join the conversation on your site themselves. VoxUno never posts on anyone's behalf.

VoxUnoBot signs every request it sends with Web Bot Auth: HTTP Message Signatures (RFC 9421) with an Ed25519 key. Each request carries Signature-Agent, Signature-Input and Signature headers. We publish its public key at https://app.voxuno.ai/.well-known/http-message-signatures-directory, so you can verify that a request claiming to be VoxUnoBot really is. A signature only proves who is asking: your robots.txt still governs what VoxUnoBot collects from your site, and opting out works as described below.

What it fetches

To collect posts from a site, VoxUnoBot fetches:

• your robots.txt;
• your site's search, once for each Match term, or, where it can't use your search, your listing or feed of new posts (and, on a few sites, the page of each new post);
• a few automated checks when a site is added or reviewed: which forum software and version it runs, whether a Cloudflare challenge is in the way, and which feeds it has and how active they are;
• a weekly check that the site still answers;
• a monthly re-check of your robots.txt;
• your site's favicon, to show beside its posts.

VoxUnoBot also makes a few requests that aren't collection, and these don't read robots.txt:

• website analysis: when a customer starts a Project, VoxUnoBot reads the home page of the customer's own website and a few pages it links to;
• link checks: when a customer pastes a site's address, or a site is suggested to them, VoxUnoBot checks that the page exists;
• favicon fetches: the icon that labels a site's posts.

What governs collection

Two things govern whether VoxUnoBot collects from your site, and both must allow it:

• your robots.txt. VoxUnoBot obeys the group that names VoxUnoBot, and otherwise the * group. It reads robots.txt before each search or listing page it fetches. A site with no robots.txt allows everything; a robots.txt we can't read allows nothing.
• our team's approval. Anyone using VoxUno can paste the address of any site, but a new site waits in review until our team approves it, and our team doesn't approve a site whose robots.txt doesn't allow VoxUnoBot.

Once a site is approved, VoxUnoBot re-checks its robots.txt every month. If it no longer allows VoxUnoBot, collection from that site stops at once.

How to opt out

To stop VoxUnoBot collecting from your whole site, add this to your robots.txt:

User-agent: VoxUnoBot
Disallow: /

VoxUnoBot reads robots.txt before each search or listing page, so the change applies from its next visit. You can also disallow narrower paths. If you disallow only your search, VoxUnoBot reads your listing or feed of new posts instead, where robots.txt still allows it.

If you'd rather ask us, email bot@voxuno.ai and our team can stop collecting from your site.

Load limits

VoxUnoBot is built to stay light:

• each site has a daily request budget, and work over the budget waits for the next day;
• work is spread across the day, and when several customers look for the same term in the same Community, VoxUnoBot runs that search once for all of them;
• it makes at most one request at a time to a forum;
• it honours Retry-After and rate-limit headers by resting, and backs off when requests fail;
• it stops at once if it's blocked.

If VoxUnoBot is causing you trouble, email bot@voxuno.ai.

What it never does

VoxUnoBot never:

• tries to get past anti-bot protection, including Cloudflare's challenges;
• hides behind a spoofed User-Agent: it always names itself as VoxUnoBot;
• uses fake accounts;
• reads anything behind a login.

What it keeps

VoxUnoBot keeps only the posts that match one of our customers' Monitors. It reads other posts to find the matches, then discards them: they're never stored.

For each matching post, VoxUno keeps what a customer sees: the title, an excerpt around the match, the full text where your site gave it, the author's name or handle as shown on your site, the link, and when it was posted and collected.

VoxUno doesn't build profiles of the people who write posts, doesn't link an author's posts across sites, and infers nothing sensitive about them. A post is kept while a customer's Result refers to it. If a post is edited or deleted on your site, VoxUno's copy doesn't change, so to have it removed, ask us (see below).

The Privacy Notice has the full detail on what we keep, why and for how long.

API platforms

Some platforms are read through their official APIs, within each API's own limits: Hacker News, Bluesky, Stack Exchange, GitHub, DEV and others. robots.txt doesn't govern those requests, so a robots.txt rule isn't the way to opt out of them. Each platform's own terms and settings apply, and you can ask us to remove a post as described below.

Removal

To have a post removed from VoxUno, email bot@voxuno.ai if you run the site, or privacy@voxuno.ai if you wrote the post, with a link to it.

Our team deletes the post, and with it every customer's Result on it, saved ones included. That's the whole process. We keep no block list, so a removed post could be collected again if it matches a Monitor again. To stop collection from a whole site, use robots.txt as described above.

Contact

• Site owners writing about VoxUnoBot: bot@voxuno.ai
• Personal data and post removal: privacy@voxuno.ai
• Anything else: support@voxuno.ai

VoxUno is operated by Holden Labs LLC: