Your screenshot

What happens to it

• It is held in memory for the length of one request, resized, and sent to the configured vision provider to read the champion portraits.
• It is never written to disk, never put in a database, and never attached to an analytics event.
• It is never logged. Error logs record an error code and a duration — never image bytes, and never the provider request body that contained them.
• Once the response is sent, the bytes are garbage-collected. There is nothing to delete later because nothing was kept.

Summoner names

A champion-select screenshot usually shows the names of nine other players. The vision model is instructed to ignore names and chat entirely, and the response schema has no field they could be returned in — only champion names, roles and confidence values can come back.

What is stored

• Anonymous counters: which step ran, how long it took, how many champions were read, the recommended champion and its score.
• A random session id generated in your browser and kept in sessionStorage. It groups the events of one visit and is discarded when you close the tab.
• Your 👍 / 👎 on a recommendation, with the composition it was made for, so the scoring model can be improved.

No accounts, no cookies, no third-party analytics.