Cookie Policy

Last revised: 2026-10-06 (version 2026-10-06-v5 — this version corrects what the previous one said about the app and about Meta, and lists what else we keep in your browser. The app reads no advertising identifier: the previous version said it could share your phone's advertising identifier with Meta, and it no longer does (section 5). The Meta Pixel is not loaded on the pages where you type personal data, runs with Meta's automatic event collection switched off, and for what it collects we and Meta are joint controllers (sections 2.4 and 5). Stripe's cookies are set by its payment form embedded in our checkout, not on Stripe-hosted pages (section 5). A new section 2.5 lists the other small items we keep in your browser. Nothing about which cookies need your consent has changed.)

This Cookie Policy explains how MeetPlayNow uses cookies and similar technologies on our website. It complements the Privacy Policy.

A cookie is a small text file stored on your device by your browser when you visit a website. Cookies are widely used to make websites work, to make them work more efficiently, and to provide information to website operators.

2. Categories of Cookies We Use

2.1 Strictly Necessary (always on)

These cookies are required for the platform to function and cannot be disabled in our system. They are typically only set in response to actions you take, such as logging in or submitting a form. They include:

Authentication session — keeps you logged in.
CSRF token — protects forms against cross-site request forgery.
Locale preference (essential) — preserves the language you have selected for navigation.

These cookies do not store any data that personally identifies you beyond what you have entered yourself.

2.2 Preferences

These cookies remember choices you make to provide a personalized experience:

Language switch (next-intl) — remembers your preferred display language across visits.

2.3 Analytics (currently inactive)

We are evaluating the use of privacy-friendly analytics (e.g. PostHog or Plausible). These cookies would help us understand how visitors interact with the platform in aggregate. They will only be activated with your explicit consent, and you can change your choice at any time.

2.4 Marketing

These cookies exist to measure whether our advertising works and to show our advertisements to people who have visited us. None of them is set unless you allow marketing cookies, and allowing them is not a condition of anything: the platform works exactly the same without them.

`_fbp` — set by the Meta Pixel (Meta Platforms Ireland Ltd). A random identifier for your browser, so that Meta can recognise the same browser across visits and attribute a sign-up or a payment to an advertisement it showed you. Expires after 90 days.
`_fbc` — set by the Meta Pixel (Meta Platforms Ireland Ltd). The identifier of the Meta advertisement you clicked (`fbclid`), if you arrived from one, with the time of the click. Expires after 90 days.
`mpn_attrib` — set by MeetPlayNow itself (first-party). The campaign you first arrived with: the `fbclid` and `utm_` tags of the address you landed on, that address, the referring page and the time. It is written once and never overwritten while it lives, and it is read back only when you create an account, to record on your account which campaign brought you. It is not sent to Meta by itself. Expires after 90 days.

The Meta Pixel is a script loaded from `connect.facebook.net`. While it runs it tells Meta which pages of MeetPlayNow you view and when you start a checkout (with the amount, the currency and the competition), together with the two cookies above. It runs with Meta's automatic event collection switched off, and our code never gives it your email address or user id. It is not loaded on the pages where you type personal data — sign-up and sign-in (with email verification and sign-in callbacks), password reset, consents, onboarding and the choice of city, policy updates, your whole dashboard, account deletion, unsubscribing, the chat, the organizer area, the contact form, the city waiting list and the shop pages — so it cannot read what you type there. On the pages where it stays loaded, it is paused while you type in a field that takes personal data — the email field in the footer, a partner's email address at payment, a city request, the chat with Khun Somtum — and resumes when the field is empty again or the form is closed; the creation of an account reaches Meta only from our server. Separately, our server reports two events to Meta (an account created, a payment completed) with your email address and user id in hashed form — that is not a cookie, and it is described in section 8 of the Privacy Policy; it is governed by the same marketing-cookie choice.

2.5 Other things we keep in your browser

These are not trackers and are not shared with anyone; each exists for the function named beside it, and none needs your consent.

`mpn_active_sport` and `mpn_market` (cookies, 12 months) — the sport and the country and city you chose, so that the site opens on them next time.
`pending_referral_code` (cookie, 7 days) — the invitation code of a referral link you followed, so that it can be applied when you sign up.
`mpn_cookie_consent` (local storage) — your answer to the cookie banner when you are not signed in, so that the banner is not shown again and your choice is respected.
Tab storage (session storage, deleted when you close the tab) — the chatbot's conversation identifier and message count, and a draft of the sign-up steps you have not finished.
A dismissed notice (local storage) — that you closed the notice about publishing your profile, so that it does not come back.
`mpn_geo_banner` (local storage) and `mpn_geo_banner_closed` (session storage) — that you already answered, or closed, the banner suggesting the country or city for where you are, so that it is not asked again.
`mpn.privacy.export` (local storage) — the state of a data download you requested from /dashboard/privacy, so that the page can follow it until it is ready.

3. Duration

Session cookies are deleted when you close your browser.
Persistent cookies are stored for up to 12 months at most, after which they expire and a new consent prompt may be shown. The marketing cookies in section 2.4 are shorter-lived: 90 days.

4. How to Manage Cookies

A cookie consent banner is shown on your first visit. You can accept all, reject non-essential, or fine-tune your choices per category.
You can change your preferences at any time at /dashboard/privacy when logged in — each cookie category you allowed is listed there and can be withdrawn — or, when not logged in, by clearing this site's data in your browser and revisiting the platform, which shows the banner again.
Withdrawing marketing cookies stops the Meta Pixel from loading and stops our server reporting to Meta from the next page load. It does not delete the cookies already on your browser: they expire on their own after 90 days, or you can delete them in your browser's settings.
Most browsers also let you block or delete cookies via their settings. Note that disabling strictly-necessary cookies may break login and core functionality.

5. Third-Party Cookies

Some third-party services we use may set their own cookies:

Stripe — set by Stripe's payment form, which is embedded in our checkout page, and required for payment functionality and fraud prevention. Stripe's own Privacy Policy and Cookie Policy apply to those cookies.
Meta (Meta Platforms Ireland Ltd, Dublin, Ireland; with data also processed by Meta Platforms, Inc. in the United States) — the `_fbp` and `_fbc` cookies of section 2.4, set by the Meta Pixel only if you allow marketing cookies. For collecting data through them and transmitting it to Meta, we and Meta are joint controllers, under Meta's Controller Addendum; what Meta then does with it, it decides as an independent controller — section 8 of our Privacy Policy explains both. Meta's own Cookie Policy and Privacy Policy apply. The transfer to the United States is covered by Standard Contractual Clauses and the EU-U.S. Data Privacy Framework — section 12 of our Privacy Policy.

The Meta Pixel is the only third-party tracking tag on the website. We embed no social-network buttons and no other advertising tags.

The mobile app uses no cookies and loads no Pixel: nothing in this policy is set by it. It reads no advertising identifier either. What the app can do instead, and only if you turn on "Advertising measurement" in the app, is give our server a short description of the device, which our server then passes to Meta together with the same two events it reports from the website. That is not a cookie and it is not done by any code of Meta's in the app; it is described, with the switch that governs it, in section 11 of the Privacy Policy.

6. Changes to This Policy

We may update this Cookie Policy. Material changes will be notified via the platform; the current version is always available at /cookies.

7. Contact

For questions about cookies: privacy@meetplaynow.com.