Privacy
The public website uses aggregate content-quality signals. The private Discord support bot stores only the records needed to route, review, deliver, and reconcile a request.
A privacy-conscious analytics binding may record that a wiki search happened, whether it returned zero results, the broad category selected, and a bounded query-length bucket. The search words themselves are not sent or stored, and the optional event endpoint does not set a cookie.
Applications, tickets, reports, and deletion requests include the Discord account and server IDs, fixed workflow fields, timestamps, and a stable reference. Ticket content is available only through fresh, role-checked private reads; staff forum notifications contain metadata, not the submitted body.
Successfully delivered ticket content is scrubbed after the protected bridge acknowledges it. Minimal ordinary receipts are retained for no more than 30 days after acknowledgement; sensitive receipts for no more than 90 days. Pending workflows and human-reviewed deletion requests follow their documented state rather than being silently discarded.
Run /privacy in Discord to read the bot summary or request deletion. Deletion is human-reviewed because staff must reconcile eligible D1, Discord, local ticket, log, and backup copies before confirming completion. The bot does not claim that one button erased every copy.
The public website is not connected directly to the game database. A future dashboard connector must use a verified server-side session and return only records belonging to that account. Preview dashboard records are fictional.
Cloudflare may process necessary network and security data when serving or protecting the website and support Worker. Discord separately processes content submitted through its service. KrispyXI does not sell support data, create advertising profiles, or use a report to automate punishment.
