Cookie policy
Last updated: 22 September 2026
What cookies are
Cookies are small files stored by your browser on your device when you visit the platform. Scripts and pixels loaded from another company's servers work in a similar way, and this policy covers them too. We use cookies so that the site works — to keep you signed in, to remember the display language and to remember your answer to the cookie banner — and, only if you agree, to measure an advertising campaign.
Essential cookies
These cookies are strictly necessary for the platform to function (for example authentication and session maintenance). They do not require consent and cannot be disabled. Every cookie our own code sets falls into this category; they are listed in the first table below.
Analytics and audience measurement
We measure how the site is used, in aggregate form, through the Vercel Web Analytics service — but only if you accept the Statisticscategory in the cookie banner. If you refuse, or simply have not answered yet, the measurement script is not loaded at all. According to the provider's documentation the service stores no cookies and creates no persistent identifier for you. We do not run Google Analytics.
Marketing and advertising cookies
Only if you accept the Marketing category, the site loads the Meta pixel through Google Tag Manager. It is there for a paid campaign promoting one event, which our partner Calmly runs from its own Meta advertising account; the tag container that loads the pixel is ours, and nothing in it runs on this site until we publish it. Marketing is separate from Statistics, and accepting one does not accept the other.
Once you have accepted it:
- Google Tag Manager (the
gtm.jsscript, from Google Ireland Limited) loads on the site's public pages and loads the pixel when it is needed. It sets no cookie of its own, but loading it sends Google your IP address and browser details. - The Meta pixel (the
fbevents.jsscript, from Meta Platforms Ireland Limited) stores an advertising identifier in the_fbpcookie. Although Meta's script writes it, the cookie sits on this site's own domain. The pixel loads when you complete a purchase and reports it: the event, the ticket type, its price and the currency. Once loaded, it may also report pages you open afterwards in the same tab. Each report also carries the page address, the page you came from, your IP address and your browser details. - The pixel also keeps two notes in your browser's local storage about what kind of page you arrived from (for example, no page or another site) and when. If you arrived by clicking a Meta ad, it also stores the click reference from that link, in the
_fbccookie and in local storage. - Meta's pixel template also fetches a helper script that Meta hosts on Amazon Web Services servers in the United States (
capi-automation.s3.us-east-2.amazonaws.com). Fetching it sends those servers your IP address and browser details; the script rewrites the_fbpand_fbccookies in the format Meta uses. - If your browser allows third-party cookies and you are signed in to Facebook or Instagram, or have visited them, your browser sends Meta's own cookies for those sites (such as
fr) along with each report. We do not set or read those cookies; Meta controls them under its Cookie Policy. - When a purchase has been reported, we note it in your browser's local storage, so that the same purchase is not reported twice.
Your name, email address and phone number are never sent, whether in clear or in hashed form. The pixel runs with Meta's automatic matching of personal details ("advanced matching") off, with its automatic collection of button clicks and page details off, and without Meta's server-to-server Conversions API. It never loads on account, organizer, administration or sign-in pages, nor for organizer or administrator accounts, nor on a page whose address carries an order-access link.
Meta, and the other third parties involved, use this information to provide measurement services and to target and deliver ads, including ads shown to you on Facebook, Instagram and elsewhere outside this site. How Meta does so is set out in its Privacy Policy and Cookie Policy; who receives the data and where it is transferred is set out in our Privacy Policy.
Managing consent
The banner shown on your first visit asks you separately about Statistics and Marketing; both start switched off, and refusing is as easy as accepting. Your answer is remembered so the banner is not shown again. You can change it at any time from the Cookie settings link at the bottom of every page.
- Withdrawing consent stops the scripts from loading from then on. A script already running in a tab you have open keeps running until you reload or close that tab.
- Withdrawing does not delete a
_fbpcookie already on your device. You can delete it, and every other cookie of this site, from your browser settings; you can also block third-party cookies there. If you block all cookies, the platform will not be able to keep you signed in. - To refuse ad targeting more broadly, you can use the ad preferences in your Facebook or Instagram account, or www.youronlinechoices.eu.
Detailed list of cookies
Essential — always on
| Name | Provider | Purpose | Duration |
|---|---|---|---|
| mingle-consent | Mingle Society (minglesociety.ro) | Stores your answer to the cookie banner, per category, with the date it was given, so that the banner is not shown on every visit and your choice is respected. | 6 months |
| better-auth.session_token | Mingle Society (Better Auth) | Identifies your authenticated session. Without it you cannot stay signed in or access your account. | 30 days |
| better-auth.session_data | Mingle Society (Better Auth) | Short-lived cache of your session details, so that not every page load has to query the database. | 5 minutes |
| mingle-order-<order> | Mingle Society (minglesociety.ro) | Set only when you buy without an account: it gives this browser access to that order (ticket, refund, invoice request) without a password. One per order. | 30 days |
| NEXT_LOCALE | Mingle Society (next-intl) | Remembers the interface language you chose (Romanian or English). | Until you close the browser |
All of the above are first-party cookies, set by minglesociety.ro itself. On the live site, served over HTTPS, the two session cookies carry a __Secure-prefix in their names. Payment takes place on a page hosted by Stripe, on Stripe's own domain; any cookies set there are governed by Stripe's cookie policy.
Marketing — only if you accept it
| Name | Provider | Purpose | Duration |
|---|---|---|---|
| _fbp | Meta Platforms Ireland Limited, written on this site's domain by the Meta pixel | Advertising identifier for this browser, used to measure the campaign and to target and deliver ads. | 90 days, renewed each time the pixel runs |
| _fbc | Meta Platforms Ireland Limited, written on this site's domain by the Meta pixel | Set only if you arrived by clicking a Meta ad: stores the click reference, so the purchase can be attributed to the ad. | 90 days, renewed each time the pixel runs |
| lastExternalReferrer, lastExternalReferrerTime | Meta Platforms Ireland Limited (local storage, not a cookie) | The kind of page you arrived from, and when, sent with the pixel's reports. | Until you clear this site's data |
| multiFbc, aemSource | Meta Platforms Ireland Limited (local storage, not a cookie) | Set only if you arrived by clicking a Meta ad: the click reference, kept for attribution. | Until you clear this site's data |
| mingle-purchase-tracked:<order> | Mingle Society (your browser's local storage, not a cookie) | Records that a purchase has already been reported, so that it is not reported twice. It holds no personal details. | Until you clear this site's data |
| fbevents.js | Meta Platforms Ireland Limited (script) | The Meta pixel itself: it sets the cookies and local storage above and sends the reports described in this policy. | Not stored beyond the browser cache |
| clientParamBuilder.bundle.js | Meta, hosted on Amazon Web Services servers in the United States (script) | Helper loaded by Meta's pixel template; rewrites _fbp and _fbcin Meta's format. | Not stored beyond the browser cache |
| gtm.js | Google Ireland Limited (script) | Google Tag Manager: loads the Meta pixel. Sets no cookie. | Not stored beyond the browser cache |
This table covers what is stored on this site's domain and the scripts that do it, as we tested them on 22 September 2026; Meta updates its pixel independently of us. Meta's own cookies on facebook.com and instagram.com, such as fr, are not set by this site and are described in Meta's Cookie Policy.