How we source hackathon data

For each hackathon we store the facts needed to find it again: name, organiser, dates, registration deadline, location, mode, prize figure, tags, and the URL of the original listing. We also keep a short description and, where the platform publishes one, a logo or banner.

We do not collect participant data, submissions, judging information, private organiser data, or anything behind a login.

Data is read from publicly accessible endpoints only. Specifically:

• Public JSON endpoints the platform serves to its own website, where those are not restricted.
• Structured data the platform embeds in its own server-rendered public pages.
• In one case, the visible content of a public page, parsed as HTML.

Currently connected: Devpost, Unstop, Devfolio, Devnovate, MLH, WeMakeDevs.

These are enforced in code, not just stated here:

• robots.txt is fetched and honoured before every request. If a path is disallowed for our user agent, we do not request it. Where a platform disallows the route its data sits behind, that platform stays switched off — we currently have one adapter disabled for exactly this reason.
• We identify ourselves as HackathonHubBot/1.0 with a contact URL. We do not impersonate a browser to evade detection.
• We rate-limit ourselves to one request at a time per host, with a delay between requests, a timeout, and exponential backoff that honours Retry-After. A full refresh of every platform is a few dozen requests, roughly every six hours.
• We never authenticate, bypass a paywall, solve a CAPTCHA, or use a headless browser to reach content that is not publicly served.

Every listing names the platform it came from and links to it. The primary action on every hackathon is Register on the original site, which sends the visitor to the organiser's or platform's own page. We do not wrap that page, inject anything into it, strip its branding, or place advertising against it.

The effect is that we send traffic to source platforms rather than substituting for them.

Event facts — names, dates, deadlines, prize amounts, locations — are information, and we treat them as such. Where a platform or organiser has written original descriptive copy, we store a shortened extract for search and preview purposes, always accompanied by a link to the full original. We do not republish complete listing pages.

All trademarks, logos and event branding remain the property of their respective owners. Their use here identifies the source of a listing and does not imply any partnership, sponsorship or endorsement.

If you operate a platform or an event and want a listing corrected, removed, or your site excluded from future syncs, email mananmmaisheri23@gmail.com from an address at the relevant domain, telling us the URL involved.

We aim to action requests within 72 hours. We will comply with a reasonable removal or exclusion request without requiring a legal instrument, and we can block a domain at the crawler level so it is not read again. Adding HackathonHubBot to your robots.txt has the same effect automatically.

Listings are mirrors of third-party data and can be out of date, incomplete, or wrong. The original listing is always authoritative. Confirm dates, eligibility and deadlines on the source site before relying on them.

This page describes how this site operates. It is a statement of practice, not legal advice, and it does not create rights or obligations for anyone. It may be updated as the site changes.