Privacy

You do not need a FindEvents account to search for events.

Search and technical data

Search queries and filters are sent to the server so that we can return results. Infrastructure logs may record the IP address, query time, address and browser technical information needed for operation and security.

Saved events

When you click a bookmark, the event identifier is saved in your browser’s local storage (localStorage). These bookmarks are not sent to your FindEvents account, because there isn’t one, and are not synchronised between devices. You can remove them by unmarking the event or clearing site data in your browser.

“Worth noting” vote

When you vote successfully in this browser, a cookie called “fe_vote” is created, valid for up to one year, with a random signed identifier. It allows us to recognise and revoke your browser vote; no account or email is needed. Only a hash of the identifier calculated with a secret value is stored in the database. The vote remains until it is revoked or the event is removed.

To protect against abuse, we store a daily changing IP hash and limited voting counters. Records older than two days are cleared when the next voting request is received; the raw IP is not stored by this feature. A shared internet connection may limit several people from voting for the same event. The number reflects browser interest, not unique people, attendance or event quality.

Selection by interests

You can name your interests in your search query or choose an event category. We do not create a hidden interest profile based on your clicks. In the previous version, interests remembered in the browser are no longer applied automatically; they can be removed by clearing site data.

Optional search refinement with AI

When you select “Refine with AI”, OpenAI receives your query, chosen language, search filters, and the selected location’s date and time zone. Do not send sensitive personal data. Response storage at the provider is disabled in the request. FindEvents briefly caches the refined text using a hash of the query and context, and limits requests using a daily changing hash of the IP address.

Suggested event links

When you submit an event or source link, we store it and its verification status for up to 30 days. The status page is accessible only through its random link; it does not show the submitted link itself. To protect against abuse, we use counters with limited validity based on an IP hash mixed with a secret value, rather than the raw IP address. Public event addresses and proof of verification that enter the approved source register may be stored longer while the source is being checked. Infrastructure logs are handled as described above for technical data.

Language preference

When you choose a language in the menu, we remember it on this device for up to one year in the “fe_locale” cookie. It contains only a language code, with no visitor identifier. The language in a link takes precedence; changing country does not change language. You can change your choice in the language menu or remove it by clearing this site’s cookies.

Description translations

When you press the translation button, OpenAI receives the public event description and target language. Response storage at the provider is disabled in the request. We cache the automatic translation in FindEvents and reuse it until the source text changes. The original remains available. We limit requests using a daily changing IP address hash; this feature does not store the raw IP address.

The service provider may process data under its own privacy and retention rules.

Country and city selection

On your first visit, we choose a country and its capital from your browser language and region when compatible with the selected website language. This does not determine your precise location. We remember your chosen country and city for up to one year in the “fe_location” cookie, which contains only public country and city codes, without a visitor identifier or coordinates; browser local storage (localStorage) is also used for compatibility. Language and location are saved separately, and the place specified in a link takes precedence. You can change these choices on the site or remove them by clearing its cookies and local storage. Only after you press “Near me” may the browser ask for location permission; we use the coordinates on your device to find the nearest catalog city, without sending them to the FindEvents server or saving them.

External pages and images

When you open a ticket seller, organiser or map link, you use that website’s services and privacy rules. Event photos and posters are loaded from external sources: the browser contacts the image provider’s server. The image source link is shown on the event page. If there is no image or it cannot be loaded, a FindEvents category illustration is shown.

MCP and AI assistants

A connected assistant sends catalogue search parameters and receives public event information. Assistant chats are subject to the rules of the AI service provider you choose. Do not send personal ID numbers, payment details or other sensitive information in event searches.

Analytics and advertising

We use our aggregated usage statistics: page type, the associated event identifier, the selected country and city, search terms and result counts, save, share and calendar actions. Search terms that resemble personal or sensitive data are masked; in the admin panel, the text is shown only after at least three matching observations. By default, for analytics we do not create a visitor or session identifier, cookie or digital fingerprint, and we do not store precise coordinates, the raw IP address or the browser user-agent string. Search summaries are stored for 30 days, others for 180 days; outdated records are cleared when a later request is received. These are action counts, not unique people counts. For browser actions and related site search statistics, we respect Do Not Track and Global Privacy Control signals. The opt-out choice is stored on this device, in localStorage and in a “fe_analytics=off” cookie valid for up to one year, which does not contain a visitor identifier. The necessary API and MCP request, source verification and supplier cost counters remain active. We do not use paid first-event positions.

Administrative access

Administrative sign-in uses an HttpOnly, SameSite=Strict session cookie valid for up to 8 hours. The sign-in password is sent in a POST request, not in the link or localStorage; the password and session values are stored as hashes. Authentication audit logs do not store raw IP addresses or browser user agent strings; rate limiting is handled in temporary server memory.