xgEdge

Privacy

What this site collects

Very little. There are no accounts here, no form that asks for your name, and no advertising. Visits are counted with Google Analytics, but only after you have said yes to it. What follows is the short list of what does happen, and then the longer list of what does not.

Who is answerable

The controller

The controller of any personal data described on this page is [operator not yet named]. Questions about it go to [contact address not yet set].

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 cookie that remembers which language you chose. Server logs that record requests. A cookie that remembers whether you allowed analytics. And, only if you did, Google Analytics counting which pages were read.

No account, no email address, no payment details, no profile. Nothing you do here is tied to anything you did here yesterday.

Cookies

One of ours, one that remembers your answer, and Google's if you said yes

The site sets a single cookie of its own, _xg_session. It is the standard Rails session cookie, it is signed and encrypted, and on a site with no accounts it carries essentially nothing — there is no identity for it to hold.

It is not an advertising cookie, it is not read by anyone else, and nothing is stored against it on the server. Which language you are reading is decided by the address you are on rather than by a cookie.

The second cookie is named consent, and it appears when you answer the question the site asks about analytics. It holds one word, yes or no, for a year. Nothing from Google loads while it is unset, and nothing loads if the word is no.

If the word is 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. Refusing, or clearing your cookies, removes them from the equation.

Analytics

Counting visits, with your permission

If you allow it, the site loads Google Analytics and sends it one event per page you read: the address, the title, and what the browser volunteers about itself. Google processes that on our behalf, under its 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 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.

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

Filter state, stored locally

The schedule remembers which competitions you last filtered it by, under the key matches.leagues in your browser's own storage. That never leaves your device and is never sent to the server.

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 are kept only as long as they are useful for running the site.

What does not happen

The long list

No analytics beyond the one you were asked about — no pixel, no heatmap, no session recording. No advertising and no ad network. No other third-party script loads from anywhere, and the one that can does not until you say so.

No accounts, no newsletter, no contact form, no comments. No data is sold, rented or shared with anyone for any purpose. No automated decision is made 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, bought from a data provider. 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.

Your rights

What you can ask for

Under the GDPR you may ask what personal data is held about you, ask for it to be corrected or deleted, object to its processing, or complain to your national data protection authority.

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. Write to the address below and you will get that answer in whatever detail you want.

Security

How it is held

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

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 [contact address not yet set].

Last revised 3 October 2026.