DATA HANDLING / UPDATED NOVEMBER 4, 2026
Privacy Policy
Your label data
Barcode values, ZPL source, CSV rows, VIN validation, images, PDFs, and exports are processed locally in browser memory. The conversion and export workflows do not upload label content to our server. The explicit “Decode with NHTSA vPIC” action sends the VIN to the official NHTSA API. There is no automatic VIN lookup.
Browser storage
Printer settings restore from localStorage. When you save a named preset, its configuration and source template persist in this browser until deleted. Pro access requires a signed-in account and online verification against current account-scoped payment state. A random browser installation ID is stored in an essential cookie and, when available, localStorage. Short-lived browser credentials are stored in an HttpOnly cookie. Legacy localStorage passes do not independently authorize Pro. Browser activations and credential references are stored with creation, verification and revocation times; they are not hardware fingerprints and IP addresses are not used as device identity. A pending-checkout cookie expires after 24 hours. Clearing site data removes local presets and credentials; sign in with your purchase account to verify paid access again. Contact support if your plan is missing. Private browsing may restrict storage.
Optional account and cloud sync
When Clerk is configured, you may sign in with an email verification code, password, or an enabled social provider to associate purchases and access saved presets across browsers. Clerk processes your basic account profile. Supabase stores your account identifier, configuration-only presets by default, and billing entitlement status. A ZPL source template or fixed label field values are synchronized only when you explicitly select template synchronization. Checkout IDs, license keys, and account tokens are not placed in preset URLs or public metadata.
Payments and license verification
Creem handles checkout, payment information, receipts, and licenses under its privacy policy. Our server sends product, checkout, and license identifiers to Creem to confirm access. Payment card details are handled by Creem rather than by the label workbench. Read Creem’s Privacy Policy.
Operational records and support
Cloudflare may process ordinary request metadata such as IP addresses, request paths, response status, performance timings, and access times for security, reliability, and aggregate analytics. Billing failure logs contain a checkout identifier, plan, error code, and diagnostic message. If configured, a billing alert provider receives these diagnostic fields to notify support. Application logs exclude ZPL source, barcode payloads, CSV contents, uploaded documents, and payment card details, and redact credential values. Support correspondence is used to investigate your request; avoid sending proprietary label contents or card details.
Your choices and contact
You can delete presets using the local preset controls or clear browser site data. Account cloud presets are isolated by your authenticated user identifier. For deletion of account data or other privacy requests, contact support@zplbench.com. Payment record retention and deletion may be subject to Creem’s legal obligations.