Privacy

What is collected

If you only play

• A random identifier in a cookie, so the same browser is recognised between visits. It is a random number. It is not derived from you or your device.
• The nickname you choose, which is kept on this browser and shown to the players in any room you join. Until you choose one you play under a random name, kept only in the tab.
• Your country, which Cloudflare works out from your connection. It is shown beside your name to the other people in the room. The country is all that is kept; your address is not.
• The first and the last day this browser came here, kept in the browser itself. On your first visit of a day the game tells the server only how long ago the first one was — today, the day before, within a week, or longer — and the server adds one to that day's total for it. Nothing that could tell you from anybody else is sent or kept, and the first day is forgotten after thirteen months.
• Whether the game was opened from a Home Screen icon. If it was, the server adds one to that day's total of app opens, once a day, and one to its total of people who came into a room from the icon. Nothing else is sent with it.
• Which page a visit started on, and whether a search engine or an AI assistant sent it. Only the kind of place is kept — a search engine or an assistant by name, such as Google or ChatGPT, or else a social site, another link or none — and never the address you came from. A written page that a search sent you to adds one to that day's total for the page as it is sent. The game adds one when the visit reaches it, when its first match kicks off, when it starts a sponsor checkout and when this browser comes back the next day, for which the page the first day started on is kept in the browser beside that day. These are daily totals; no identifier is sent or kept with them.

Not being counted

This browser can be left out of the counts the game keeps of the people who use it: its visits to the world, how long ago it first came, the page its visits started on once they reach the game, the rooms' daily totals of who arrived and who played, the day's count of matches, the reports of how its matches ran, and the views an advertiser is shown for their surface. The two days above are deleted when you ask. The choice is kept in this browser and nowhere else, so it is made once on each browser you use.

It does not reach three kinds of count. Cloudflare's page counter, named below, still sees each page this browser loads; it sets no cookie and cannot tell this browser from any other. A written page's view that a search or an assistant sent is counted as the page is sent, before this browser can say anything. And a count of something the site did still includes it: a match notice sent to this browser is counted as sent, and a goal it watches adds one to that goal's views.

If you ask to be told when somebody is playing

Your browser makes a push subscription, and it is stored here: the address the push service run by your browser's maker gave it, the key a notice is sealed to, and the field you asked about, or none for any field. Kept with it are when it was made and when you were last told or last walked onto a field, so that you are told at most once in six hours and never about a match you are standing in. No name and nothing from the cookies is stored with it.

When a field fills, a notice naming the field and how many are on it is sealed so that only your browser can read it, and handed to that push service to deliver. Turning the reminder off deletes the subscription here and in the browser, and one your browser throws away is deleted the next time a notice is sent to it.

If you sign in with Google

Signing in is optional and only needed to keep a profile, a credit balance and a friends list across devices. Google is asked for openid, profile and email, and what is stored is your email address, your name, your profile picture address and Google's own account identifier. No password ever reaches this site.

If you buy a surface

Payment is taken by Dodo Payments on their own pages. No card detail ever touches this site. What is sent to them is the amount and three identifiers for the surface being bought, and what comes back and is stored is their payment identifier, the amount, the currency and whether it succeeded.

If you write to us

The feedback form keeps your message along with the screen you were on, your window size and the field you were in. A report about a player keeps what you wrote.

What a match leaves behind

A goal clip is a recording of the simulation and carries the display names of the players in it. On a phone that can send one, the last goal of a match is also made into a video with those names on it, by the phone itself; it goes nowhere unless you share it. While you are in a room, that you are in it is stored, so friends can see you are about. It is deleted when you leave. Each room also adds to a few daily totals — how many matches had two or more people in them, and whether people came in from the map, a link, an invitation, a match notice or a goal clip — which name no room, no match and no person. The one exception is the pickup match on Foundry Football three evenings a week: each of those evenings keeps how many people were on a side at its kick-off and at its busiest, and still names nobody.

At full time, or when you leave, the game sends one short report of how the match ran on this device: how many frames it drew a second, how long its slowest frames took, how often the page stalled where the browser can tell, whether you were hosting, whether the device is a phone or a computer, how many were on the pitch, and for a guest the round trip to the host and the smoothing the game chose for it. The server adds one to a few daily totals for the ranges those numbers fall in, and the report itself is not kept. It carries no identifier, no field, no match and no name.

The first few times in a visit that you go from the globe down to the map, the game sends a report like it about that descent: how many frames it drew in the first two and a half seconds, how long its slowest frame took, how often the page stalled where the browser can tell, whether it was the first descent of the visit, whether the town had finished loading, whether the device is a phone or a computer, and which kind of browser engine drew it (Safari's, Chrome's, Firefox's or another). If the map ever stops drawing because of an error, it sends one note that it happened, with the same device family and engine. When the front page has loaded, and again if you press Play now on it, it sends one note of each with the same device family and engine and nothing else. These are filed the same way: a few daily totals, the report not kept, no identifier and no name.

Cookies

Three, all set by this site, all HttpOnly, Secure and SameSite=Lax. None of them is an advertising cookie and none is read by anybody else.

Name	What it is for	How long it lasts
outlol_principal	Recognises this browser between visits, so a surface you hold and credit you have stay yours.	365 days
outlol_session	Keeps you signed in after a Google sign-in.	90 days
outlol_oauth_state	Protects the sign-in round trip against forgery, and holds the page to bring you back to. Deleted the moment it comes back.	10 minutes

The browser also keeps some things on your own device:

• The nickname you choose, which is shown to the players in any room you join.
• Whether you have seen the controls hint, whether sound is on, the keys you play with, whether the ping readout is shown, and whether the pickup match had been taken off the page when it last asked. These are never sent anywhere.
• The first and the last day it came here, which leave it only as the bucket described above, and whether you asked not to be counted.
• A key the browser makes for itself, so a room can recognise it again without a sign-in. Only its public half is ever sent.
• If you ask to be told when somebody is playing, the push subscription, until you turn the reminder off, and the small script that shows a notice when one arrives. The script keeps nothing.
• For as long as the tab is open: your random nickname until you choose one, the words of a bid you were writing when you went to sign in, when the tab last reloaded itself after an update, and when it last heard from the world, so a reload is not counted as a new visit.

Your network address

Your IP address is read to count requests against a limit, so one browser cannot flood the service. It is combined with your browser identifier and hashed immediately; only the hash is stored, for 24 hours. The address itself is never written to the database and never logged by this site. Cloudflare, which hosts it, samples a tenth of requests into its own logs, and those carry the address.

What you upload

A picture you put on an advertising surface is stored and served publicly, at an address anybody can open, which is the point of it: it is an advertisement. It is kept while the surface is held and swept two hours after an abandoned attempt.

The file is stored as you sent it. Information your camera or editor wrote into the picture — the location it was taken, the device, the date — is not removed, so it stays in the file that is served. Strip it before you upload anything you did not make for this.

A goal clip is stored publicly too, at an address that cannot be guessed, and is deleted after seven days.

Who else is involved

• Cloudflare hosts the site, the database and the stored files, provides the relay a match falls back to, and counts how many people visit. Cloudflare Web Analytics sets no cookie, reads no cookie and builds no identifier, so it can tell how many times a page was opened and not whether the same person opened it twice. It is described at Cloudflare Web Analytics.
• Google, if you choose to sign in with it. Google tells this site your identifier, name, email and picture.
• Dodo Payments, if you buy a surface. They take the payment; this site never sees the card.
• The push service run by your browser's maker, if you ask to be told when somebody is playing. It carries the notice to your browser, sealed so that it cannot read it.
• An advertiser's own website, whose icon is fetched by this server to draw on their surface. If their site has no icon, Google's icon service is asked for one. Both requests are made by the server and carry nothing about you.

There is no tracking pixel, no advertising script and no profile of you anywhere. One third-party script runs, named above and named again in the policy every page is served: Cloudflare's cookieless page counter. The written pages — this one, the terms, the pages about the game and its advertising, and the sponsor board — are served a policy that also admits Google's advertising hosts, because a page to read is the one place an advertisement from a network could go. None is placed today, and placing one would mean naming it here first. Everything else, the game itself included, is served a policy that refuses a script from anywhere else, by the browser rather than by a promise, so a second one cannot be added there by accident.

Advertising

The advertising in this world is bought from this site and painted into the scene: the hoardings, the stands, the centre circle, the building. It is the same for everybody in the room. Nothing you do is used to decide what you are shown, because there is nothing to decide — the surface shows whoever holds it.

There is no third-party advertising network running on this site today, and no advertising cookie is set. If that changes, this page will say so before it happens, and it will say what those vendors do: a network such as Google serves advertisements using cookies, which you can read about at Google's advertising page and turn off at Google's ad settings.

How long things are kept

What	How long
Rate-limit records	24 hours
Match receipts	1 day
Goal clips, and their recordings	7 days
Abandoned uploads	2 hours
Sign-in sessions	90 days
A held surface and its creative	The 30-day term
Being in a room	Until you leave
A request to be told when somebody is playing	Until you turn it off, or your browser lets it go
An account, and the season records against it	Until you ask for it to be deleted

What you can ask for

Write to egevirgen@gmail.com and ask for a copy of what is held about you, a correction, or deletion. It is one person reading that address, so say what you want plainly and it will be done.

Deleting your account removes your email, your name, your picture address, your handle and your Google identifier. Records that have to survive it — that a payment happened, that a season was won — are kept without your name on them. You can also just sign out and never come back; signing out clears both cookies from your browser.

Children

This is not made for children under 13 and nothing here is aimed at them. If you are a parent and your child has signed in, write to the address above and the account and everything attached to it will be removed.

Changes

If this notice changes, the date at the top changes with it. A change that affects what is collected or who it goes to will be said plainly here rather than folded quietly into a paragraph.