Privacy

Iterary is free to use without an account. This page says what the site collects, where it goes and why. Last updated October 2, 2026.

Kept in your browser

The game you are working on, recovery drafts, your theme and My library (the list of image links you add) are saved in your own browser's storage. They are not sent to Iterary. Clearing your site data deletes them.

If you sign in

Signing in is optional and uses Google sign-in through Google Firebase. It is only needed to save games to your account and to make short share links. When you do, Firebase stores your Google account id with the games you save (readable only by you) and with any short share link you create (anyone who has the link can open that game). Iterary does not store your name or email address with a share link.

Analytics

Iterary uses Google Analytics, which sets cookies, to count page visits and how people arrive through share links. Share links are removed from the address before it is counted, so your game is not sent. Cloudflare Web Analytics also counts visits; it uses no cookies.

Ads

The site loads Google AdSense and shows one ad unit beside the editor on desktop. Google may use cookies to show and measure ads. See how Google uses data from sites that use its services.

Import from TTS Workshop

When you import a Tabletop Simulator Workshop item, your browser sends only the Workshop item id to Iterary's relay, which asks Steam for the item's title and file link. Nothing about you is sent to Steam by the relay, and nothing is stored apart from a short-lived cache of that public item information. Your browser then downloads the file and its images directly from Steam's servers, so Steam sees that request like any visit to Steam.

Other services

Fonts load from Google Fonts. Images on cards and pieces load from wherever they are hosted; Iterary only keeps their links. The site is served by Cloudflare.

Questions? Open an issue on GitHub.