TMDB
This website uses TMDB and the TMDB APIs but is not endorsed, certified, or otherwise approved by TMDB.Movie titles, posters, runtimes, release dates, and cast credits come from the TMDB API. The above string sits here, in our credits, where TMDB's developer FAQ asks for it; the site-wide footer links to this page. We comply with the TMDB API terms: attribution, no bulk redistribution of the dataset, and no inclusion in a training corpus. API responses are cached for up to 24 hours; a small set of derived facts we depend on (release dates, title matches, artwork references) is stored durably in our catalog with attribution.
Maps & geocoding
Interactive city maps use the Google Maps Platform maps SDK, rendered with Google's attribution, which we don't modify. The location search box and venue geocoding, turning a place name or address into coordinates, use OpenStreetMap's Nominatim service under its usage policy, with attribution to OpenStreetMap contributors.
OpenStreetMap
The city and ZIP autocomplete in our location pickers, and the coordinate lookup behind "use my location", are powered by OpenStreetMap data via Nominatim. OpenStreetMap data is available under the Open Database License (ODbL), and its cartography is licensed CC BY-SA 2.0. We query Nominatim server-side through our own proxy (identifying user-agent, per-IP rate limiting, and response caching) rather than calling it from the browser, per the Nominatim usage policy. We don't redistribute the underlying dataset.
GeoNames
Some of the ZIP codes our ZIP lookup recognizes, mostly smaller towns and PO box ZIPs, come from the GeoNames postal code dataset, which is available under the Creative Commons Attribution 4.0 License. We use it only to turn a ZIP code into an approximate location, and we don't redistribute the dataset.
Anthropic Claude
We use Claude for vet-pipeline flagging and copy summarization. Per Anthropic's commercial terms, we disclose this in our editorial policy. We don't claim model output as our own original reporting; AI-summarized event descriptions are clearly derived from the source link.
Our scraper
SeeItEarly runs a polite scraper. It identifies itself as:
User-Agent: Mozilla/5.0 … Chrome/120 (standard browser headers)
Being direct about this: our fetchers generally send standard browser-style headers rather than a self-identifying bot User-Agent, and they do not read robots.txt. What keeps them polite is throttling and scope: every page fetch goes through a per-origin limiter set to one request every two seconds by default (a few high-capacity APIs are configured faster), fetching targets the public listing pages we index, and new sources are tested against small samples first. If you'd like us to stop fetching your site entirely, become a partner (free). We'll flip the scraper off and credit you. Or email partners@seeitearly.com.
AI crawlers
Our robots.txt blocks three crawlers by name: CCBot (the Common Crawl training corpus), Bytespider (very high request volume), and Diffbot (resells extracted structured data, which would substitute for our listings directly). Every other crawler, including AI crawlers such as GPTBot, ClaudeBot, PerplexityBot and GoogleOther, is currently permitted to read public listings. We'd rather AI search engines surface a correctly attributed listing than fail to mention us; reach out if you think we have that balance wrong.