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. The advertising ID the app’s ads report to Google is none of those: it does not say your name, but it does single your device out from other devices, and the GDPR treats it as personal data all the same — the “Analytics and advertising” section below says what it is.

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.

Cookies

The website uses a single cookie: ff_locale, which stores your language preference (kept for at most one year). The website uses no tracking, advertising or analytics cookies. FilterFC uses no cookies at all in the app; the language preference lives in an ff.locale record on the device. The inside of the ad strip is Google’s own surface, and what is kept there is not FilterFC’s to decide; what the app sends to Google is itemised below.

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. The app also connects to Google’s servers to fill the ad strip; what travels with that request is itemised in the “Analytics and advertising” section below. 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 Android app does carry advertising, in exactly one place: a strip between the count and the matches it counted. The ad is served by Google AdMob; it is the reason the app stays free. To fill that strip the app reports the following to Google: your device’s advertising ID (a resettable number Android issues), the app’s name and version, the device and operating system type, the language preference, and the IP address the request comes from. This is a different thing from the website measurement: the advertising ID does not say your name, but it does single your device out from other devices — which is why this page does not claim that the app collects nothing.

In the European Union, the United Kingdom and Switzerland, Google’s consent window appears when the app opens; no ad is requested and no strip appears until you answer it. That window’s wording is Google’s, and it describes what the hundreds of partners it lists are capable of — not what this app does. The concrete difference: FilterFC asks for no location permission and declares none to Android, so “precise geolocation” does not leave this app. The only identifier the app hands Google is the advertising ID named above.

You can change your mind afterwards. In the app, Settings → Privacy options reopens the same window; withdraw your consent and the strip disappears in that same session. That entry is shown only if you are in a region where consent is required, and is absent when it is not. You can also reset or delete the advertising ID at any time: on Android, Settings → Privacy → Ads.

The app carries no other form of advertising: no full-screen interstitial, no rewarded video, no notification ads; and no space is held for the strip in advance — if no ad arrives, that row is never born. What appears inside the strip is Google’s choice; FilterFC does not select it, and nothing travels back from the ad into the app. How Google processes this data is set out in its own policy: policies.google.com/technologies/ads

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.

Shared filter links

Share links starting with "/f/" carry only numeric criteria; they contain no information about who created them.

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. For the advertising in the app there are two controls in your hands: withdraw your consent from Settings → Privacy options, and reset or delete the advertising ID from Android’s Settings → Privacy → Ads. 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