WHAT WE STORE, AND WHAT WE DISCARD

Accounts: There is no account. No email, no password, no sign-in, and nothing that identifies a person.
Your file: The file you upload is read in memory and never written to disk. What is kept is a summary of it: the figures, how rough each stretch of the session was, and a thinned-out copy of each measurement — at most 600 points, where your file holds tens of thousands. The frame-by-frame detail is not kept and cannot be recovered from what is.
Identifying fields: Identifying fields are thrown away as the file is read, before anything is stored: the machine's name, the number Windows uses to identify it, the monitor model, the driver's internal name, and any free-text box you may have typed into in the capture tool.
If you send a DxDiag: A DxDiag report is the other file this site accepts, and it is handled more strictly than a capture, because it carries more. It is read in memory, reduced to a fixed list of fields, and the report itself is never written to disk.
What a DxDiag leaves behind: Ten things are kept from it and nothing else: your display driver's version, its date, which graphics card it belongs to, how many serious faults Windows has recorded against this machine, the first and last of those dates, how far committed memory sits above physical memory, the machine's model name, and two of our own — which capture it belongs to and when it was attached.
What a DxDiag never leaves behind: What is refused is named rather than left to an absence: the machine GUID, any serial number, the PCI device key that identifies your installed card, your computer's name, the registered owner, and every file path, because a path carries an account name. A test fails if a field outside that list ever reaches the store.
Your link: A link you are given is a durable reference to one upload. It is not an account, it carries nothing about who you are, we cannot tell two uploads from the same machine apart, and anyone holding the link can see what it points at.
Sharing: Nothing is shared until you ask for it. A shared page is a different page: it carries the findings and not the machine, so no model, no part names, no driver versions and no crash history.
Where the population comes from: The comparison you are placed against is built from public Steam reviews. When somebody writes a review, Steam can attach a description of the machine they wrote it on, and that description is public. We read that block and nothing else: no review text, no name, no Steam ID, no profile.
What we keep from a review: What we keep from a review is the hardware and the month it was written: graphics card, processor, memory, and whether the machine is a laptop. We also keep Steam's own id for the review, which is what lets an interrupted collection resume without counting anybody twice. It is a public reference to a public review.
Consent: Those reviewers did not ask us for anything, which is the honest description of it. Nothing we publish names a reviewer or a review, every figure is a count over thousands of machines, and no page can be narrowed to one person.

WHO RUNS THIS, AND WHERE

This site is run by one person, under the name BD911-Coder. That is a pseudonym and not a legal name. It is a durable public profile with a working contact address, and for a beta that takes no money, keeps no accounts and stores no personal data, it is what you get instead of a company.

BD911-Coder on GitHub

The machine is in Turkey. It is a computer that person owns and operates personally, not a rack in a data centre, and anything you upload sits on a disk they control.

Write to [email protected]. That is the only published address; there is no postal address and nothing here needs one.

For simply reading a page, the server keeps no access log, no account and no cookie. Your address is never written to disk. To limit how fast one visitor can read or upload, it keeps a scrambled form of your address in memory, mixed with a random value made when the server started and thrown away when it restarts — so it cannot be turned back into an address by anything that is kept.

WHAT THIS IS AND WHAT IT IS NOT

No tool that accepts a CapFrameX file can prove that file is genuine. The hash inside it covers other hashes, not the frame data, so somebody editing the numbers leaves it perfectly self-consistent. We check what can be checked and say so plainly rather than implying more.

What we check: What is checked: the file's internal hash chain, that the frame arrays are the same length and the clock runs forwards, that the sensor readings agree with the frame rate claimed, and that the same file has not been submitted before. Aggregates use medians, so one accepted forgery moves little.
Money: We make no money from this. No ads, no affiliate links, no sponsored placement, no paid ranking, and nothing is for sale.
Valve: Not affiliated with or endorsed by Valve. Not associated with the CapFrameX project; we read its file format and nothing more.
Ratings: We never rate a component. A score here is a percentile, the share of a named population this machine sits ahead of, and it says nothing about whether a part is good.
Beta: This is a beta and the population is still small. Where a number rests on few observations, it says so beside the number.