Last updated: October 2026
We collect information you provide directly to us when you:
We use the information we collect to:
The items below are everything the site writes to your device. None of them is used to build an advertising profile of you, and nothing follows you to other websites.
| What | Where | Why | How long |
|---|---|---|---|
oauth_state | Cookie | Proves a social sign-in came back from the same browser that started it. Without it somebody could finish a login on your behalf. | 5 minutes |
token | Local storage | Keeps you signed in between pages, so you are not asked for your password on every click. | Until you sign out |
consent | Local storage | Remembers your answer to the storage notice, so it is not shown again. | Until you reset it or clear it |
rm-newsletter-offer | Local storage | Remembers that you subscribed to the newsletter or dismissed the offer, so the offer is not shown again. | Until you clear it |
rm_auth_return | Session storage | Holds the page you were on, so that after signing in you come back to it. It is removed when it is used. | Until used or until the tab is closed |
pv:<product> | Local storage | A timestamp of the last counted view of a product page, so repeat requests are not sent for one hour. | Does not expire by itself |
dv:<thread> | Local storage | Records when this browser last requested a community thread view count, to suppress repeat requests for one hour. The thread author's requests bypass this browser-side limit. | Does not expire by itself |
theme | Local storage | Remembers whether you chose the light or dark theme, once you switch it. Until then the theme follows your system. | Until you clear it |
We use no advertising trackers and no analytics cookies. A paid placement, where we offer one, is a listing we choose to show, not something targeted with data about you. We do measure how the site is used, in a pseudonymous way, as described below. The typeface and the scripts of the site are served from here. Product logos and screenshots, however, can be loaded from image addresses supplied with a listing, and those can be on other companies' servers, which then see the request your browser makes for the image.
Our own visit counter works like this. Each page view adds one to a daily tally for the page opened, the site you came from, your country (looked up from a local database, so your address is not sent anywhere), your device type (desktop, mobile or tablet) and the hour. This counter does not store your IP address or browser details. To count unique visitors it keeps a daily fingerprint that changes every day. An hourly cleanup deletes the fingerprints of earlier UTC days, so a fingerprint is not kept for an exact 24 hours. Nothing is written to your device for this counter. If your browser sends Do Not Track or Global Privacy Control, your visits are not counted at all. Visits from browsers that report being controlled by automation software are not counted either.
Separately from that counter, we run a self-hosted Umami instance on our own server for aggregate statistics and a few events: sign ups, product submissions, newsletter confirmations and clicks to product websites (the event for a click carries the slug of the product). It sets no cookies. It stores individual page view and event records with a timestamp, the page address without its query string or fragment, the page title, the site you came from (domain and path, also without query string or fragment), your browser, operating system, device type, screen size, language and approximate location. Records are tied to a pseudonymous session identifier computed from your IP address and browser string with a salt that rotates monthly. The same IP address and browser combination therefore gets the same identifier throughout a month, so records from different visits in that month can be grouped together. Umami also stores a separate visit identifier. It reuses the identifier from its in-memory cache and recalculates it when that cache is absent, when the session identifier changes, or when the cached visit is more than 30 minutes old. The calculation includes the current hour, so recalculation within the same hour can produce the same identifier. The raw IP address is not stored. The data stays on our server and is not shared. Do Not Track, Global Privacy Control and automated browsers are not counted, and neither are site administrators.
Product pages have their own view counter, separate from the page analytics above. It stores a hash of your IP address and browser string that changes every day, never the raw address or browser string. An hourly cleanup deletes hashes whose last counted view was more than 24 hours ago. The server counts each product at most once per hour for the same daily hash; this deduplication resets at midnight UTC. Your browser stores a per-product timestamp in local storage to suppress repeat requests for one hour; the timestamp does not expire automatically. Automated browsers, Do Not Track and Global Privacy Control are not counted.
Community threads have a separate view counter. For readers other than the author, the browser stores a per-thread timestamp in local storage to suppress repeat requests for one hour. The timestamp does not expire automatically. This counter does not check Do Not Track, Global Privacy Control or the browser automation flag.
The first time you arrive we ask what may be kept on your device. Your answer is stored in the consent item above so we do not ask again. At present no feature of the site switches on or off according to that answer: your theme choice is written down when you switch it, whatever you answer, because that is something you asked for, and the visit counting does not use storage on your device. The necessary items are not offered as a choice, because switching them off would not be a preference. It would be a site you cannot sign in to.
We may use third-party services for authentication (Google, GitHub OAuth). These providers have their own privacy policies governing the use of your information. We only receive the basic profile information necessary for account creation.
We retain your account information for as long as your account is active. You can request deletion of your account and associated data by contacting us.
Statistics records in our Umami instance stay on our server. We have not set up any automatic deletion for them, and the monthly rotation of the session identifier only changes how new records are grouped. It does not delete older records. The daily fingerprints of our own visit counter and the hashes of the product view counter are deleted by the cleanups described above.
If you have questions about this privacy policy or your personal data, please reach out at contact@radarmakers.com or through the contact page.
What may we keep on your device?
Signing in stores a token on your device to keep you signed in. Social sign-in also uses a five-minute cookie to check that the login return matches the browser that started it. If you switch between the light and dark theme we remember that too, because you asked for it. We use no advertising trackers and no analytics cookies. We do count visits in a pseudonymous way, with our own counter and a self-hosted Umami, and Do Not Track or Global Privacy Control turns that off. Your answer here is saved so we do not ask again; at the moment it does not change what the site does.