Privacy notice
This notice explains what personal data we handle on MaKoncert, what we use it for, who we share it with, how long we keep it and how you can exercise your rights. MaKoncert is a private individual's free, non-profit community project: we sell nothing and show no advertising, so we handle no payment data either. It is the information required by Articles 13 and 14 of the GDPR.
In force from: 7 November 2026 · The Hungarian text prevails; this English version is an informational translation.
1. Who handles your data?
The controller is Hajdú Patrik Zsolt, a private individual who develops and runs MaKoncert ("we"). MaKoncert is not a company or a business but a private individual's free, non-profit community project, with no commercial activity.
For every privacy question and request, reach us at hello@makoncert.hu. We send e-mail from two addresses: sign-in e-mails from noreply@makoncert.hu and notifications from ertesites@makoncert.hu. They are send-only, so if you want to reply, write to hello@makoncert.hu.
We have not appointed a data protection officer because Article 37 of the GDPR does not require one: we do not carry out large-scale regular and systematic monitoring, nor large-scale processing of special categories of data. We have no joint controllers.
This notice covers makoncert.hu, the features available to guests and to registered users, your account, connecting music accounts, and the notifications by e-mail and on the site. The data-collecting robot MaKoncertBot has its own page, /bot.
2. What we process, why, and on what legal basis
You can browse as a guest, without an account; we then record no personal data about you beyond the technical logs of your requests and the short-lived counters of the rate limit. Only you can create an account. The table lists, per activity, the data processed and the legal basis (Article 6(1) GDPR); retention periods are in section 6.
"Performance of a contract" here means the terms of use under which the service is free. Where data is needed for that (for example your e-mail address for sign-in), the registered-user features are not available without it; providing any other data is voluntary.
| Activity and purpose | Data processed | Legal basis |
|---|---|---|
| Browsing, security and error logs | IP address, timestamp, requested path, browser type (user agent), error message, logged by the network provider (Cloudflare) and the server. Purpose: security of the service, preventing abuse, troubleshooting. | Legitimate interest (Article 6(1)(f)) |
| Rate limiting (protection against excessive use) | A one-way hash made with a secret key (HMAC-SHA-256) of your IP address, or of the e-mail address entered for sign-in, in a short-lived counter; when you are signed in, some counters (for example those of submissions) are tied to your account identifier. | Legitimate interest (Article 6(1)(f)) |
| Account and sign-in | E-mail address, language, for Google sign-in the Google account identifier (if Google also passes on a name and a profile picture address, the authentication provider stores them), role, the time of accepting the terms of service and the version accepted, time of last activity (updated at most once a day while you are signed in), technical data of the session and the sign-in log (IP address, browser type). Purpose: signing in (sign-in link or Google), operating the account, proving the acceptance of the terms, deleting inactive accounts. | Performance of a contract (Article 6(1)(b)) |
| Settings | The home location you enter (town, coordinates or your browser's location, rounded to about 100 metres; label), radius, and whether you unsubscribed from the notification e-mails. The home location defaults to Budapest; you can change or delete it at any time. | Performance of a contract (Article 6(1)(b)) |
| "Near me" on the Concerts page as a guest (only when you click it) | When you click the button, your browser asks for permission to tell your location; your position is never asked for otherwise. Only your browser uses the position: it looks up the nearest Hungarian town or village in a built-in list, and only that place's name and coordinates are kept; the exact position is neither sent to us or anyone else nor stored. The place is remembered on your device (mk_saved_place) so the Map starts with it once you sign in. When you are signed in, "Near me" uses the home set in your settings (see the Settings row), where the home can also be deleted. | Consent (Article 6(1)(a)), given by clicking the button and on the browser's permission prompt |
| Followed artists, concert alerts, notifications | Followed and muted artists (with or without notifications), concert alerts (what we watch, a price limit), the content and state of notifications (e-mail, the Notifications page). Every notification e-mail carries an unsubscribe link; once you follow it, we send you no more notification e-mails. | Performance of a contract (Article 6(1)(b)) |
| Connecting music accounts (optional) | The artist list taken over from the provider (see section 9), the provider identifier, the display name and the access token (in an encrypted store). Purpose: taking over and regularly refreshing the artists you follow. | Consent (Article 6(1)(a)), given when connecting |
| Event submission and moderation | The data of the submitted event, the free-text note, the uploaded image (poster), the submitter's account, the moderator's decision and any reasons given. | Performance of a contract (Article 6(1)(b)) |
| Earlier submission without an account (possible until 7 November 2026) | The data of an event submitted without an account before 7 November 2026, the free-text note, the uploaded image (poster), the moderator's decision, any reasons given, the optional contact e-mail address the submitter entered (used only if the moderator has a question about the submission), and a one-way hash made with a secret key (HMAC-SHA-256) of the IP address, so that the moderator can see how many submissions came from the same source, but not the IP address itself. Since then, events can only be submitted with an account. | The event data: performance of a contract (Article 6(1)(b)), i.e. the service under the terms of use; the hash of the IP address: legitimate interest (Article 6(1)(f)), protection against abuse and against flooding the moderation queue; the e-mail address: consent (Article 6(1)(a)), given by entering it and withdrawable at any time at hello@makoncert.hu |
| Language model (OpenRouter, when switched on) | Tidying up public event data (for example splitting the performers out of an event title), putting the submitted note into a structured form for the moderator, and the moderation suggestion (see section 3). For these only text is sent: the note, or event, artist and venue names, dates and the domain name of a ticket link, and the text of the public Instagram posts of the venues that agreed in writing, from which we read the concerts they announce (with e-mail addresses and phone numbers masked, see section 8); we attach no data of your account (for example your e-mail address). If you use the "Fill in from a poster" step of the submission form, we send the poster image you pick (with everything visible on it) through OpenRouter to a language model that reads images, so that it reads the details of the event for the form; the request requires that it goes only to a model operator that neither stores it for its own purposes nor uses it for model development (as far as OpenRouter allows this), we do not store the image, only its hash and the details read from it, and we attach no data of your account to this either. We store the model's answer identified by a hash of the input, without any user identifier, and the moderation suggestion (codes and percentages), the model name and the moderator's final decision to measure accuracy. | Legitimate interest (Article 6(1)(f)): faster moderation and tidy public data; a moderator decides on a submission or asks the models to decide (see section 3) |
| Contact, complaints, data subject requests | Name, e-mail address, the content of the message, complaint or request, our reply, and what is needed to identify you. | For data subject requests legal obligation (Article 6(1)(c), Article 12 GDPR); otherwise legitimate interest (f) or performance of a contract (b) |
| Collecting public event data | Artist name, date, venue, ticket price, ticket link (see section 8). | Legitimate interest (Article 6(1)(f)) |
| Administration and logging | The log of administrator actions (who, what, when), moderation; when a submission is rejected, also the submitter's identifier and the reasons. | Legitimate interest (Article 6(1)(f)): investigating abuse and disputes |
| Register of deletion requests | The request to delete an account: the account identifier, the time of the request and of its completion, the reason (own request or inactivity). Purpose: proving the deletion, and making sure a deleted account does not come back after a restore from backup. | Legitimate interest (Article 6(1)(f)) |
| Backup | The encrypted daily backup of the database and of the uploaded posters (without the tokens of music accounts). Purpose: protection against data loss and disaster. | Legitimate interest (Article 6(1)(f)) |
We do not ask for special categories of data (for example data about health, religion or political opinion) and do not knowingly process them; please do not write such data, or other people's personal data, into the note of a submission. We draw no such conclusions from the artist list of a connected music account.
Where the data comes from:
- From you: what you enter when you create the account, in settings, in the submission form or in an e-mail.
- From Google, if you sign in with a Google account: your e-mail address and account identifier. If Google also passes on your name and the address of your profile picture (earlier sign-ins did), the authentication provider (Supabase) stores them; we do not use them.
- From music providers (where available: YouTube, including YouTube Music, and Spotify), only within the permission you give when connecting: the list of artists you follow or listen to (details in section 9).
- From public sources: data about events, artists and venues (see section 8).
3. Automated decisions and profiling
We make no decision about you based solely on automated processing that produces legal effects concerning you or similarly significantly affects you (Article 22 GDPR). A moderator decides whether a submitted event is accepted or rejected: either directly, or through the "Let the AI decide" function of the moderation console, in which, at the moderator's request, the language models approve or reject a submission only if all the models asked agree; otherwise the submission waits for the moderator. You can ask for human review of such a decision too (see below).
A language model assists the moderators: from the title, artists, venue, date, the domain name of the given ticket link and the submitter's masked note (links, e-mail addresses and long digit runs are replaced by markers) of a submitted event (or of a suspected duplicate) it suggests whether it is a concert, whether it resembles an existing event, whether some data is incomplete or implausible, and how confident it is. The model may also put the submitted note into a structured form for the moderator; for that the note is sent masked in the same way (dates are kept). The suggestion is informational only: by itself it never approves, rejects or merges anything; a decision can result from it only in the way described above, started by a moderator. You can ask for human review, express your point of view and contest the decision at hello@makoncert.hu.
For public event data the language model and automatic matching may work without human approval (for example splitting the performers out of an event title, or merging listings of the same concert that come from different sources); these are not decisions about you.
We compile your notifications from the artists you follow, and on the My artists page we also suggest similar artists; if you ask for it in settings, the suggestions also go into the digest e-mail. This is part of the service, simple profiling with no legal effect; you can switch off the suggestions sent by e-mail in settings at any time. There is no advertising and no paid promotion: nobody can buy which concerts are shown or in what order.
4. Who receives the data?
The providers below work on our behalf (processors, Article 28 GDPR), under data processing terms that are part of their contract terms or concluded with them separately; the exception is OpenRouter, which acts under its own terms (see the table). The table lists the providers of the live service; those used only by a feature that has to be switched on are marked. Beyond that we disclose personal data only where the law requires it (for example an authority request) or you ask us to.
| Provider | Task | Location and basis of transfer |
|---|---|---|
| Supabase (Supabase Pte. Ltd.) | Database, authentication (sign-in, sending the sign-in e-mails), file storage (your browser loads submitted images directly from here), encrypted store for tokens | EU, Frankfurt. The contracting entity is in Singapore, and support access by the group from outside the EEA is possible: standard contractual clauses (SCC) |
| Cloudflare (Cloudflare, Inc.) | Content delivery (CDN), DNS, the tunnel that serves the website (Tunnel), bot protection (Turnstile, when switched on) | Global network, US company: EU-US Data Privacy Framework (adequacy decision), SCC as a fallback |
| Oracle (Oracle Cloud Infrastructure) | In the live service: the web server, background processes (data collection, notifications) and storage of the encrypted database backups | Germany (Frankfurt, EU) |
| Resend | Delivering e-mail: sign-in e-mails (noreply@makoncert.hu) and notifications (ertesites@makoncert.hu) | USA: EU-US Data Privacy Framework (adequacy decision), SCC as a fallback |
| OpenRouter (OpenRouter, Inc.) | Broker for language models (free models), when switched on, for the purposes described in section 2. OpenRouter and the operator of the selected model handle the request under their own terms; for requests that hold a submission, a poster image or an Instagram post we require that they go only to a model operator that neither stores requests for its own purposes nor uses them for model development (as far as OpenRouter allows this), requests with public event data only may go without that condition, and we send only the text listed in section 2 (for filling in from a poster, the poster image you pick) and never attach data of your account (for example your e-mail address) | USA; the model operator may be in the USA or another country. The transfer is subject to the own terms of OpenRouter and of the model operators |
Independent controllers, under their own notices: Google (for Google sign-in, for the YouTube connection and for the Google Maps map of the venue and concert pages, see below) and Spotify (Spotify AB) when you connect your account to them (see section 9). With every request that holds a submission or a poster image we instruct OpenRouter to route it only to model operators that do not collect requests (do not store them for their own purposes or use them for model development), as far as OpenRouter's settings allow. Requests that tidy up public event data (event title, venue, time, performer names, the structure of source pages, no personal data) may also go to a free model whose operator stores requests for its own purposes or uses them for model development; even so, OpenRouter and the model operators handle requests under their own terms, which is why we ask you not to write personal data into the note of a submission.
For some features your browser contacts an external provider directly, which then receives your IP address and the usual browser data; we do not receive this:
- Map: on the Map page for signed-in users, the OpenFreeMap tile server (tiles.openfreemap.org; operated by Hyperknot Software Kft. in Hungary), which according to its own notice does not log IP addresses by default (it may do so temporarily during a security incident) and uses no cookies. The map of the venue and concert pages is Google Maps (see below). Legal basis: legitimate interest (Article 6(1)(f)), showing the map.
- Google Maps map (on the venue and concert pages, only with your consent): the map is provided by Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland) and Google LLC (1600 Amphitheatre Parkway, Mountain View, CA 94043, USA) as independent controllers, under their own privacy policy (https://policies.google.com/privacy). The map only loads once you choose "Accept" in the question shown on your first visit, or "Load map" in the place of the map; until then your browser requests nothing from Google and the place of the map shows a drawing. When it loads, your browser contacts Google directly, which receives your IP address and browser data and may set cookies on its own domain (https://policies.google.com/technologies/cookies). We keep your choice for 30 days in the mk_maps_consent cookie (section 7), then ask again. Legal basis: your consent (Article 6(1)(a)), which you can withdraw at any time with the "Change settings" button of the "Cookies and browser storage" section (the "Cookie settings" link in the footer leads there); this does not affect earlier loads.
- Sign-in protection (only when switched on): the Cloudflare Turnstile bot check (challenges.cloudflare.com) on the sign-in page, which processes technical data (IP address, browser data). Legal basis: legitimate interest (Article 6(1)(f)), protecting sign-in against abuse.
- Sign-in and authorisation: for Google sign-in your browser goes to Google's sign-in page and from there back to us, and when you connect a music account, to the provider's own authorisation page (Google, Spotify). The provider's notice applies there, and it may set cookies on its own domain.
5. Transfers outside the EEA
As a rule we store data in the European Economic Area: the database and files are in the Supabase Frankfurt (EU) region, and in the live service the website, the background processes and the backups are on an Oracle server in Frankfurt (Germany). The operator also keeps a copy of the encrypted backups on their own computer in Hungary.
Data may reach countries outside the EEA (mainly the United States, in Supabase's case also Singapore) when Cloudflare's globally distributed network serves your request (your IP address and request data pass through it); when Resend delivers an e-mail to you; when OpenRouter and the operator of the model it selects process the text or poster image sent to the language model; when you agree to load the Google Maps map on the venue and concert pages (which Google does as an independent controller, under its own safeguards); or when the group companies of Supabase outside the EEA (support, operations) access data stored in its EU data centre.
Basis for the transfer: where the provider is certified under the EU-US Data Privacy Framework (at the time of writing, for example, Cloudflare and Resend), the European Commission's adequacy decision (Article 45 GDPR); otherwise (for example for Supabase's Singapore contracting entity) the Commission's standard contractual clauses (SCC, Article 46(2)(c)) contained in the provider's data processing terms, with supplementary measures where needed (EU region, encryption, minimising the data sent). OpenRouter and the model operators reached through it apply their own terms. You can ask for information about the safeguards and a copy of them at hello@makoncert.hu.
6. How long we keep data
Data tied to an account is kept until the account is deleted and then deleted, apart from the exceptions below. Expired data is deleted or irreversibly anonymised; the automatic deletions run daily in a background process. Technical helper data (for example caches and the queue of background jobs) may briefly hold copies of the data below; it is deleted automatically too.
| Data | Retention |
|---|---|
| Account data, settings, follows, concert alerts | Until the account is deleted. We carry out the deletion usually within minutes of your request, and within 7 days at the latest |
| Connected music account (provider identifier, name, token) | Until the connection is ended or the account is deleted; the token is then deleted at once. A connection whose access was revoked at the provider is deleted together with its token if you do not reconnect within 28 days |
| The artist list taken over from a music account and the follows that come from it | Refreshed at every sync (usually daily); a copy of the list left without refresh is deleted after 30 days. When the connection is ended, the list and the follows that came only from it are deleted at once (see section 9) |
| Inactive account | If you are not signed in on the site for 24 months, we notify you by e-mail; if you still do not sign in within 30 days after that, the account is deleted. If the notice cannot be delivered (for example the mail server refuses it), the account is deleted 30 days after the failed attempt. Admin accounts are not deleted for inactivity |
| Notifications (e-mail, the Notifications page) | 180 days |
| Messages of the Notifications page | 90 days |
| Submitted events | The event data (title, date, venue, artists, link) stays after the account is deleted but can no longer be linked to you. The note and uploaded images not yet published are deleted when the account is deleted, the image of a rejected submission after 30 days. The image of an accepted event stays as part of the event until you ask for its removal |
| Earlier submission without an account (until 7 November 2026): contact e-mail address and IP-address hash | The e-mail address is deleted 30 days after the moderator's decision, or at the latest 90 days after the submission if nobody decides; the IP-address hash is deleted after 14 days. The event data and the (unpublished or rejected) image are kept as in the row above |
| Raw pages fetched by the robot | Of each page we keep only the latest copy, older copies are deleted after 1 day; when a source is removed, its copies are deleted too |
| Rate-limit counters (hash) | 1 day |
| Security and error logs | Data of the network provider and the sign-in log for at most 30 days. Logs of the background processes are overwritten by size; they contain no e-mail addresses or tokens |
| Language model usage log and answers (with a hash of the input, without any user identifier) | 400 days |
| AI moderation suggestions (codes, percentages, model, the moderator's decision) | 400 days. The daily request counter is kept 40 days |
| Correspondence by e-mail, complaints, data subject requests | 2 years after the matter is closed |
| Log of administrator actions | 5 years; older entries are deleted automatically |
| Register of deletion requests | 180 days after the deletion is completed |
| Backup | 30 days. Deleted data can remain in the backup for that long; if we restore data from a backup, accounts deleted in the meantime are deleted again |
7. Cookies and browser storage
Our own cookies and browser storage are only those strictly necessary for the service to work or for a feature you explicitly ask for (for example remembering your language or appearance). Under § 155 of the Hungarian Electronic Communications Act (Eht., Act C of 2003) these need no consent. We ask for consent for one thing only: the Google Maps map of the venue and concert pages, because when it loads Google receives your IP address and may set cookies on its own domain (see section 4). A question about it appears on your first visit ("Accept" or "No thanks"); until you accept, the map does not load. The mk_maps_consent cookie keeps your choice for 30 days, then we ask again. You can change or withdraw it at any time with the "Change settings" button of the "Cookies and browser storage" section (the "Cookie settings" link in the footer leads there); when you withdraw it, the maps disappear at once and the mk_maps_consent cookie is deleted, so we ask again on your next visit. We have no advertising, tracking or profiling cookies.
You can delete cookies and browser storage in your browser at any time; you are then signed out, your language and appearance choices are lost, and we ask about the map again next time.
| Cookie / browser storage | Purpose | Duration |
|---|---|---|
| sb-lporkemibnfpnypmxcgz-auth-token | The signed-in session (Supabase). Created only after sign-in; HttpOnly, so scripts in the browser cannot read it. | Up to 400 days; deleted on sign-out |
| sb-lporkemibnfpnypmxcgz-auth-token-code-verifier | The security code of the sign-in (PKCE), which stops anyone else from completing your sign-in. HttpOnly. | Deleted when the sign-in completes; after an abandoned sign-in it can stay up to 400 days |
| mk_google_login | Security data of a Google sign-in in progress (a one-time identifier, the PKCE code and the page you return to), which stops anyone else from completing your sign-in. HttpOnly, valid only on the /auth/google path. Contains no personal data. | Deleted when the sign-in completes; after an abandoned sign-in at most 10 minutes |
| mk_signed_in_hint | Indicates that a signed-in session probably exists, so that the header does not flicker. Contains no personal data. | 30 days; deleted on sign-out |
| mk_login_email | The e-mail address entered when requesting a sign-in link, so that an expired link can be re-sent with one click. HttpOnly. | 15 minutes |
| mk_oauth_state_<provider> (mk_oauth_state_spotify or mk_oauth_state_youtube) | Security identifier of the connection of a music account (OAuth state). Signed, HttpOnly, valid only on the /api/connect path, single use. | 10 minutes |
| mk_locale | Remembers the language you chose or last viewed. | 1 year |
| mk_theme | Remembers the chosen appearance (light/dark); created only when you switch. | 1 year |
| mk_concert_scope | When signed in, your last "My artists | All" choice (mine or all), so that the posters of the home page, Concerts, the city pages and the Map open with it; created only when you switch. Your browser writes it, the Map page reads it. | 1 year; deleted on sign-out |
| mk_maps_consent | Your choice about the Google Maps map (maps: accepted, none: declined), so that we do not ask on every page. Your browser writes and reads it; our server does not process it. | 30 days; you can change it at any time with the "Change settings" button of the "Cookies and browser storage" section (the "Cookie settings" link in the footer leads there) |
| mk_saved_place (localStorage) | The name and coordinates of the nearest town or village found with the "Near me" button as a guest, so the Map starts with it once you sign in; it stays on the device and is not sent. | Until you delete it in the browser |
| mk_deploy_reloaded (sessionStorage) | If the page was open during an update, the tab reloads itself once so that the new version loads; this flag (the time of that reload) stops it from reloading again and again. It holds no personal data. | Until the browser tab is closed |
| mk_offline_pages_v3, mk_offline_static_v3 (Cache Storage, service worker) | When signed in, the last copy of the "My artists" page and the static files needed to show it, so that it can be read without internet. | The copy of the page is deleted at the first page load after sign-out; the static files (no personal data) stay until you delete them |
Sign-in protection (Cloudflare Turnstile, when switched on), the Google Maps map of the venue and concert pages (only once you accept it) and the external sign-in and authorisation pages may set cookies on their own domains; see section 4.
8. Public event data and the people in it
We collect concert data (event title, artists, date, venue, ticket price, ticket link) from publicly available sources with the MaKoncertBot robot; to identify artists we use public data of MusicBrainz and Wikidata, for artist pictures Spotify (Web API) and YouTube (YouTube Data API), and to place venues on a map the public data of OpenStreetMap Nominatim. Our own server downloads and stores the artist pictures and shows them from there, so your browser does not contact Spotify or YouTube. Legal basis: legitimate interest (Article 6(1)(f)), presenting the artist. An artist's name (and picture, if any) counts as personal data where the artist is a natural person. We send these services artist and venue names, addresses and identifiers; if you search for an artist while signed in, we may also pass the text you type to MusicBrainz, without any account data.
A few venues that agreed to it in writing publish their programme only on Instagram. We read theirs through the official developer interface of Meta (Meta Platforms Ireland Ltd.), the Instagram Business Discovery feature of the Graph API, with our Instagram account linked to the MaKoncert Facebook Page: we ask for the text, time and link of the venue's latest public posts, and we do not download any page of instagram.com. For this Meta receives only the venue's Instagram username. A language model reads the text of a post (see section 2) and takes from it the title, performers, date and ticket link of the concerts it announces. We do not store the text of the post, only the details read from it; the event page links to the post as its source.
Purpose: providing a concert discovery service. Legal basis: legitimate interest (Article 6(1)(f)). The balancing in short: the data is public, serves to inform the audience, and artists themselves want their concerts to be known; the impact on the individual is small. An artist or organiser can ask at hello@makoncert.hu for the data to be removed or changed, or object to its processing (Article 21 GDPR); we act on the request without undue delay and at the latest within one month (see section 11). This is the information required by Article 14 GDPR; notifying each individual would involve disproportionate effort (Article 14(5)(b)).
9. Connecting music accounts
Connecting a music account is optional; where a provider is available, you switch it on in the account settings. Because of Spotify's developer rules, the Spotify connection is currently available only to a closed test group. You give permission on the provider's own page; we change nothing in your account there, and we only fetch the following:
- YouTube (Google, YouTube Music included): the list of your channel subscriptions, with read-only access; of these we keep only music channels (official YouTube Music artist channels among them) and drop the rest at once. To identify the artist behind a music channel, only the name of that channel may be looked up in the public MusicBrainz database: no account data and never the name of a non-music channel. For this MaKoncert uses the YouTube API Services: the connection is also subject to the YouTube Terms of Service (https://www.youtube.com/t/terms) and the Google Privacy Policy (https://www.google.com/policies/privacy). You can also revoke the access at any time in Google's security settings (https://security.google.com/settings/security/permissions). Send questions or complaints about the YouTube connection to hello@makoncert.hu.
- Spotify: the list of artists you follow.
We also store your account identifier and display name at the provider and, where needed, the access token (in an encrypted store, not in the backups). The list is refreshed at connection, then usually once a day, and when you press "Sync now": what you follow there you follow here, what you unfollow there is removed here; artists you add or hide by hand stay yours.
You can end a connection in the account settings at any time: we then delete the token, the list and the follows that came only from it at once, and for Google (YouTube) we also revoke the access at the provider. For Spotify you can also remove the app's access in your own Spotify account. If you revoke the access only at the provider (or it lapses), we mark the connection as needing to be reconnected; if you do not reconnect within 28 days, we delete it in the same way as when you end the connection (the token, the list and the follows that came only from it).
When you upload your Spotify data, the data file you downloaded from Spotify is read in your browser: only the artist names are sent to us, and of these we store only the follows of artists in our catalogue; the file itself is not uploaded or kept.
We use this data only to show you the concerts of the artists you follow, to notify you about them and to suggest similar artists (the follows of users are used only in aggregate: a pair of artists counts only if at least 10 users follow both); we do not sell it, pass it on (apart from the MusicBrainz lookup above) or use it for advertising. MaKoncert's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.
10. Security and personal data breaches
- Encrypted connections (TLS) between the browser and the server and between the server and the database; HSTS and a Content-Security-Policy; your browser does not talk to the database directly.
- Row-level security on every application table of the database; the service keys exist on the server side only, and the access tokens of music accounts are kept in an encrypted store (Supabase Vault) and do not go into the backups.
- We handle no payment data, because nothing on MaKoncert costs money. Rate limiting works with one-way hashes of IP and e-mail addresses made with a secret key (HMAC) instead of the addresses themselves.
- In the live service an encrypted backup (age) of the database is made daily to storage independent of Supabase, and its restorability is checked regularly and automatically.
- The admin interface is role-restricted and its actions are logged; secrets are not in the source code, and automatic secret scanning runs.
- E-mail addresses, tokens and cookies are removed from error logs before they are written.
These measures reduce risk, but no internet service can guarantee complete security. In the event of a personal data breach we investigate it and, if it is likely to pose a risk to the rights of the persons concerned, report it to the NAIH without undue delay and, where feasible, within 72 hours (Article 33 GDPR). If it is likely to result in a high risk to you, we also inform you without undue delay (Article 34). We keep a register of breaches.
11. Your rights
You can exercise your rights at any time at hello@makoncert.hu or, where indicated, directly in your account. We act on your request without undue delay and at the latest within one month; for complex or numerous requests this can be extended by two further months, and we tell you within the first month, with the reasons. Acting on a request is free of charge; for manifestly unfounded or excessive requests we may charge a reasonable fee or refuse. If we doubt your identity, we ask you to confirm through the e-mail address of your account.
- Access (Article 15): you can find out whether we process your data and obtain a copy of it; write to our contact address and we send you the data of your account in a JSON file.
- Rectification (Article 16): you can change your account data in settings; you can also ask by e-mail for inaccurate data to be corrected.
- Erasure (Article 17): you can delete your account in settings; we then delete your data and the stored access tokens, with the exceptions described in section 6. Deleted data runs out of the backups within 30 days.
- Restriction (Article 18): you can ask us only to store data while you contest its accuracy, while we decide on your objection, where the processing is unlawful but you ask for restriction instead of erasure, or where we no longer need the data but you need it for a legal claim.
- Portability (Article 20): you receive the data you provided, processed on the basis of a contract or consent, in a machine-readable format (JSON).
- Objection (Article 21): you can object at any time to processing based on legitimate interest (for example public event data); we stop unless compelling legitimate grounds apply or the processing is needed for the establishment, exercise or defence of legal claims.
- Withdrawing consent: you can end the connection of a music account in the account settings (and at the provider) at any time. This does not affect the lawfulness of processing before withdrawal.
- Automated decisions (Article 22): the automated processes are described in section 3; you can ask for human review.
- Data of a deceased person: for five years after your death, a person you authorised, or failing that a close relative, may request access to your data, its rectification or erasure, or the restriction of its processing (§ 25 of the Infotv.).
- We notify the recipients of the data of any rectification, erasure or restriction unless this is impossible or involves disproportionate effort (Article 19).
12. Remedies
If you think we have infringed your rights, please write to us first at hello@makoncert.hu; we will try to settle it as soon as we can.
You can lodge a complaint with the Hungarian National Authority for Data Protection and Freedom of Information (NAIH): seat: 1055 Budapest, Falk Miksa utca 9-11.; postal address: 1363 Budapest, Pf. 9.; phone: +36 1 391 1400; e-mail: ugyfelszolgalat@naih.hu; website: naih.hu. You can also complain to the supervisory authority of the EU member state where you live or work, or where the infringement took place (Article 77 GDPR).
You can also go to court (Article 79 GDPR; § 23 of the Hungarian Infotv.). The case falls within the jurisdiction of the regional court (törvényszék) and, at your choice, can be brought before the regional court of your place of residence or stay. The controller and the processor must compensate damage caused by unlawful processing (Article 82 GDPR).
13. Children
A MaKoncert account can be created by a person aged 16 or over (Article 8 GDPR); by registering you declare this, and we do not check age separately. We do not knowingly collect data of persons under 16; if we learn of such data we delete it. If you think your child has created an account, write to hello@makoncert.hu.
14. Changes to this notice and legal background
We may amend this notice, for example because of a new provider or feature. The version in force is always on this page, with its effective date at the top. We inform you of material changes before they take effect on the site and, where reasonably possible, also by e-mail.
Legal background: Regulation (EU) 2016/679 of the European Parliament and of the Council (GDPR), Act CXII of 2011 on the Right of Informational Self-Determination and on Freedom of Information (Infotv.), and, for cookies and similar technologies, Act C of 2003 on Electronic Communications (Eht.).