Privacy
Learn how the default local-first workflow handles image editing, PNG export, and any future remote features.
In the normal browser workflow, portrait images do not need to be uploaded just to crop or export a token.
How image handling works
The main editor is designed so portrait images can stay in the browser while you crop, frame, and export them. That keeps the default experience simple and better suited for campaign art, client commissions, and private homebrew material.
PNG export is generated from the editor state on the client side. If you are only using the local workflow, the normal download action does not require the site to store your portrait image on a server.
The product requirements already describe upload as an adapter layer. If you later enable remote storage, document the storage provider, retention policy, and share-link behavior before turning it on in production.
If you add analytics, error tracking, or rate limiting in production, keep those disclosures in this page so the operational detail stays easy to find when users need it.
