Privacy, plainly.
This page explains the small amount of information KeyKatana uses to run a match, remember a preference, protect its forms, and answer messages.
Current service state: KeyKatana does not currently show ads and does not set advertising cookies. We do not run third-party analytics on the game. If that changes, this page will be updated before those tools are used.
Gameplay identifier and match records
When you start a game, the site uses a random first-party browser identifier named inkblade_player. It is stored as an HttpOnly, SameSite=Lax cookie for up to one year. HttpOnly means page scripts cannot read it. This lets the game recognize the same browser on later visits, but it does not contain your name or email. The server stores a hash of the identifier for browser totals; the original token is not stored in the player table.
Match summaries use a random match ID and record the mode, whether the opponent was a bot or human, start and end times, both scores, outcome, and optional early finish time. A persistent player ID is not linked to an individual match summary. The hashed browser identifier and match summaries are retained for site administration until the operator removes them. Temporary room identifiers and live game state are cleaned after inactivity.
Sound preference
If you change the sound setting, the choice is saved in your browser’s local storage under inkblade-sound. It stays on that browser and is not used to identify you on the server. You can clear it in your browser’s site data.
Contact and copyright forms
If you submit a contact or copyright notice form, the operator receives the name, email, message, and the additional details you choose or are asked to provide. Those submissions are stored in the site’s operator inbox and may be used to review the request and reply by email. The operator may manually delete them; no automatic deletion date is promised. Copyright notices can include personal details that you should provide only if you are comfortable sharing them for this purpose.
Security and administration
Submitting forms uses a short-lived rate limit to reduce spam. The server uses a keyed hash of the trusted request address for this limit rather than saving the raw address in the application’s rate-limit table. If an admin signs in, an HttpOnly, SameSite=Strict fruit_admin session cookie is used for up to eight hours. It is only for the operator’s admin area.
Cookies and browser controls
The site operator chooses the hosting and database providers used for the live service. These providers may process connection details, such as your IP address and request details, to deliver and protect the service. Their own privacy notices describe their logs and any cookies they set. This site does not promise or control a provider's log or cookie lifetime.
The game identifier and admin session cookie are first-party service cookies. The sound choice is local storage, not a cookie. You can block or clear site storage in your browser; doing so may end a match, reset sound, or make a new anonymous player record on your next game.
Questions and requests
Use the contact form to ask about this notice or request deletion of a contact submission. Deleting the browser cookie in your device does not by itself identify or remove a previously stored hashed player record.
Updated November 4, 2026.