Data handling and technical boundaries
Your LBX stays local in the public print bench.
The interactive page parses, binds, previews, and prepares output inside the browser. Selecting a local file does not upload the template or its field values.
Public print bench
Template bytes and edited values remain in browser memory. The demo has no upload endpoint. Browser and WebUSB permissions are still controlled by your browser and operating system.
On-premises pilot
The render API can run inside the customer environment. Access control, retention, logging and deletion are agreed before customer templates are processed.
Hosted pilot
A temporary instance is offered only with explicit access and retention terms. Logs must not contain template bytes or field values. It is not an anonymous public rendering API.
Input limits
LBX is treated as untrusted ZIP/XML/image input. Archive entries, expanded bytes, XML depth and nodes, decoded image pixels and output canvas size are bounded. Unsupported objects generate warnings rather than being presented as supported.
Printing limits
A rendered preview or raster job does not establish that a printer is online, that the right media is loaded, or that a physical label passed acceptance. QL raster support is intentionally limited to documented printer and DK-media profiles. System print and WebUSB each retain their platform constraints.
Fonts and layout
Cross-platform font substitution can alter wrapping and geometry. Pilot acceptance is performed with the customer templates, target fonts, printer and media.
Need a specific data boundary?
Choose browser-local, on-premises, or a bounded hosted pilot after a technical review.