This isn't a legal document — it's a plain description of what CheckMyARM actually does with your data today, based directly on how the app is built. See About for how compatibility classification works, or How CheckMyARM Thinks for the reasoning behind the recommendation itself.
We don't want — or need — to see anything that would invade your privacy. CheckMyARM was designed with a privacy-first mindset: before anything else was built, the question was "what's the least we could possibly look at and still answer this honestly?" Everything below follows from that answer, not the other way around.
That's why CheckMyARM intentionally avoids collecting documents, passwords, browsing history, personal communications, file contents, and other sensitive information — not because we promise to handle them carefully, but because none of it helps answer the question you're actually asking: will my stuff work on Windows on ARM? The technical observations we do use exist for one purpose — building your assessment — and nothing else.
We never retain your assessment. If you choose to save your work — exporting it to continue later — that's your decision, not ours; nothing about how CheckMyARM works requires us to keep a copy on our end. Real privacy by design is achieved by minimizing what's collected and how long it's kept, not by building bigger locks around ever-growing stores of data. We can't promise perfect security — no one honestly can — but we can, and do, promise there's simply less here to protect.
When you run a scan, the scanner sends your browser (and then our server) a list of your installed applications, some basic device information, and the compatibility results we look up for them:
Sharing your own compatibility findings with the community is optional, and signing in with Google or GitHub is optional too — CheckMyARM works fully anonymously if you never do either.
CheckMyARM currently:
Scan sessions are temporary. They exist primarily so we can generate your report and let you refresh it later without re-scanning — not as a permanent record of your machine.
Compatibility contributions are different: if you share what you found about an app, that contribution is intentionally kept, because it becomes part of the shared compatibility database that helps everyone else's reports.
Your personal assessment notes — decisions, priorities, and comments you add in your Workspace — are never sent to our server at all; they live only in your browser, and you can export them anytime to save your progress or continue later. Community contributions are different: those are stored on our server, and we don't yet have self-service export or delete tooling for that specific data. That's a real gap, and something we intend to address in a future update.
You can share what you found about an app's ARM compatibility without signing in — we recognize your browser with a cookie so you don't end up voting on the same app twice, not by anything tied to your identity.
Signing in is entirely optional, and never required to use the scanner or contribute. If you sign in after already contributing anonymously, your prior contributions move to your account automatically.
If you change your mind about an app, resubmitting updates your existing answer in place — it doesn't create a second, conflicting entry.
CheckMyARM relies on a small number of outside services, only where the app actually needs them:
We believe compatibility information is valuable, but personal inventories are not. CheckMyARM collects only what's needed to generate your report and improve the shared compatibility database — nothing more.