Privacy and Data Handling

LabelFlow Pro is built around a local-first architecture to protect sensitive business data. This page documents our data handling practices, local processing model, and the role of Lemon Squeezy for secure payments and licensing.

Privacy approach

Local-first workflow

Core label preparation tasks are designed to run in the browser, including layout editing, field mapping, barcode generation, serial workflows, and print preparation.

No forced cloud workflow for core label work

LabelFlow Pro is designed so users do not need to route working label data through a cloud-only workflow just to design and print labels.

Suitable for business-sensitive workflows

This matters when working with internal SKUs, shipment references, customer records, stock identifiers, asset tags, and other operational data.

What is handled in the browser

  • Template editing: label size, layout, positioning, spacing, and visual structure
  • Field mapping: binding spreadsheet fields to text, barcode, QR, or serial elements
  • Barcode and QR generation: inside the active label workflow
  • Sequential numbering: for serial-based label jobs
  • Print preparation: preparing output for the browser print workflow

What can still involve network activity

Website delivery

The website, application files, stylesheets, images, fonts, and related assets are delivered through normal web hosting infrastructure.

Payments and licensing

LabelFlow Pro uses Lemon Squeezy for checkout, payment handling, subscription-related flows, and licensing workflows. When users purchase or activate paid access, those actions may involve Lemon Squeezy services and related network requests.

Analytics, diagnostics, or support systems

If analytics, usage monitoring, error logging, or support tools are enabled, some technical or usage-related metadata may be transmitted as part of those services.

Payments and Licensing

Lemon Squeezy

We use Lemon Squeezy as our Merchant of Record to handle all payment processing, checkout flows, and subscription management. This ensures your billing data is handled by a PCI-compliant, secure financial platform.

License Activation

Commercial license activation and periodic seat verification require communication with our licensing servers and Lemon Squeezy to maintain active Pro features.

Data Segregation

Your working label data (spreadsheets, SKUs) remains in the browser and is never shared with Lemon Squeezy or our payment infrastructure.

How data is handled

LabelFlow Pro is designed so that core label preparation workflows are handled directly in the browser. This includes template design, data binding, barcode generation, serial numbering, and print preparation.

Working label data such as spreadsheet content, SKUs, and label values is processed locally as part of the active session and is not required to be uploaded to a central server for normal use.

Payment, subscription, and licensing workflows are handled separately through Lemon Squeezy. These flows may process customer and transaction-related data as part of checkout and account management.

Frequently asked questions

Do I need to upload working label data to use the core workflow?

LabelFlow Pro is designed so that core label preparation tasks can be handled in a local-first browser workflow rather than requiring a cloud-only process.

Does local-first mean completely offline?

Not necessarily. Local-first describes the core processing model. Full offline capability depends on how the application, assets, and related services are deployed.

Who handles payments and licensing for LabelFlow Pro?

LabelFlow Pro uses Lemon Squeezy for checkout, payment processing, subscriptions, and licensing-related workflows. Core label preparation is positioned around a local-first browser workflow, but commercial transactions and license handling are separate from that core processing model.

Is LabelFlow Pro suitable for privacy-conscious businesses?

Yes. The product is intentionally positioned for workflows where users prefer to keep core label preparation tasks closer to the browser and away from unnecessary cloud handling.

Start with one template. Scale to full batches.

Test the workflow with your own data and move from manual edits to repeatable label production.

Start Free