Privacy Policy

Frag-o-Matic is organised by E-Events VZW, company number BE0871.628.142, Professor Scharpelaan 90, 3130 Betekom, Belgium. E-Events is responsible for the personal data described in this policy.

For privacy questions or requests, email [email protected]. For tickets, competitions and other event questions, use [email protected].

This notice covers the FoM website, accounts, shop, tickets, seat reservations, competitions and related event administration. Our Cookie Policy explains browser storage and optional tracking. Our Terms and Conditions cover purchases and participation.

We use the details you provide to create and manage your account: your name, nickname, email address, password hash, verification status and any optional profile details or avatar you add. Some services also need your date of birth, contact details or address. Required fields are marked in the relevant form. Without the information needed for a particular service, we may be unable to provide it.

If you choose Google or Discord sign-in, that provider supplies the identifiers and profile information authorised during sign-in, such as your email address and display name. We use those details to sign you in or link the account you selected. We do not receive your Google or Discord password. You can manage supported account links in your account.

We process account information to provide the service you request and take steps towards that service, under Article 6(1)(b) GDPR. Verification, access controls and checks against account misuse also support our legitimate interest in keeping accounts and the event secure, under Article 6(1)(f).

An account carried over from an earlier FoM website can also contain earlier participation, linked gaming identifiers and optional profile answers, such as education, profession or gaming preferences. Not every field is collected by the current registration form. You can ask us to review or correct information retained from an earlier account.

Orders contain the products and quantities you buy, prices, discounts, tax, payment status and references, billing details and any delivery details needed for the purchase. Tickets record their event, buyer, assigned attendee, validity, refund status and check-in history. Seat reservations connect the relevant ticket to a seat and record changes so staff can resolve mistakes and disputes.

Payments made through Mollie are handled by Mollie and the payment method you choose. They receive the information needed to process the transaction. FoM receives payment references, status and related transaction information; we do not ask you to enter your payment-card number or security code into a FoM account form. See Mollie's privacy statement.

When another customer assigns a ticket to you, we receive your account reference through that assignment. The buyer and attendee can see the ticket information needed to manage their respective rights. An assignment does not make either person's full account or billing details public. If a ticket appears in your account unexpectedly, contact us.

This processing is needed to fulfil purchases and event participation, handle requested changes and prevent duplicate or fraudulent use. Accounting and tax records are also processed to meet legal obligations, under Article 6(1)(c). A group organiser should only provide other people's information where they are entitled to do so and should tell them about this notice.

Choose your nickname with public visibility in mind. The public seatmap can show a nickname and clan beside a reserved or occupied seat, and visitors can search for people or clans. Seat status can indicate attendance. Seatmap listings do not disclose your email address, legal name, billing details, ticket barcode or individual check-in time.

Participant lists and player rosters require sign-in and show nicknames and clans. Team names, results and clan pages can be public. Community features such as looking-for-team posts can show the profile image and text you share to other signed-in members. Do not put private information into a nickname, clan name, profile image or community post.

We use these displays to help participants find their friends, organise teams and follow the event. Where we rely on our legitimate interests in running a community event and maintaining its results, you can object and explain your circumstances.

Competition records can include registrations, eligibility checks, team membership and roles, game identifiers, opponents, schedules, scores, standings and prizes. Nicknames, teams, match results and rankings may be published so participants and spectators can follow the competition. Historical editions and results can remain available after the event.

Crew may use score submissions, match evidence, reports and decisions to resolve disputes, investigate cheating and enforce competition rules. Evidence submitted for review is not automatically intended for publication. Only include information relevant to the case and avoid exposing other people's unrelated personal details.

We use necessary registration and match information to run the competition you enter. Keeping accurate results and handling disputes also serves our legitimate interests in fair play and the event's history. Prize administration may require a recipient's name, payment details and information needed for accounting or tax obligations. We do not send those payout details to the public results pages.

We may contact you about account verification, password recovery, orders, payments, ticket changes and issues affecting a service you requested. These are operational messages, separate from marketing subscriptions.

Newsletters require a separate subscription choice. Where email confirmation is requested, subscribing is completed only after that confirmation. We retain information needed to record the subscription and its status. Buying a ticket, creating an account or accepting the terms does not subscribe you to marketing.

You can withdraw newsletter consent using the unsubscribe route provided with the newsletter or by contacting us. Cookie preferences and newsletter subscriptions are separate choices. Withdrawing marketing consent does not prevent necessary messages about your existing order or account.

If you separately enable browser notifications, we store the subscription endpoint and keys needed to deliver them through your browser's push provider. Your browser lets you withdraw that permission. Account closure revokes the stored subscriptions. In-app messages can be addressed to relevant participants, such as members of an event, team or clan, and can record whether a message was read or dismissed.

Optional analytics helps us understand which pages and products visitors use and where people stop during ticket purchase. Where enabled and accepted, Google Analytics 4 receives selected events such as viewing products, adding to a cart, starting checkout and a verified paid purchase. Campaign labels can help us understand which campaign brought a consenting visitor to the site.

Purchase measurement uses product information, amounts and a pseudonymous transaction reference. Pseudonymous does not mean anonymous. Our measurement events are designed to exclude names, email addresses, postal addresses, ticket barcodes, account passwords and private form text. Private account and authentication pages are excluded from tag loading.

Advertising measurement and remarketing require the separate marketing choice and the relevant configured tags. These tools can relate a visit or purchase to an advertisement and help show FoM advertisements to people interested in the event. Rejecting optional tracking does not stop you using the shop or taking part in competitions. We do not upload customer email lists or enable enhanced conversions through your acceptance of these terms.

The Cookie Policy explains the controls, storage and enabled-service limits. Consent is the basis for optional tracking, under Article 6(1)(a). The cookie settings in the footer let you change your choice at any time. Newsletter permission is not permission for advertising cookies.

We use technical records such as IP addresses, device or browser information, access times, account actions and relevant order or seat changes to protect accounts, investigate faults and abuse, support participants and keep an audit trail. Access is limited according to staff responsibilities. Operational alerts can be sent through the communication tools used by the crew.

Support messages may contain information you send us voluntarily. Please do not send passwords, complete payment-card details or copies of identity documents by ordinary email. If we need to check an identity, we will explain why and request information proportionate to that purpose.

Security and support processing is based on providing the requested service, applicable legal obligations and our legitimate interests in preventing fraud, protecting people and resolving problems. We do not treat every visitor as having agreed to unrelated data use simply by browsing the site.

An event can include photography, recorded gameplay and live coverage. A nickname, voice or recognisable image in that coverage may be personal data. The context matters: a crowd shot is different from a close-up portrait or a separate promotional interview. Buying a ticket is not blanket consent for every use of your image.

Where a use requires consent, that consent must be requested separately. Contact the FoM crew about planned coverage or [email protected] about a specific image or recording, identifying it so we can review your request. Separate platforms used for broadcasts have their own privacy notices.

The event's admission rules and game-specific age restrictions still apply. A parent or guardian can contact us about a younger participant's data. We do not use acceptance of the event terms as a substitute for a child's or guardian's consent where the law requires it.

Authorised crew and service providers may receive the information needed for their task. Relevant provider categories include hosting and infrastructure, email delivery, technical support and logging, operational communication, payments and the sign-in provider you select. Public-facing information is limited as described above. Authorities and professional advisers may receive information where a legal duty, claim or dispute requires it.

Choosing an external service can involve its own processing. Google and Discord sign-in, Mollie payments, external maps and broadcast or social platforms each have their own privacy information. A link to an external website does not itself enrol you in that provider's service.

Some providers operate outside the European Economic Area. Transfer arrangements depend on the provider and service, and may rely on an applicable adequacy decision or contractual safeguards. Contact us for information about the recipients and safeguards relevant to your data, including how to obtain a copy. We do not claim that all processing stays in Belgium or that information is never shared with a provider.

Retention depends on the record and its purpose. Account information is used while the account supports your participation and services. Closing an account removes access and pseudonymises profile information, but does not automatically erase the records of orders, payments, tickets or past competitions.

Orders, invoices, payment and refund records are kept for the applicable accounting, tax and legal-claim periods. Competition history is kept to maintain understandable results and resolve relevant disputes. Support, security and operational records are assessed according to the incident, investigation and need for evidence. Records subject to a legal hold may need to be kept longer. You can ask which period or retention criteria apply to your particular information.

Browser storage has its own lifetimes, listed in the Cookie Policy. Newsletter subscription records are used until withdrawal, with limited information retained where needed to record the withdrawal and avoid unwanted messages. Removing an active record does not immediately remove every backup copy; copies remain subject to the backup and recovery process and must not be reused for unrelated purposes.

You can ask for access to your personal data, correction, erasure or restriction of processing. Where the conditions apply, you can request a portable copy of data you supplied for consent-based or contractual processing. You can object to processing based on legitimate interests and to direct marketing. These rights have legal limits, for example when an invoice must be retained or information is needed for a legal claim.

Email [email protected] with your request. We may ask for proportionate information to verify that it comes from the right person. We normally respond within one month. If a lawful extension is needed because a request is complex or numerous, we will explain that within the first month. You do not need to close your account to make a privacy request.

Consent can be withdrawn without affecting processing that was lawful before withdrawal. You can also complain to the Belgian Data Protection Authority, or the competent supervisory authority where you live or work. You do not have to give up other legal remedies to contact us first.

This version is dated 3 October 2026. We will explain material changes through the website and, where appropriate, a direct notice. A new purpose that needs consent requires a new choice; updating this policy does not silently grant that consent.