Render Ngt Labels Native renderer in the browser shell
Label Viewer Label API Label Docs
1D Barcodes 2D Barcodes GS1 and EAN Barcode Samples
Templates API FAQ About
Sign in -
Sign in Settings Provide a suggestion Report a Problem

About

Render Ngt Labels

Managed web front-end for the native Ngt renderer.

This page groups the project overview, the imprint details mirrored from the public trade site, and the privacy rules that apply to this managed web demo.

Back to Demo Support

About this project

Render Ngt Labels hosts the demo UI in the browser and proxies the rendering work to the managed backend that powers the native renderer. The page is structured so it can be deployed on a Linux server without requiring a desktop runtime.

Impress

Angaben gemäß § 5 DDG.

Frede DV Daniel Frede Bismarckstrasse 6 97209 Veitshoechheim Deutschland E-Mail: support@inetconnector.com Verantwortlich i. S. d. § 18 Abs. 2 MStV: Daniel Frede, Bismarckstrasse 6, 97209 Veitshoechheim

Important notice: This website does not provide investment advice and does not issue legally binding buy or sell recommendations. Every decision remains your own responsibility.

Privacy

This demo is intentionally lightweight and does not use analytics, advertising pixels, fingerprinting scripts, or third-party trackers. No cookies are required for the page to function.

  • The demo stores optional UI preferences, such as the last label, density, zoom, and API settings, in browser local storage only when you explicitly enable that behavior.
  • The label editor content is kept in the page state during the session so the renderer can update the preview, but it is not written to a database by the web front-end.
  • File uploads for local Ngt opening are used only for the current rendering request and are not retained by the page after the browser session ends.
  • If you configure an external API host, that value remains in your browser until you change or clear it, and the requests then follow the privacy terms of that external endpoint.
  • The managed backend may keep standard operational logs such as request time, route, status code, and source IP address for troubleshooting, abuse prevention, and service monitoring.
  • No personal data is intentionally sold, shared with ad networks, or used for profiling by this application.
For self-hosted deployments, the operator of the server is responsible for any additional retention, backups, access control, or logging policies configured outside this page.