Cookies

What this site sets

• qt_id — set only if you choose to raise your daily limit by confirming an email. It holds a signed note saying “this browser proved a mailbox”, and nothing else: not the address, not a hash you could reverse, not a profile. You can discard it from the home page.

That is the whole list.

What is kept in the browser, but is not a cookie

Your recent jobs are remembered in this browser's local storage, so that a result page you come back to still knows the link is yours. It is never sent to a server — the token that proves a job is yours travels in the part of the URL after the #, which browsers do not transmit. Clearing site data removes it.

Other people's

• Page-view counting — Google Analytics, told to store nothing before its own code loads: no cookie, and no identifier kept between visits, so there is nothing to join one visit to the next. It counts which pages are read, from roughly where, and what linked here. Result pages are counted without their link, which is the part that would identify anything.
• The bot check — the thing that decides whether a submission is from a person — may set a cookie of its own while it decides. It is doing bot detection, not tracking, and it only runs on pages with a form.
• The donation page sets whatever it sets, but only after you have followed a donate link and left this site. Nothing of its is embedded here.