Privacy Policy
Last updated: 4 November 2026
FilterFC (the filterfc.com website and the Android app) works without a sign-up and without knowing who you are; the filters you build stay on your own device. There are no ads on the website or in the app. Apart from the website's cookieless visit measurement, only two things leave your device: the technical error record sent when something breaks, and an anonymous return count that identifies nobody. The “Error records” and “Analytics and advertising” sections below itemise what goes with each. This page explains what is stored where, what is never collected, and your rights. Where a section applies to only one of the two, it says so.
Contents
No accounts, no identifying information collected
FilterFC has no sign-up and no accounts. No identifying information — name, e-mail address, phone number — is ever requested or collected. Neither is any identifier that would single your device out from other devices: the app does not read your device’s advertising ID and declares no permission to Android that would let it — the “Analytics and advertising” section below says why.
Your filters, the draft on screen, your language preference and, on the website, your theme preference are stored only on your own device: on the website in the browser's local storage and IndexedDB, in the app in the app's own local database. None of it is sent to us; no copy exists on our servers. The one case in which a criterion name can appear inside an error message is set out in the “Error records” section below. On the website, clearing your browser's site data removes all of it; in the app, uninstalling it — or, on Android, Settings → Apps → FilterFC → Storage → Clear data — does the same.
Hosting and access logs
The website is hosted on Vercel; match data files are served to both the website and the app from Supabase Storage through a content delivery network (CDN) — so the app downloads those files directly too. Apart from that, the only connections the app opens are the error record and the return count below; it never connects to Google’s ad servers. When something breaks, both the website and the app connect to Sentry; what goes there is itemised in the “Error records” section below. Like any web server, these providers may briefly process technical records such as IP address and client details to fulfil requests, for security and operations. FilterFC does not use these records to profile anyone.
Analytics and advertising
There are no ads on the website. To measure how many people visit the website, FilterFC uses Vercel Web Analytics: it places no cookie, stores no IP address, discards the temporary hash that distinguishes a visitor after 24 hours, and does not follow you across other websites.
What is collected is aggregate: the page address, the link you arrived from, country and region, browser and device type. None of it identifies you as a person. Because no cookie is placed and no personal data is stored, this website measurement does not ask for your consent.
The website and the app also carry an anonymous return counter, to see how many people come back to FilterFC without knowing who comes back. Your device keeps only two dates — the day you first opened FilterFC and the day of its last count — and never sends them. What it sends, at most once for each of six periods of use (the first open, the next day, the rest of the first week, days 7–29, days 30–89, and after that) for as long as the counter's local data is kept, is a short count: website or app, language, the app's version number, the week of the first open (not the day) and the period. The server only adds it to a total; it records no IP address, no device details and nothing that would tell one sender from another. The counter uses no cookie and, because it stores no personal data, does not ask for your consent; clearing your browser's site data on the website, or the app's data in the app, deletes both dates and the count starts over.
The Android app carries no advertising. Before version 0.3.0 it carried a single ad strip, filled by Google AdMob; that version removed it. The app now makes no ad request at all, does not read your device’s advertising ID, and the advertising ID permission (com.google.android.gms.permission.AD_ID) is not among the permissions it declares to Android. Google’s ad library has been taken out of the app package as well: there is no code in the app that could send an ad request.
Because there are no ads, the Google consent window that used to appear at launch in the European Union, the United Kingdom and Switzerland no longer appears; and because there is no consent left to withdraw, there is no control in the app that reopens it. FilterFC asks for no location permission and declares none to Android. You can still reset or delete your device’s advertising ID yourself at any time: on Android, Settings → Privacy → Ads.
The app carries no form of advertising: no strip, no full-screen interstitial, no rewarded video, no notification ads — none. No space is held in advance in case an ad arrives; there is no ad row to be born.
Carrying no ads has a second consequence: the app carries no tool that measures what you do inside it — the website's Vercel measurement has no counterpart in the app, and the only count the app sends is the return count above. Advertising will not come back without this page being updated first.
Error records
If something on the website breaks unexpectedly, a technical record of the event is sent to an error monitoring service called Sentry. What is sent is this: the error message and the line of code it happened on, the address of the page that was open, the browser and operating system version, the screen size and the time. The last few steps before the break are added too, such as the addresses you moved through, the files the page fetched and the name of the element you clicked. It places no cookie, records no IP address, and takes no picture or recording of your session.
The Android app sends a record to the same service when something breaks inside it. What is sent is this: the error message and the line of code it happened on, the app's version, the device model, the Android version and the device's language, and the time — along with the technical fields the device reports about itself, such as screen size, battery level and free storage; the last few steps before the break are added too, such as which data file it was trying to download. If the fault is deep enough to close the app, the operating system's own stack trace goes with it. There are no cookies on a phone; no IP address is recorded, no picture or recording of your screen is taken, and no list of what was on the screen is collected. A record is sent only when something breaks: opening the app sends nothing on its own.
The contents of the filter you build are not added to the record separately. There is one exception: some error messages say which criterion could not be processed, so a criterion name or a league code can appear inside the message itself — and the message is what gets sent. Your saved filters, the draft on screen and the match data you downloaded stay on the device.
These records — the website's and the app's alike — are stored in Sentry's European Union region (Germany) and are deleted after 30 days. They exist for one purpose: so that we can see what you saw break. The two do not travel the same way: the website's records go through filterfc.com rather than straight from your browser, so that content blockers cannot silence the report without anyone noticing. The app's do not pass through filterfc.com at all; they go straight to Sentry, because there is no such blocker in the way on a phone.
The code shown on the website's error screen is that record's number. Including it when you write to us lets us find the event; you are not required to. There is no such code in the app: a fault there is either a screen that names the problem or the app closing, and neither hands you a number.
Your rights (KVKK and GDPR)
Under KVKK article 11 and the GDPR you have the right to access, correct and delete your data and to object to its processing. Because the data lives on your device, you can exercise most of these rights yourself: uninstalling the app — or, on Android, Settings → Apps → FilterFC → Storage → Clear data — erases everything it keeps on your device. Because the app shows no ads and does not read the advertising ID, there is no advertising consent left to withdraw. For questions, write to the address below.
Changes
When this policy changes, the new text is published on this page and the date above is updated.
Data controller and contact
The data controller is the operator of filterfc.com. For any privacy question: info@filterfc.com