Last changed 5 September 2026.
Without signing in you see only the entrance page. Nothing is collected there beyond what serving any page involves, which is described under "Other people's computers" below.
Using the site requires signing in. Signing in gives this site, through Supabase Auth, the Google account identifier, email address, display name and profile picture URL that Google returns for your account. That is the whole of it: no contacts, no calendar, no Drive, nothing else.
Once signed in, your deck list is parsed and matched inside your browser. Matching alone uploads nothing, logs nothing and stores nothing. The only request that leaves your browser on your behalf while matching is the one that loads a public Piltover Archive deck: the link you paste is sent to this site's own server, which fetches that page and caches the result for ten minutes. Nothing about you is attached to it.
Pressing Save stores one row: the deck list exactly as you pasted it, the name you gave it, which format you were matching against, and the times the row was created and last changed. Nothing derived from it is stored — the combos are recomputed in your browser each time you load a list, so a deck saved today is matched against tomorrow's catalogue rather than kept as a stale answer.
Only you can read your rows. That is enforced in the database itself by row-level security, which checks the signed-in account against the owner of every row on every read, insert, change and delete.
No advertising, no donations, no analytics, no tracking pixels, no play-rate or win-rate data, no profiling, and nothing sold or shared with anybody. There is no third-party script on any page of this site.
Sign-in and the saved decks run on Supabase, in a Postgres database hosted in the United States. The pages themselves are served by Vercel. Sign-in itself goes through Google. Every page also loads the Inter typeface from Google Fonts, which means Google sees the request and therefore your IP address; that happens whether you sign in or not.
This site sets no cookies. When you are signed in, your browser's local storage holds a session token so that you stay signed in between visits. Signing out deletes it.
Deleting a saved deck deletes the row. Delete account, in the same panel, deletes the account and every deck attached to it at once and for good; there is no copy kept and no waiting period. You do not have to write to anybody to make either happen.
Open an issue at github.com/GermanAbuArab/RiftCombo.