Security at PrinterVision

Last updated: 22 October 2026

Hosted in the EU

PrinterVision runs on Microsoft Azure in the West Europe region, in the Netherlands. The application, the databases and their backups stay in that region. There is no printer vendor's cloud or gateway in between: printers and collectors talk to PrinterVision directly.

A database per customer, with its own login

Every customer has its own PostgreSQL database. Each database is reached with its own database login, with a random password that is stored encrypted. That login can connect to its own database only: it cannot open another customer's database or the platform database, and cannot create databases or logins. A mistake in one customer's environment therefore cannot expose another's data.

Azure Database for PostgreSQL encrypts the data and its backups at rest. [TO CONFIRM: backup retention and geo-redundancy of the production databases]

Encrypted in transit

• The website and the application are only served over HTTPS (TLS).
• Zebra printers connect over WebLink with mutual TLS (TLS 1.2 or 1.3): PrinterVision presents its certificate, and each printer must present a client certificate before it is accepted.
• The collector, for Honeywell, SATO and other makes, only makes outbound HTTPS connections to PrinterVision: no inbound port is opened on your network. A collector is enrolled with a one-time code.

Sign in with Microsoft

People sign in with their Microsoft work account (Microsoft Entra ID). PrinterVision has no passwords of its own in the cloud, so your own policies apply: multi-factor authentication, conditional access and disabling an account when someone leaves all work as they do for your other Microsoft applications. A session ends after an hour without activity.

Control over who does what

• Roles with their own permissions, which can be limited to sites, so each team only sees and changes its own printers.
• New printers wait for approval before they are managed.
• Every change, and every sign-in with the address it came from, is written to the operation log of your environment.

Support access is visible to you

CaptureTech support only works in a customer's environment to help that customer [TO CONFIRM: only at the customer's request, or also for operations]. A support person signs in with their own CaptureTech account and works under their own name, marked "CaptureTech support", never as one of your users. Opening your environment is written to your operation log, so you can always see who was there and what they changed.

What we are still working on

We prefer to be open about it: the installer of the collector is not code-signed yet, so Windows may warn when you run it. Download it only from your own PrinterVision environment.

Reporting a vulnerability

If you believe you have found a security problem in PrinterVision or printer.vision, please mail security@capturetech.com. Our contact details for security reports are also in /.well-known/security.txt.

• Describe what you found and how to reproduce it; English or Dutch is fine.
• Give us reasonable time to fix it before you disclose it publicly.
• Do not access, change or delete other people's data, and do not disrupt the service (no denial of service, no spam, no social engineering).
• Never test against printers or networks that are not yours.

We confirm receipt, keep you informed, and do not take legal action against anyone who reports in good faith and follows these rules. [TO CONFIRM: response time and safe-harbour wording]