Privacy policy
Effective August 30, 2026. Last updated October 8, 2026.
Argusic (argusic.com) is operated independently. Contact for anything in this policy, including data subject requests: [email protected].
What we collect from visitors
Argusic runs no advertising and no fingerprinting, and reading everything on this site requires no registration. You may optionally sign in with GitHub to follow projects, which is the one case where we hold an account for you; what that stores is set out under "If you sign in" below. Our infrastructure providers process standard technical data (IP address, user agent, request logs) to serve and protect the site: Cloudflare (CDN and security) and our hosting provider. That processing is our legitimate interest in operating a secure service; the logs rotate on short retention and are not used to profile anyone.
Measurement
The public pages of this site load Google Tag Manager, a container the operator uses to run measurement tags such as page views. Depending on which tags are configured in it, those tags may set cookies in your browser and send data about your visit to Google, whose own privacy terms then apply. It does not load on the staging site and it does not load in the admin area.
If you would rather not be counted, browser settings and tracking-protection extensions block it, and nothing on this site is withheld from you for blocking it: every page, every log and every recording reads exactly the same either way.
Embedded videos
Some project pages carry a video of the test session. Until you press play, that video is a picture and a button: the image is served from this site, and nothing at all is requested from the video host, so no third party learns that you opened the page. Pressing play loads the player from youtube-nocookie.com, and from that point Google receives the request and its own terms apply. Every number and every line of evidence on the page is there whether you press play or not; the video is a rendering of a recording you can also download in full.
Outbound links, and what we count
Some links leave this site: to a project's own repository, to a cloud provider, to a shop. Where a link may earn Argusic a commission it says so beside the link itself, never in a footnote. When you follow one of those links we record three things and no more: which link it was, what kind of destination it went to, and when. No address, no browser, no cookie, nothing that could identify you or be joined up later. It is a counter, not a trail, and it exists so we can tell which comparisons people actually use.
Prices shown for hardware come from a retailer's own interface and carry the time they were read. Following a price link takes you to that retailer, whose own terms and privacy policy then apply.
If you sign in
Signing in with GitHub is optional and exists for one feature: following a project so you can find it again. It is not needed to read anything. When you sign in we store your GitHub numeric id, your login, your display name, your avatar URL, and the times your account was created and last seen, plus the list of projects you follow. That is the whole of it. We do not receive or store your email address, we request read-only access to your public profile and nothing else, and a follow is a private bookmark: it is never shown publicly and never influences a score, a verdict, or a ranking.
The session is a signed cookie. You can delete your account yourself on the profile page. It happens immediately and removes your sign-in record and your follows; nothing is kept except records that are not personal data, such as the public results and any project a request already put in review. The site owner can also delete an account, or stop it from sending test requests.
Comments
Discussion on this site runs on GitHub Discussions through giscus, and it is live on subject pages, run pages, and the servers page. The comment box is loaded from giscus.app, which in turn loads from GitHub, so opening one of those pages sends a request to both and their own privacy terms apply to it. That happens whether or not you comment, because the box is part of the page.
Posting needs a GitHub account and is entirely between you and GitHub: your comment is stored as a GitHub Discussion in a public repository, not in our database, and we store nothing about who wrote it. Reading a page never requires an account, and comments never affect any score or ranking.
Public subject data
Subject pages mirror public metadata about the projects Argusic tests (description, stars, license, topics) from each subject's own source, always with that source linked. Test evidence (logs and terminal recordings) contains the output of publicly available code running in an isolated machine; it is not personal data by design. If a recording ever captures something you believe is personal or should be removed, write to us and we will review it promptly.
Your rights
Where GDPR, UK GDPR, CCPA, or similar laws apply, you have the rights of access, rectification, erasure, restriction, portability, and objection, and the right to complain to your supervisory authority. If you have never signed in, most requests will simply confirm that we store nothing about you, because we build no profiles and there is nothing to build one from. If you have signed in, write to us and we will tell you exactly what your account row holds, or you can delete the account yourself on the profile page, which removes your follows with it. We never sell personal data.
If you email us, we keep the correspondence for as long as needed to handle it. Our mail is hosted on Google Workspace.
Changes
Changes to this policy are published on this page with a new effective date. The history of this page, like everything on Argusic, is version controlled.