Privacy

What this site collects, and why

Short version: DetectFPS is a static site with no accounts and no tracking of its own. It only collects what you type into the build form and, if you sign up, your email for the newsletter. Here is the whole list.

What is collected

Build submissionsWhat you enter on the submit form: hardware, model, camera count, inference time and the other numbers, plus the optional config paste, screenshot, source link, name or handle, email and notes. The form is handled by Netlify Forms, which stores the entries in the site's Netlify dashboard and emails a copy to the site owner.

Newsletter signupsYour email address, entered in the newsletter signup form on the newsletter page. The newsletter provider (beehiiv) stores it under its own privacy policy and handles unsubscribes; every issue has an unsubscribe link.

Hosting logsNetlify, which hosts the site, keeps standard server logs (IP address, pages requested, browser) for a short time for security and debugging. DetectFPS does not read or export them.

AnalyticsNone is running today. When one is switched on it will be GoatCounter, a privacy-friendly counter that uses no cookies and stores no personal data, and this line will say so.

Cookies and storageThe site sets no cookies. The dark/light theme choice is kept in your browser's local storage, on your device only. If you use the submit form, what you typed is also kept in that browser tab (to draw the build card on the thanks page) until you close the tab; it never leaves your device that way.

Why

Submissions exist to be published: the numbers, hardware, model, version and your name or handle (only if you gave one) appear in the builds database with a note that the build was submitted directly. Your email, config paste and screenshot are never published; they are used only to ask a question about the submission or to verify a number, then kept with the form entry in Netlify.

Newsletter addresses are used for the newsletter and nothing else. Prices and price drops are covered in the newsletter; there are no per-device alerts, so no other list exists.

How long

Published build data stays in the public dataset (it is downloadable as JSON). Form entries stay in Netlify until the owner deletes them, which happens after a submission has been added to the dataset or rejected. Newsletter addresses stay until you unsubscribe.

How to ask for removal or correction

Email hello@detectfps.com with the build id (shown on every build page, like db-155) or the email address you signed up with. Your name or handle can be removed from a published build on request, or the whole build if it is yours; newsletter addresses are removed by unsubscribing or by asking. Requests are handled by hand, usually within a week.

Affiliate links and sponsors

Some buy buttons are affiliate links, labelled as such; the retailer may know you came from DetectFPS, but no information is passed the other way. A sponsored “Featured build” slot, when present, is labelled on the page and gets no data about you.

Not affiliated with Frigate

DetectFPS is an independent community project and is not affiliated with the Frigate project. Nothing you send here goes to them.

Last updated 2026-10-19.