← Enuva

EnuvaBot

Last updated: 29 August 2026

Enuva turns news articles into short spoken briefings for individual readers. EnuvaBot fetches articles from publications our readers follow so that we can summarise them, and every briefing links back to the original article. This page is for publishers: it explains how to stop us, and how to reach a person if you want something removed.

How our crawler identifies itself

EnuvaBot/1.0 (+https://enuva.app/bot)

That token is on every request we make for an article page. Requests for your RSS or Atom feed — when a reader asks us to find your publication, and on the polling that follows — currently carry no Enuva token at all. We would rather tell you that than let you conclude the crawler you can see is the only one we run.

How to block us

We honour robots.txt when we fetch article pages — both rules addressed to EnuvaBot and rules addressed to *. To stop us fetching your articles, add this:

User-agent: EnuvaBot
Disallow: /

To exclude only part of your site, name those paths instead of /. We fetch robots.txt once per site per collection run, so a change takes effect on the run after you make it rather than part-way through one.

One limit worth stating plainly. That rule stops us fetching your article pages. It does not stop us polling a publicly listed RSS or Atom feed, which we request without identifying as EnuvaBot. If you want us to stop entirely, email us using the section below — excluding a publication stops feed collection too.

Asking us to remove something

Email contact@enuva.app. Tell us who you are, which publication or article this is about, and whether you want a specific briefing removed, your publication excluded from future briefings, or both.

We will acknowledge your message, act on it before debating the merits, and reply telling you what we removed or excluded and from when. Excluding a publication takes effect within minutes and does not wait for a software release: we stop collecting your feed, stop fetching your articles, and withdraw the briefings that used them.

Two tails are worth knowing about, because we would rather state them than have you discover them. Audio already sitting in a content-delivery cache can still be served for up to a day. And a briefing a reader had already downloaded before your request stays playable on that person’s own device, where we cannot reach it, until their app deletes it. That is normally 30 days, but the app deliberately keeps a briefing past that while it is still the reader’s copy for that day or is the one they are playing, so treat 30 days as the usual case rather than a guarantee.

What EnuvaBot does not do

• It fetches individual article pages. It does not crawl your site recursively.
• It does not archive or republish your articles. Article text is kept only long enough to write a briefing, then deleted — the window is 48 hours and a sweep runs every hour, so about two days at the outside.
• It does not log in, and it does not try to get around a paywall.