Privacy, plainly.

This local website

The website has no accounts, payment forms, analytics, advertising trackers or cookies. Interactive previews use temporary page memory and reset when you reload. They do not send answers, scores or identities to Discord. The local preview server may record requests in its terminal; public hosting would need its own logging disclosure.

Using the Discord bot

Discord processes your interactions under its own policies. Bot operators and authorized staff may also have access to relevant records. Private menus reduce visibility to other members; they are not a guarantee of anonymity.

Practice results and sharing

Personal practice history is saved only when you choose to save it. Saving privately and sharing to a server leaderboard are separate choices. Saved summaries include scores, completion time and an account link; they do not include item responses. Shared results can show an alias, a display name or your Discord account, depending on your choice.

Saved practice records expire 90 days after quiz completion. Cleanup runs while the bot is online and on startup or relevant access after downtime. Research participation has its own separate opt-in and disclosures; saving or sharing a score is not research consent.

Competition records

Participating in lobbies and tournaments requires records such as Discord identities, registrations, match settings, responses and results. Competition identities and outcomes are visible within the participating server. Room codes, individual answers and evidence are excluded from spectator views. Closed competition records have a 90-day retention policy; active or unresolved events may remain until concluded.

Your controls

You can remove shared scores while keeping private history. Use /iq delete for the bot’s account-wide deletion flow. Deletion does not automatically remove previously delivered Discord messages, screenshots, exports or backups. Active competitions affected by deletion can require staff review.

For help with records or a privacy request, see support. Before public launch, the operator must provide a working privacy contact and confirm hosting and backup practices.