What we collect
We collect your response (Waitlisted, Reserved, or No email yet), storage size, later answers about ordering, shipping, and delivery, optional accessory answers, timestamps, a two-character country or coarse Cloudflare connection category, and keyed codes derived from your network address and a random browser token. The poll application does not store raw IP addresses, hardware IDs, names, email addresses, avatars, regions, cities, or exact locations. For new responses, we store a coarse browser family and operating system and internal anti-abuse flags. If you enter when your order email arrived, we store that time to the minute and the time you confirmed it. If you answer the estimated order availability question, we store your answer, By December 2026 or In 2027. If you answer the optional verification feedback question, we store one up/down answer under a keyed browser code. Steam verification processes Steam's numeric account ID, but the poll stores only a keyed code and the verification time. We do not receive your Steam name, email, avatar, or profile.
How we save it
Vote and limit databases are encrypted. The application uses keyed codes for network and browser identifiers and does not write raw IP addresses or browser tokens to its database or application logs. These codes are pseudonymous, not anonymous. IPv6 is grouped at the network level for duplicate prevention. Request, network, browser, and burst counters expire and are removed during later checks. A one-day anti-abuse observation table is pruned as new responses arrive. A one-time offline DB-IP Lite lookup added country labels to some older IPv4 codes; recovered addresses were not saved. Cloudflare processes connection information, including its browser challenges, under its own policies. Public results expose aggregate counts, country and storage breakdowns, order, shipping, delivery, accessory, order availability, verification, feedback, and promotion counts. The live feeds show recent response categories, storage size, country, derived shipping region, and time. Order-email times appear only as aggregate chart data. Internal identifiers and per-response anti-abuse flags are not public. The poll application does not build advertising or analytics profiles.
How responses work
The poll allows one active response per network slot. A signed random browser token in a secure cookie and local browser storage normally lets the browser that submitted a response manage it. A response you own can be changed or removed from another connection. If that token is lost, a browser on the same network may be able to change or remove the network's one response. The session does not directly reveal another browser's choice or capacity, but public totals and feeds can make a shared-network change inferable. Connections that look like VPN, hosting, mobile, proxy, or other shared services may be refused new responses because many people appear behind them. These classifications are heuristic and can be wrong. Rate limits and other anti-abuse checks can also pause new responses. The site may use browser challenges to raise the cost of automation, but they do not prove human identity and do not stop every bot. We keep exact detection signals, thresholds, and challenge rules private so they are harder to game. Steam sign-in is optional. One Steam account can verify one active response and can carry that response to another device or network. The Steam code is pseudonymous, not anonymous. If the same account verifies two responses, the older one stays active and the newer one is retired. Logging out keeps the response but removes verification. Steam verified shows only aggregate counts for verified responses.
Removal and retention
Removing a response removes it from active totals and releases its active vote slot. It does not undo results already seen or erase aggregate history. Some separate records may remain for integrity and abuse prevention, including keyed locks, short-lived observations until they expire, a private retirement record when duplicate Steam responses are merged, optional verification feedback, and promotion history. Active responses remain while the poll and its historical results need them. We do not currently promise an automatic deletion date for every record.
