The MaKoncertBot
The data-collecting robot of MaKoncert. If you see this name in your site's logs, this page tells you who we are, what we collect, under which rules, and how you can stop us or ask us to remove data.
In force from: 7 November 2026 · The Hungarian text prevails; this English version is an informational translation.
User-Agent
MaKoncertBot/1.0 (+https://makoncert.hu/bot; bot@makoncert.hu)1. Who runs it and what is it for?
MaKoncertBot is the robot of the makoncert.hu concert finder, a free, non-profit community project. Operated by Hajdú Patrik Zsolt. Contact: bot@makoncert.hu.
The robot collects listing data from publicly available concert pages (ticket sellers, venues, festivals) so that our visitors can find Hungarian concerts in one place and reach the ticket seller's page. It is not a general web search crawler: it visits a pre-selected list of known sites and, staying within each source, does not follow links to other parts of the internet. In addition it may open the official homepage given for an artist in MusicBrainz with a single request (at most once every 30 days) to check that it really belongs to the artist; it does not store that page's content.
2. What does it collect?
From events, facts: the event's title and type, the performers, the times (doors, start, end), the venue and its address, the ticket price and availability, the address of the ticket page and the event status. From descriptions we at most derive facts (for example the price); we do not take descriptive texts, reviews, content behind a login or personal data of users into the catalogue. We may store the address of an image found on a page, but we do not download or display the image; an image appears on our site only if it is the artist's Spotify picture, comes from Wikimedia Commons (under a free licence, with the author named) or from user submissions.
The raw content of a fetched page (the whole page, compressed) is kept for troubleshooting: of each page we keep only the latest copy, and older copies are deleted automatically after one day. As a supplement we query small amounts of public data from MusicBrainz, Wikidata, Wikimedia Commons, Spotify (Web API, the artist's picture) and OpenStreetMap Nominatim (based on artist and venue names, addresses and identifiers); we use the same identifier for those.
3. How does it behave?
- It always states its identifier (see above). It does not use a User-Agent disguised as a browser or another robot.
- Before requesting anything else from a host it downloads the host's robots.txt and caches it for 24 hours; it does not fetch disallowed addresses. It follows the rules of the group named MaKoncertBot, or failing that those of the * group, and it honours Crawl-delay.
- If robots.txt is unavailable with a 4xx error, that means no restrictions under the standard (RFC 9309). If it returns a 5xx error or cannot be reached, nothing is fetched from that host, and robots.txt is requested again after about a quarter of an hour; a 429 or 503 answer is treated like a block (see below).
- Per host only one request runs at a time, with at least 3 seconds between two requests; if robots.txt or the value set for the source asks for a longer pause, it follows that.
- By default most sources get a quick check roughly every two hours (adjustable per source between 1 and 24 hours) and a full pass once a week. One run sends a limited number of requests (by default at most 400) and stops after five errors in a row. The start of the runs is shifted by up to 20 minutes per source, and only a few sources are processed at the same time.
- In the quick checks it fetches event pages with conditional requests (If-None-Match, If-Modified-Since) where possible, to cause as little traffic as possible. It accepts at most 5 MB per response, gives up after 30 seconds, and follows at most 5 redirects, only within the same site.
- On a 403, 429 or 503 response it stops the run of that source at once and honours Retry-After (up to 7 days) in later runs too; without one it waits at least an hour. After a block (403) the source is paused and we are notified; if the block is intentional we switch the source off, and until then it makes at most one careful attempt every six hours. It never circumvents a block.
- It does not circumvent protections: no disguise tools, proxy rotation or CAPTCHA solving, it signs in to no account, and it does not download paid or login-protected content.
- No source uses a headless browser at the moment. If one is ever needed for a page whose content only exists after scripts run, it will send the same identifier, will not load images, media files or fonts, and will navigate only within that site.
4. How can you block it?
Adding an entry to your robots.txt is enough; we apply it on the next download (within 24 hours at most). A block can apply to a host or to a path: for example Disallow: /events/ excludes only that path.
User-agent: MaKoncertBot
Disallow: /We also treat robots.txt as a machine-readable reservation of rights against automated use of content: we do not touch the disallowed parts.
5. Removal request
If you want us not to collect data from your site, or to delete data we already hold, write to bot@makoncert.hu. We act on the request as soon as we can, usually within a few days: we switch the source off (within ten minutes at most no new run starts, while a pass already running may still finish), delete the ticket offers and raw page copies that came from it, take the events known only from it out of the catalogue, and then confirm in writing.
If the robot causes excessive load, write to the same address: we pause the source as soon as we can and look for a solution together.
6. Contact and coordination
For technical questions or complaints: bot@makoncert.hu. The operator's details are in the Imprint. We are happy to agree custom crawl rules or a direct data feed (API, iCal, feed), which means less load for both sides. If you want to identify the robot by IP address, write to us and we will tell you its current address.