Artwork and local storage
The current editor stores multiple documents and recovery revisions in IndexedDB. Save project backup downloads an editable .pixelwall file. Reference layers remain in native documents; rendered exports omit them by default and offer an explicit Include reference layers option.
Clearing site data, removing an app profile, or browser/OS storage cleanup can remove local work. Download independent backups. PixelWall does not upload documents to a cloud project account.
Your analytics choices
On pixelwall.dev, public pages and both web editors share Privacy preferences. Required only is the default: optional analytics stay off until you choose Usage analytics or Enhanced diagnostics. Do Not Track and Global Privacy Control keep optional analytics disabled. You can change your choice from Privacy preferences at any time.
Usage analytics shares page categories, recognized navigation and download clicks, feature use, storage and export results, Pro interactions, and basic browser/device details with PostHog. Coarse referral categories describe the current page’s immediate source. Optional analytics use a stored browser identifier to recognize repeat visits; this identifier is not anonymous.
Enhanced diagnostics adds performance measurements and scrubbed error reports. No privacy level records sessions or automatically captures page text and clicks. Artwork, imported files, document and layer names, license and purchase identifiers, scripts, error messages, and full URLs are excluded from analytics.
Activity before permission is discarded rather than collected later. Withdrawing permission stops optional collection immediately and synchronizes the preference across tabs. If a preference cannot be saved, optional analytics stay disabled for that visit.
Downloaded desktop apps, the standalone browser bundle, and the CLI do not initialize optional site analytics. Local development and the private preview are excluded as well. Desktop update checks request release information separately; they do not upload artwork or optional usage analytics.
Payments and offline licenses
Stripe handles checkout and payment data. Online verification checks purchase-related records. The hosted store uses private cookies; the app stores a signed PW2 license locally for offline verification. The license includes a purchase identifier and must be kept private.
An existing PW1 recovery code can be sent to the explicitly configured storefront to exchange it for an offline license. Offline PW2 verification does not need to send the license or artwork to a server.
Website hosting processes requests needed to deliver pages and downloads. A downloaded standalone app serves its own editor assets locally. A retained license does not imply cloud project sync.