Privacy policy

Dataracing Group Kft. is the controller of personal data processed to provide Yondernite. Its registered office and contact details are below. This notice covers visitors and account holders, including people using connected services. For privacy requests, write to our shared privacy address and identify the service as Yondernite.

Service provider & data controller

Dataracing Group Kft.

Registered office

2161 Csomád, Kossuth Lajos út 47., Hungary

Company registration

13-09-246370

EU VAT number

HU33022473

Account and sign-in: email address, display name, profile picture, password hash, session records, and any linked sign-in identifier you provide. We use these to create and secure your account, sign you in and support verification or recovery (GDPR Article 6(1)(b), providing the requested service; security also Article 6(1)(f), our legitimate interest in preventing abuse). Providing the required sign-in fields is necessary to create an account, but an account is not required to browse public events.

Personalisation: your chosen town and search area, interests, artists, wishes, saved events and feedback help us rank programmes (Article 6(1)(b)). Guest preferences are kept in browser storage and a first-party cookie and sent to our server to answer your requests; they and your reactions to events are also saved automatically as a backup on our server (see the guest backup section). If you have not chosen a town yet, your first visit takes an approximate Hungarian town from the network address of the request and offers it as the default; it is not stored and you can change it at any time. Your answers on the taste card and what kinds of programmes you react to stay only in your browser and a small first-party cookie (they are not kept on our server) and decide the mix of types in your list. If you enable guest notifications, we also store a private notification profile containing your interests, chosen town, language, device subscription and delivery history, so matching can continue while the browser is closed. It is tied to this browser and cannot be used to sign in. If you choose a device location feature, the browser asks for permission. Avoid entering sensitive information in free-text fields.

If you use Yondernite without an account, we make a private profile for this browser once you have started using the site. Until then nothing leaves your browser: it only keeps a short list of your first actions in its own local storage (what you searched for or filtered by, which events you opened, expanded, asked the explanation of or clicked a ticket button of, and that you reacted, each with its time; at most the latest 200, none older than 120 days, so a visit every few weeks still counts). The profile is made as soon as that list holds about five actions, or holds actions from two different days, or at once when you save something you would not want to lose: a town other than the default, a topic, a favourite artist or a wish. A browser that reports being driven by automation, and a burst of actions far faster than a person can make them, do not count. Then the browser sends the list together with your choices in one request, it is written into your own profile with the times you did them, and the list in the browser is emptied. It is made automatically, without a click and without asking for an email address or a name. Opening a page, scrolling, a default profile, or a visit with only a few actions creates nothing, and neither does a visit by a crawler or a program. We treat the profile as we would an account’s. It keeps your choices (town, topics, favourite artists and wishes) and your reactions to events (Interested, Not this time, Not interested). We prepare your personal recommendations in advance on the server, also while this browser is closed, and your interest and wish text may be processed automatically by AI providers to interpret and compare it for those recommendations. We also record what the feed showed you and where, which programmes you opened, whose other dates you expanded or for which you opened the explanation, which ticket buttons you clicked, which cards were fully visible on your screen and for how long, and how long the page of an event stayed open (where the website’s reporting of views is on), what you searched for and which event type, genre, date or venue filters you chose; a counter for each programme remembers how often you have seen it. We use this only for your own recommendations: to order your feed, to avoid showing you the same cards again and again, and to learn from what you repeatedly choose (for example, if you keep filtering for concerts, concerts come a little earlier in your list; nothing is asked of you and your own choices are never changed). It is never used for another person’s feed, shared, sold or used for advertising. The separate analysis of your interests by AI (direct-interest verdicts) stays off until you turn it on yourself; notification permission and the notification profile are separate too. A separate secure HttpOnly cookie gives this browser access; it is not a sign-in or public profile. We store only a hash of its access key. If that cookie ever disappears, your browser also keeps a separate recovery key in its local storage: it can only issue a new access cookie for this profile, and it changes every time it is used. Anyone who could read this browser’s local storage, for example through a malicious script injected into the site, could use that key, which is why it is separate from the cookie and is removed when you delete the profile. We record when you last visited, at most once per visit, to know when the profile expires.

The profile expires after 400 days without a visit, the longest time a browser keeps a cookie. A visit is recorded at most once each time you open the site, or come back to it after at least 30 minutes, never on every request, and every recorded visit renews the 400 days; saving your choices renews it the same way. After the expiry, scheduled cleanup removes the profile and its data. The rows of what was shown to you and of your actions are kept for 180 days and are then reduced to counts per month; the rows of which cards were fully visible for 30 days; the counter of each programme until you have not seen it for 120 days (see “Your activity in the feed”): a guest’s are kept exactly as a member’s. If you have not visited for 14 days, we stop computing recommendations for the profile until you come back. Under Settings → Guest profile for this browser, you can immediately delete the profile, its reactions, its history and its access while keeping your browser choices; after that nothing is recorded and nothing is sent to the server until you choose something, search, use a filter, open an event or react to one again, and then your first few actions stay in your browser again until there are enough to make a new profile. Deleting also empties that short list. If only the recovery key is left, deleting also works with it. Clearing browser data alone does not immediately delete the server copy; the 400-day expiry applies. If only this browser’s own copy of your choices is gone while access remains, they come back from the server automatically. If both the access cookie and the recovery key are gone, the old profile can no longer be reached: a new one is made when you do something again, and the old one expires. While you are signed in, the guest profile is not used or updated. Signing in or up also discards the short list of first actions your browser may still hold: it is never sent. Signing up makes the history of the guest profile (what was shown, your actions, views and counters) part of your new account and ends the guest profile; signing in to an existing account ends the guest profile and deletes its history, and the account’s own history stands. Backup copies follow the limitations in the retention section.

Deleting immediately revokes access and removes the profile, its reactions, its history of what was shown and done, its prepared recommendations and its recovery copy. To notify background processes, we keep a technical deletion marker containing a random internal identifier, internal references and the deletion time for at most 30 days; it contains no profile data, access key or event history. The shared interpretation cache for interest phrases, without a link to a person, follows its own expiry of at most 30 days. Shared computation data also used by other profiles or the public catalogue may remain. Protected backups follow their backup lifecycle. Data handled by AI providers follows their own retention rules; deleting the profile does not promise immediate erasure from every provider or backup copy.

When you start a plan, it keeps the programmes you marked, the town, the days you chose and the name shown as its organizer, and the link that belongs to it (a long address that cannot be guessed). Anyone you send the link to can use it, and a plan holds at most six people. Whoever joins through the link gives a name and answers once per programme (I'm in, Maybe, Can't). Without an account that name belongs to an anonymous guest identifier, tied to the browser by the same HttpOnly cookie as the guest backup; the name is stored as that identifier's display name and we prefill it next time. The people in a plan see each other's names and answers and nothing else: the plan does not show your profile picture, interests, saved programmes or feedback. The link is not put into search engines and is not passed to other sites as a referrer.

The organizer can revoke the link (it gets a new address; the people in the plan stay), remove a participant, and close or delete the plan. Leaving or being removed deletes your answers. If the organizer's account is deleted its plans are deleted; if a participant's account is deleted their answers and membership are deleted; when the guest identifier expires (400 days without a visit) the guest's participation ends with it. When you sign in or register, the answers you gave through a link move to your account. If you turned notifications on separately (on your account's devices, or for this browser without an account), we also send you a notification about a plan, and only about these: everybody can go to one programme (to the organizer), the organizer confirmed a programme, someone added a programme (never to the person who added it; programmes added within ten minutes are one notification) and the chosen programme was cancelled or changed. A single answer never sends one, and nothing is sent in your quiet hours. The notification carries the plan's title and the programme's title, never anybody's name or answer, and opens the plan's link. For a guest we tie this browser's notification profile to the guest identifier so the plan can reach it; the tie ends when you turn the notifications off, when the notification profile expires (90 days without a refresh, which opening a plan renews) or when the guest identifier expires, and nothing is sent after either expires. The legal basis is providing the service you asked for (GDPR Article 6(1)(b)).

If you choose Google or Facebook sign-in, we receive the provider identifier and permitted basic profile information: your name, email address and profile picture. The picture is copied once, when you create the account, and you can decline it on the sign-up form or remove it later in settings. Sign-in does not import contacts or friendships. If you enable profile discovery or friend suggestions, your display name, profile picture and relationship information may appear to other signed-in users. Friendships require acceptance. Shared recommendations have a separate opt-in: friends can then see that an event may match your interests, but cannot see your personal lists, saves or reactions. You can turn this off in settings. Ideas and answers explicitly submitted to a shared plan are visible to its accepted participants; leaving removes your answers. The organizer can delete the plan. These features serve your request (Article 6(1)(b)); optional discovery settings can be switched off.

Connecting Spotify lets us obtain your top and followed artists and store connection credentials and artist suggestions. You choose which suggestions become favourites. Disconnecting removes our connection credentials and cached suggestions; favourites you explicitly imported remain until you remove them. You can also revoke access in Spotify. For notifications, we store your preferences and device subscription or push token, and send messages through the device’s delivery provider. Optional Spotify access and notifications use your consent (Article 6(1)(a)); you can disconnect or disable them without losing ordinary discovery.

When you post a photo to an event we store the photo in two sizes (without its metadata, such as its location), the caption, the time of posting, the event's name, time and place, the photo's fingerprint (a short number by which we recognise a removed photo being posted again), likes, and the reports made against you or your photo. Anyone can see the photo on the event's page, in the "Most odabent" rail and on its share link; your name and profile picture show with it only if your profile can be found (Settings). The legal basis is providing the service you asked for (GDPR Article 6(1)(b)), and preventing abuse is our legitimate interest (Article 6(1)(f)).

Every posted photo is checked automatically: a reduced copy of it goes to an AI model (Anthropic's Claude, see "Who we share it with"), which decides whether the photo follows the rules and belongs to an event. No person makes the decision; a reported photo is checked again, more strictly. A photo stays until you or we remove it; the files of rejected and removed photos are deleted after 14 days at the latest, those with harmful content at once. We do not store a reporter's address, only a one-way code so that one address can report a photo once.

If you connect your account to an AI assistant (for example Claude, ChatGPT or Gemini), the assistant can query the public yonder𝒏𝒊𝒕𝒆 programme listing without you signing in. It can read your recommendations and your Interested list only after you sign in and explicitly allow it on the connection page. It does not receive your email address, password, settings or friends, and it cannot change anything on your account. The connection is optional and rests on your permission.

What the assistant receives is handled by the assistant’s provider (for example Anthropic, OpenAI or Google) under its own terms and privacy notice; we have no control over that. About the connection we store which assistant registered itself, under what name and return address, when you connected it and when it was last used, and its access keys, which we keep only as a hash. You can disconnect the assistant at any time under Settings → Connected assistants, and its access ends immediately. When you delete your account, the connections and their keys are deleted too.

Network and security information, such as IP address, request metadata and error or access records, can be processed by our hosting and delivery infrastructure to serve pages, diagnose failures and prevent abuse (Article 6(1)(f)). When you contact us, we use the message and contact details to respond, handle complaints or meet legal duties (Articles 6(1)(b), (c) or (f), according to the request).

Only with your analytics consent do two services measure. Google Analytics processes browser and device information, page visits and feature-use events, using pseudonymous cookie identifiers. PostHog (EU cloud) measures how you use the site: which pages you open, how far you scroll, how many events you look at in a visit and what you do (for example following an external ticket link). For PostHog events the browser stores a random identifier; if you are signed in it receives an irreversible (HMAC) identifier derived from your account, not your account ID, email address or name (Article 6(1)(a)). PostHog requests go through our own domain, the specific event, artist or search is removed from page addresses and page names, your IP address is not stored, and the traffic of staff accounts is not measured. Events are kept for 12 months. PostHog also measures the errors of the site (addresses, e-mail addresses and long numbers are removed from the message), the loading and interaction timings of pages, and where you click on the public content pages (coordinates and element identifiers, no text). Our custom events describe actions and counts, not your wish text, search terms or email address. Google may receive connection metadata when requests reach its servers. Advertising personalisation and Google signals are disabled in our tag configuration. See the cookie policy to change your choice; after you withdraw, the browser deletes its analytics identifiers. If you delete your account or guest profile, we also ask PostHog to delete the data tied to you.

When you submit a search, we save the text you typed, and when you open a result from the list, which result it was and where in the list it stood. We use this to see what people look for, which results answer it, and to improve search, suggestions and the interpretation of ideas (our legitimate interest, Article 6(1)(f)). Before it is saved, e-mail addresses, phone numbers, long numbers, web addresses and card or bank-account numbers in the text are replaced by a placeholder and the text is cut to 200 characters. A record holds the text or the opened result, the time, the language, whether you were signed in, how the search was understood and how many programmes it found. It holds no name, account ID, IP address, cookie value or browser details, only whether the request came from a phone or a computer. So that the searches and clicks of one visit can be read together, a code is made from your account or address with a secret that changes every day and is deleted soon after; it cannot be linked to you or to another day. Records are deleted after at most 90 days. Only anonymous daily counts of words, of the interests searches were read as and of the places in the list that were opened are kept longer. For a search by idea (Enter or the search button) the text you typed is sent to Claude (Anthropic), our processor, for interpretation; your profile and saved events are not sent, and the interpretation can be used in the search address for 24 hours. Anthropic also operates outside the European Economic Area, in the United States (see Recipients & international processing).

Only administrators can read the saved searches, every reading is recorded, and they are not shared with, sold to or sent to any other company, nor given to the AI model that reads somebody else's search. Do not type personal details into the search box: a name or other detail written in words can still identify you, and we cannot always recognise it. If your browser sends a Do Not Track or Global Privacy Control signal, nothing is saved: no search text and no click. You can object to this processing (Article 21) or ask us to remove a saved search: write to the privacy contact below with the words you searched for and roughly when. Copies in protected backups follow the backup lifecycle described under “How long information is kept”.

When you are signed in, and as a guest once your private guest profile exists (see “Guest profile on the server”), we keep a record of what your feed showed you and what you did with it: which programmes were listed for you and at which place in the list, which you opened, whose other dates you expanded or for which you opened the explanation of why it is shown, which reactions you gave (Interested, Not this time, Not interested, or taking one back), which ticket buttons you clicked, what you searched for (the text) and which event type, genre, date or venue filters you chose. This record is kept today and has no setting of its own. Where the website’s reporting of views is switched on, your browser also tells us which cards were fully visible on your screen and for how long, and we store the programme, the card’s place in the list, the time it was fully visible and the time bucket of your visit; the page of an event also tells us how long it stayed open and in view, which we store with the record that you opened it, so that a programme you only glanced at does not count as interest; the phone app does not send this. We use this record to order your own feed (providing the service you asked for, GDPR Article 6(1)(b)), to avoid showing you the same cards again and again, to learn from what you repeatedly choose in the filters and searches (a type or a genre you choose on at least three different days or in three different searches lifts it a little in your own list, more for someone we know little else about; your own choices are never changed) and, as anonymous counts, to measure how the product works (our legitimate interest, Article 6(1)(f)).

The rows of what was shown to you and of your actions are kept for 180 days and are then reduced to counts per month, view and kind, which stay until your account is deleted. The rows of which cards were fully visible are deleted after 30 days. A counter for each programme, remembering how often you have seen it so that a programme you keep seeing can move down your feed, is deleted when you have not seen that programme for 120 days. Separately, we keep anonymous counts of views per day, view, place in the list and kind of slot for 90 days; they hold no account, name, address or browser details. If your browser sends a Do Not Track or Global Privacy Control signal, these anonymous counts are not written. The rows and the per-programme counters are what orders your own feed, so they are still written, and you can ask us to delete them. None of this is shared with, sold to or sent to another company or to an AI model. Deleting your account deletes the rows and the counters; copies in protected backups follow the backup lifecycle described under “How long information is kept”. You can object to this processing (Article 21) or ask for access or deletion: write to the privacy contact below.

Data is available to authorised people and providers as needed for hosting, security, email delivery, notifications and the optional integrations you use. Cloudflare supports website delivery and security. Google and PostHog provide analytics when permitted; Google, Meta and Spotify receive information when you use their respective services. An embedded Spotify player contacts Spotify only after you choose to open it. Anthropic receives the text of searches by idea and a reduced copy of uploaded photos for interpretation. Following an external event link or loading externally hosted artwork can disclose network information to that website. Those providers also have their own privacy notices.

Some providers operate outside the European Economic Area, including in the United States. Transfers requiring GDPR safeguards must rely on an applicable adequacy decision or appropriate safeguards, such as standard contractual clauses. Contact us for information about the safeguards relevant to your data. We may disclose information where legally required or necessary to establish, exercise or defend legal claims.

• Google privacy policy ↗
• Spotify privacy policy ↗
• Meta privacy policy ↗
• Cloudflare privacy policy ↗

Account information and saved preferences are kept while your account is active, until you remove the information or delete the account. Disconnecting an integration removes its credentials and connection data as described above. Browser preferences remain until cleared; cookie lifetimes are listed in the cookie policy. Account deletion removes the active account and associated personal records; restricted backups or records required for security, legal duties or disputes may remain for as long as that purpose requires. Retention is assessed by necessity, applicable legal periods and the lifecycle of protected backups, rather than a promise of instant deletion from every copy.

Guest notification profiles expire after 90 days without a successful profile refresh during a visit. Expiry stops delivery; the scheduled cleanup removes the profile and associated personal records. Turning off guest notifications removes that server profile immediately. Browser wishes remain until you clear them. When you sign in on the same browser, an existing push opt-in can move to that account and the separate guest notification profile is removed. Backup copies follow the backup limitations described above.

Subject to the GDPR’s conditions, you can request access, correction, erasure, restriction or a portable copy of your data, and object to processing based on legitimate interests. You can withdraw consent at any time; this does not affect processing that was lawful before withdrawal. Use the settings for profile changes, connections and account deletion, and the cookie controls for analytics. For other requests, contact our privacy address. We may ask for proportionate identity verification. We normally respond within one month; if a lawful extension is needed, we explain it within that month.

You can complain to the Hungarian National Authority for Data Protection and Freedom of Information (NAIH), 1055 Budapest, Falk Miksa utca 9–11., or to the supervisory authority where you live or work, and seek a judicial remedy. See NAIH’s website for current submission channels.

NAIH: complaints and contact ↗

Yondernite uses automated ranking to personalise event suggestions. This does not decide your legal rights or produce similarly significant effects: you choose which events to explore. You can change the interests and feedback that influence recommendations. The order of the feed can also change from one visit to the next and takes into account which programmes you have already seen, so that the same cards do not stay on top. When you have chosen no interests, or are not signed in, the list is ordered by general factors such as the kind and size of the event, how soon it takes place and the time of day, together with the town you chose, and by nothing else about you. Clicking the separate idea-search button sends the entered query to Claude (Anthropic) for interpretation, without your profile or saved events. The interpreted conditions can be used in the shareable search address for 24 hours. Typing does not trigger these AI calls. Automated analysis may interpret public event descriptions; the current event-analysis integration does not send your private profile to its AI provider. We update this notice when data practices change and seek fresh consent where required.