Cookies and local storage

Why there is no banner

The right reason is not 'there is no cookie' - the Belgian law of 13 June 2005 covers everything written to your device, cookie or not. The right reason is that everything we write is strictly necessary for the service you asked for: keeping you signed in, making the app work without a network, remembering the language you chose. Nothing is there to follow you, profile you or resell you. The day we added a YouTube video, a map, a captcha, a chat widget or an ad pixel, this page would stop being true and a banner would become mandatory. That is why we do not add them.

On aftermatch.be, the site you are reading

Two things, and that is all. The Oakeye traffic measurement, which we host ourselves: no cookie, no identifier that follows you, your IP address and browser processed then dropped within the second - the privacy policy sets out the mechanism. And a language cookie, set only when you switch to French, Dutch or English, so the question is not put to you again on the next page. No form, no account, no trace of your visit tied to you.

On app.aftermatch.be, your team's app

One session cookie, set when you sign in. It is what recognises you from screen to screen; without it there is no app. It lasts 30 days, and goes when you sign out.

A language cookie, as on the site, set when you change language in your profile.

A service worker and two caches. The first keeps the app's screens so it opens instantly, even without a network. The second keeps the server's latest answers - dashboard, rankings, squads with names, reasons from a counted match - so the screen still opens when coverage drops. Uploaded images stay there for thirty days. This is what makes aftermatch work in a clubhouse with no bars; it is also what leaves your teammates' names sitting on your phone.

A local database, called aftermatch, holding one kind of entry: the ballot you confirmed while the network was down. It sits there in clear text - the best, the worst, and your two reasons - until it goes out. That is the price of working offline, and you should know it.

Two traces tied to reminders: a local key remembering that you dismissed the prompt to turn notifications on, so it is not pushed at you again, and, if you did turn them on, the subscription your browser creates with its relay. You clear the first along with the site data; you switch the second off from your phone's notification settings.

The same traffic measurement as on the site, with the same cookie-free setup. It does not read your account, your team or your ballots.

On club.aftermatch.be, the club space

A session cookie separate from the app's, with its own, shorter life: twelve hours. It is a desk tool for administering a club, not an app you keep open on the bench. Nothing else is placed there, and the confirmation page a club receives during a claim works with no session and no cookie at all.

No third parties, and that is a rule

No Google Analytics, no share button loading a script, no font pulled from a third party, no embedded video, no map, no captcha, no chat, no pixel. If a video demo ever appears, we will host it ourselves - that is what lets you watch it without a third party watching you. This rule is not a press release; it is what makes the absence of a banner defensible.

Clearing everything

On the site there is nothing to clear but the language cookie. In the app: uninstall it from your home screen, or open your browser settings and clear the site data for app.aftermatch.be - that takes the cookie, the caches, the local database and the notification key in one go. Reminders are switched off separately, in your phone's notification settings.

One thing to know: signing out currently clears neither the caches nor the local database. That is a gap we will fix, and it matters if you lend your phone or use a shared device. Until then, clear the site data.

Contact

A question about these pages, a report, a request about your data: contact@aftermatch.be. You get an answer, and we tell you what we do with it.