xgEdge

Privacy

What this site collects

Very little. There are no accounts here, and the two forms that ask for your name are the contact form and the partnership enquiry form, which you only fill in if you want an answer. Visits are counted with Google Analytics and the site is paid for with Google ads, but both only after you have said yes to them. What follows is the short list of what does happen, the legal footing each item stands on, and then the longer list of what does not.

Who is answerable

The controller

The controller of the personal data described on this page, in the sense the General Data Protection Regulation (GDPR) gives that word, is xgEdgeStats. Questions about it, and every request under the rights section below, go to info@xg-edge.com.

If that name still reads as a placeholder, the site has not been deployed under a declared operator yet, and this page is describing the software rather than a service anyone is running.

The short answer

Three things, and a fourth you are asked about

A session cookie the site needs to check that a form was submitted from one of its own pages. A cookie that remembers whether you allowed analytics. Server logs that record requests. And, only if you said yes, Google Analytics counting which pages were read and Google AdSense showing ads.

If you write through the contact page or the partnership enquiry form, the name, company, email address and message you type are emailed to the operator so that you can be answered. The site itself does not keep them: they live in the operator's inbox, and are deleted from it when the conversation no longer needs them, or sooner if you ask.

No account, no payment details, no profile. Nothing you do here is tied to anything you did here yesterday, and nothing here knows who you are.

Legal basis

Why each of those is allowed

The session cookie, the consent cookie and the server logs are processed on the basis of legitimate interest (Article 6(1)(f) GDPR): a website cannot be served, kept secure or repaired without them, and none of them reveals who you are.

Google Analytics and Google's ads run only on your consent (Article 6(1)(a) GDPR), asked for before anything loads and withdrawable at any time from Cookie settings in the footer. Withdrawing it does not affect anything that happened while it stood.

A message sent through the contact form or the partnership enquiry form is processed to answer it, on the basis of legitimate interest (Article 6(1)(f) GDPR) — you wrote in order to be answered.

The footballers' statistics described further down are published on the basis of legitimate interest too: they are a factual record of public sporting events, of the kind every league table and match report has always printed.

Cookies

Ours, and Google's if you said yes

The site sets up to three cookies of its own. _xg_session is the standard Rails session cookie: signed, encrypted, holding nothing but the token that proves a form came from this site, and gone when you close the browser. consent holds one word, yes or no, for a year, and appears when you answer the question the site asks about analytics. matches_view appears only once you use the schedule's filter, and copies your saved leagues and last view so the page opens on them: league numbers and view settings, for a year.

None is an advertising cookie, none is read by anyone else, and nothing is stored against any of them on the server. Which language you are reading is decided by the address you are on rather than by a cookie.

If your answer was yes, Google Analytics sets its own cookies, _ga and one beginning _ga_, which hold a random identifier for up to two years so that two visits from the same browser can be told apart. Saying no, or clearing your cookies, removes them.

With the same yes, Google AdSense sets advertising cookies of its own — on this site ones such as __gads, __gpi and __eoi, and on Google's own domains ones such as IDE — which hold a random identifier for up to thirteen months so that the same ad is not shown endlessly, so that fraud can be told from traffic, and, where you have allowed it in your Google account, so that ads can be chosen from your earlier visits to this and other sites. Saying no stops them being set here; the ones on Google's domains you clear in your browser, and personalised ads can be switched off at adssettings.google.com.

Every cookie, who sets it, what for and for how long is listed on the cookies page, linked at the bottom of this one and in the footer.

Analytics

Counting visits, with your permission

If you allow it, the site loads Google Analytics 4 and sends it one event per page you read: the address, the title, and what the browser volunteers about itself. Google Ireland Limited processes that on our behalf, as a processor under Google's data processing terms, and shows us counts — which pages are read, from which countries, on what kind of device. We do not see you, and we do not try to.

Google Analytics 4 does not store IP addresses; it reads a rough location off the address and discards it. Google Signals and advertising features are switched off for this property, so the data is not joined to a Google account or used to show you anything anywhere. Reports are kept for fourteen months and then deleted.

Some of that processing happens on Google's servers in the United States. The transfer rests on the EU–US Data Privacy Framework, under which Google LLC is certified, and on the European Commission's standard contractual clauses in Google's terms.

You are asked once, and you can change your answer at any time from Cookie settings in the footer; saying no after yes removes Google's cookies. Say no and the site works exactly the same; the only difference is a page view that was never counted.

In your browser

Settings stored locally

The schedule remembers the competitions you saved as My leagues and the view you last left it on, under the key matches.leagues in your browser's own storage, and copies them into the matches_view cookie so the page can open on them. A few screens remember a view or a sort for as long as the tab is open, in storage the browser empties when it closes. Apart from that one copy, none of it leaves your device.

Clearing your site data removes it, and every page renders correctly without it.

Logs

The ordinary server record

Like any web server, this one records requests: the address asked for, the time, the response, the user agent and the IP address the request came from. That is what makes it possible to fix a page that is broken and to notice when something is hammering the site.

The logs are not read against individuals, not built into profiles, and not shared with anyone. They live in a fixed-size rolling buffer of about 30 MB on the server; when it is full the oldest lines are discarded first, and nothing is archived or copied off the machine.

Who else sees it

The processors, and the merchandise banners

The site runs on a server rented from Hetzner Online GmbH in Falkenstein, Germany, inside the European Union. Hetzner hosts the machine and the logs it writes, as a processor, and reads neither. Google processes the analytics described above, only for readers who said yes. A message sent through either form is sent through GoDaddy's mail service, which also hosts the operator's inbox, and is held there as any email is.

On pages with a merchandise card, your browser requests the card's banner and a tracking pixel from the servers of Impact (impact.com), the affiliate network Fanatics runs its programme through. Impact then receives your IP address, what your browser says about itself and the address of the page, and counts the banner's impression for Fanatics' affiliate programme. This happens whether or not you agreed to analytics: the banner is not behind the question the site asks. Impact handles that as a recipient in its own right rather than a processor of ours, and what it keeps, and whether it sets cookies of its own on its domains, is governed by its privacy policy, not this one.

Apart from that, nothing is sold, rented or shared with anyone else for any purpose. The one exception any site has to name is a lawful order from a court or authority, which would be complied with to the extent the law requires and no further.

Your country

Which shop a merchandise link opens

On club and competition pages the merchandise card links to a regional Fanatics shop: the one the site assigns to your country, such as the UK shop in the United Kingdom or the US shop in the United States, and the European shop for everyone else. To choose it, the site reads your approximate country from your IP address, on its own server, against a copy of MaxMind's GeoLite2 Country database that it downloads and keeps there.

Your country is used for that and nothing else, only while the page is being built. It is not stored, not written to the logs and not sent to anyone: not to MaxMind, which is the source of the database and receives nothing about you, nor to Fanatics, Impact or Google. If you allowed analytics, the card's events say which shop's link it carried, never your country. No question is asked first, because nothing leaves the server and nothing is kept; if your country cannot be read, you get the European shop.

What does not happen

The long list

No analytics beyond the one you were asked about — no heatmap, no session recording, and no pixel but Impact's beside a merchandise banner. No advertising beyond Google's, and none of it until you say yes. No other third-party script, font or asset loads from anywhere: the merchandise banner and its pixel load from Impact for every reader, as the recipients section says, and the two scripts that can load do not until you say so.

No accounts, no newsletter, no comments, and neither the contact form nor the partnership enquiry form keeps anything on the site. No profiling and no automated decision about you, because nothing here knows who you are.

The site is not a betting operator, takes no stakes, and has no commercial relationship with any bookmaker.

Worth being clear about

The database holds personal data — footballers'

The statistics on this site include named players and their season figures, licensed from sports data providers. That is personal data, and it is not yours: it belongs to professional footballers, and it describes their work in public competitions.

It is published here for the same reason a league table is published — it is a factual record of matches that were played in public. A player who wants their entry corrected or removed can write to the address below, and the request will be weighed the way the GDPR asks: their interest against the public's in a complete record.

Your rights

What you can ask for

Under the GDPR you may ask what personal data is held about you, have it corrected or deleted, have its processing restricted, receive it in a portable form, object to processing based on legitimate interest, and withdraw any consent you gave. Write to the address below; you will have an answer within a month, and you will not be charged for it.

In practice the honest answer to the first of those is almost always that there is none: the site holds no identifier that could connect a request to a person. You will get that answer in whatever detail you want.

You also have the right to complain to a data protection supervisory authority — the one where you live, or the one where the operator is established.

Security

How it is held

The site is served over HTTPS, and the server and database are reachable only by whoever administers them. Logs live on the server that produces them.

Nothing here is a promise that a server cannot be broken into. It is a statement that there is very little on this one worth breaking into it for.

Age

Not written for children

This site describes betting markets and is not intended for anyone under 18. It does not knowingly collect anything from children, and given that it collects almost nothing from anyone, it has no way to.

Changes

How you would know

If this policy changes, the revision date at the bottom of the page changes with it. There is no mailing list to notify, because there is no mailing list.

Contact

Questions about anything on this page go to info@xg-edge.com.

Read the cookies page Read the terms

Last revised 9 November 2026.