Let's Ditch
LetsDitchBot — crawler information
This page describes the automated crawler operated by Let's Ditch (letsditch.com), referenced in its User-Agent string. If you operate a website this crawler has visited, this page should answer your questions about who we are and how to control our access.
Identity
| Name | LetsDitchBot |
| Operator | Let's Ditch (letsditch.com) |
| Purpose | Discovering and indexing public event and venue listings (concerts, activities, attractions) to power a local-outing recommendation service. We do not scrape personal data, and we are not building a general-purpose search index. |
| Current User-Agent | LetsDitchBot/1.0 (+https://letsditch.com/botinfo) |
| Contact | crawler@letsditch.com |
How we operate
- robots.txt is a hard rule, not a suggestion. We fetch and parse
robots.txtbefore crawling any site, re-check it periodically rather than trusting a single read forever, and never crawl a path it disallows. - We rate-limit ourselves conservatively per domain — at minimum one page
request per minute per site, slower still if a site's own
robots.txtdeclares a stricterCrawl-delay, coordinated across every one of our crawl workers so a site is never hit faster just because we're running more than one worker. - We do not attempt to bypass access controls. If a site presents a CAPTCHA, a Cloudflare challenge, or any other anti-automation measure, we stop crawling that site rather than trying to solve, replay, or evade it.
- We do not rotate IP addresses, use proxy networks, or spoof our identity to get around a block. If a site blocks us, that's the site's decision, and we respect it.
- We prefer structured data (schema.org/JSON-LD, sitemaps) over parsing rendered HTML wherever a site provides it, since it's lighter on both sides.
Requesting removal or a different policy
If you'd like LetsDitchBot to stop crawling your site entirely, add a Disallow rule
for it in your robots.txt and we'll honor it on our next check (weekly by
default). If you'd like us to crawl differently — faster, slower, a specific path only, or not
at all regardless of robots.txt — email
crawler@letsditch.com and we'll apply it manually.
Data handling
We retain the structured event/venue data we extract (names, dates, locations, descriptions) to power search results on letsditch.com. We do not collect or retain personal data about your site's visitors, and we do not republish your page content verbatim beyond what's needed to describe a listing (name, date, location, short description, a representative image where one is clearly licensed for that use).
← Back to letsditch.com