Open data
Check the numbers yourself
Every verified response, exported live, with the identifier hashes stripped out. Nothing on the results page is a figure you cannot recompute from this file.
Aggregate figures are also available as JSON at /api/stats.
Columns
| Column | Type | Description |
|---|---|---|
| response_id | uuid | Opaque row id. Not linked to any person. |
| verified_via | enum | How the identity was confirmed: email (magic link) or discord_oauth. |
| country | ISO 3166-1 alpha-2 | Country the respondent plays from. |
| current_platform | enum | What they play CODM on today. |
| interest_level | enum | How strongly they want a supported PC option. |
| preferred_solution | enum | Single choice of preferred fix. |
| desired_features | pipe-separated | Multi-select feature list; may be empty. |
| cpu | text | Optional, free text, sanitised before publication. |
| gpu | text | Optional, free text, sanitised before publication. |
| submitted_at | ISO 8601 UTC | When the response was written. |
What is deliberately not in here
No email addresses, no IP addresses, and not even the salted digests of them. Publishing the digests would add nothing anyone can verify while creating a target if the salt ever leaked. Uniqueness is enforced by a database constraint described on the methodology page, and the row count here is the count of distinct verified identities.