Privacy Policy
Last updated: July 7, 2026
What's in a crash dump
Minidumps — the small files in C:\Windows\Minidump\, typically under 2 MB — contain crash metadata: the stop code, the list of loaded drivers, kernel stack traces, and processor state. They generally do not contain your documents, photos, or browsing data.
Larger kernel or full memory dumps can include broader snapshots of system memory, which may contain fragments of sensitive data. We cannot inspect your file before you upload it, so we treat every dump as sensitive.
The instant preview never leaves your browser
The instant preview on our home page is computed entirely in your browser using JavaScript. That file is never uploaded — we do not see, keep, or have access to it.
Deep analysis — uploaded, analyzed, then deleted
If you choose the optional deep analysis, your crash dump is uploaded over HTTPS to our analysis server, where Microsoft's debugger (WinDbg/cdb) inspects it. We ask for your consent before this upload.
The uploaded dump file is deleted from our servers after processing — immediately after the analysis completes (successful or not). We reserve the right to retain de-identified or anonymized versions of the data we processed to improve our service; the raw dump itself is not kept.
Dumps uploaded before July 5, 2026 during our beta were retained under the retention terms disclosed at that time; email [email protected] and we will delete yours.
What we keep (de-identified)
- A parsed technical report (stop code, faulting driver and function names, symbol-resolved stack, Windows build), cached by the file's content hash for 30 days so that re-analyzing the same dump returns an instant result.
- A de-identified technical summary of each analysis (stop codes, driver names and versions, failure-bucket signatures, symbolized stack frames — never raw memory contents, never account identifiers) that we use to improve diagnosis quality and expand our driver and bug-check databases.
- Fix-outcome records (only if you connect a follow-up). Every report has a private link. If you later use that link to tell us how things went — either by uploading a new crash dump for comparison, or by tapping "no new crashes so far" — we record a de-identified outcome: which fix the report recommended, whether the crash recurred (and whether the culprit driver's build changed between the two dumps), how often you said it was crashing, and the time elapsed. These records are keyed to the crash's technical data (content hashes, stop codes, driver names) — never to your account or identity — and we use them to learn which recommended fixes actually work. Connecting a follow-up is always your choice.
Subprocessors
Deep analysis relies on a small set of providers: Amazon Web Services (Lightsail) for hosting, Cloudflare for CDN and TLS, Supabase for authentication, Stripe for payments, and Anthropic (Claude) for the plain-English explanation. Anthropic receives only a structured crash summary (bug check, faulting driver and function names, top stack frames) — never your dump and never raw memory.
Account data
If you create an account (via Google, Microsoft, or email), we keep your email address and basic profile information provided by the authentication provider. This is used solely for account management and your analysis quota.
Analytics
We use Cloudflare Web Analytics, which is privacy-focused and does not use cookies or track individual users. We also count anonymous product-usage events ourselves, first-party (for example: how many visitors selected a file, or started an upload) as plain daily counters — no cookies, no identifiers, no IP addresses are recorded with these counts.
Cookies
We use essential cookies for authentication (if you sign in) and localStorage to remember your consent choice. We do not use advertising or tracking cookies.
Data deletion
To delete your account and associated data — including any dump retained under the pre-July-2026 beta terms — contact us at [email protected].
Contact
Questions about this policy? Email [email protected].