← Back to app

SupprBot

Sloe's identified recipe-import fetcher

Last updated July 2026v1.0Revision history ↗

This page exists because Sloe’s Terms of service and Help promise that when Sloe fetches a page on a user’s behalf, it identifies itself with a SupprBot user agent that links here. If you run a website and a request has arrived with that user agent, this page tells you what it is, why it’s there, and how to reach us.

What SupprBot is

SupprBot is the fetcher Sloe (getsloe.com and the Sloe mobile app) uses to read a public web page when a Sloe user asks to import a recipe from it. It is not a search-engine crawler, it does not browse your site on its own initiative, and it does not build an index. Each request corresponds to one Sloe user, at one moment, importing one URL they pasted into the app.

Why it fetches your page

When a Sloe user imports a recipe, SupprBot requests that single page, reads its structured recipe data (ingredients, steps, times, servings — typically the same schema.org/Recipe markup search engines already read) and hands it back to that user’s own private cookbook. Sloe does not copy your article’s prose or photos, does not republish your page, and does not run background or bulk crawls of your site. See the Importing recipes section of the Terms for the full posture.

How to identify it

SupprBot always sends the same, honest, static User-Agent header:

SupprBot/1.0 (+https://getsloe.com/bot)

It never rotates user agents and never sends a browser’s or another company’s bot string (for example a search engine’s or a social platform’s) — every request is truthfully labelled. SupprBot also never attempts to bypass a login wall, paywall, CAPTCHA, or other access control; if your page requires authentication, SupprBot cannot and will not read it.

How to block it

The reliable way to block SupprBot today is to match the exact User-Agent token SupprBot at your web server, CDN, or firewall, and reject or rate-limit those requests. Because the token is fixed and never spoofed, this works immediately with no code change on our side.

We do not yet parse or act on a robots.txt Disallow rule targeting User-agent: SupprBot before fetching — if you rely on a robots.txt entry to keep it out today, use User-Agent blocking above instead, or contact us and we’ll act on it manually in the meantime.

Contact

Questions about SupprBot, a request to be excluded, or anything else about how Sloe fetches your site: legal@getsloe.com. Include your domain and, if you have it, a sample request (timestamp and path) so we can confirm it was us.