Concept – we are looking for design partners. The platform is in its validation phase and not yet available.
Security and privacy

Designed as if the cloud can't be trusted

The safest place for a document is a place it never goes. That's why documents stay on site, and why even a compromised cloud cannot read documents or push software to your devices.

The foundation

Who can do what, and above all what not

The cloud only manages

There is no command channel that lets the cloud run arbitrary commands on devices. Only signed configuration within a fixed schema, and a closed list of recovery actions with an audit trail.

Updates through a separate channel

Software updates are signed with keys kept apart from the management platform, with an offline root key. Devices refuse unsigned code and older versions.

Documents don't leave the site

Print jobs go from the PC to the node on site, and from there to the printer. The cloud sees no documents and no document names.

Confidential printing

Printed at most once, and only for the owner

The lifecycle of a confidential print job is formally modelled and verified with a model checker. That yields fixed rules which the software enforces exactly as modelled.

Release requires presence

  • NFC tags with a code that changes on every tap, or a QR code on the kiosk that is valid for at most 30 seconds
  • A phone is linked with a passkey and unlocked with biometrics
  • Wi-Fi never counts as proof that you are at the printer
  • Remote release is switched off for confidential documents

Never twice, never reprinted automatically

  • If it's not certain a document was printed, the owner is asked "Print again?"
  • Confidential documents are never automatically redirected to another printer
  • Support cannot print a confidential document
  • Two nodes on separate hardware; a node that unexpectedly loses both the cloud and the other node stops confidential delivery after 60 seconds
Printers and devices

Every device proves who it is

A certificate per printer

Every printer gets its own certificate from an issuing CA per customer, restricted to that customer's printer networks. The CA key is kept in a hardware-backed vault.

Locked printers

Printers that handle confidential documents only accept jobs from the node. A daily test checks that workstations cannot reach them directly.

No silent swaps

If the identity of a Locked printer changes, no more jobs go to it until two administrators confirm the change with a FIDO2 key.

Device identity in hardware

PCs, Macs and nodes have a key that cannot leave the device (TPM or Secure Enclave). A user token alone is never enough.

Storage on the node

Held jobs are stored encrypted, with a separate key per job. Backups and snapshots of the node contain no documents.

Documents in a throw-away process

Every document is converted in an isolated process without network access, which disappears after the job.

Management and access

Administrators have limits too

  • Partner and platform administrators sign in with passkeys or FIDO2 keys
  • Four-eyes approval with FIDO2 for bulk actions and new printer destinations
  • Customers are strictly isolated from each other, with tests on every route
  • Partners only see their own customers, and no document names by default
  • "Log in as" only with the customer's consent, for a chosen period, with a visible banner
  • Administrative actions in a tamper-evident audit log
  • The customer is notified of sensitive changes
  • Minimal permissions in Microsoft Entra, with a clear consent procedure
Privacy and compliance

Privacy by design, reviewed before launch

Privacy

  • Document names masked in overviews, logs, telemetry and tickets
  • Job trail kept for 90 days, aggregated counts for 2 years
  • Privacy mode and a DPIA template for customers
  • Export and deletion per user
  • Hosting in the EU (Azure West Europe)

What happens before the first customer

  • A threat model, reviewed by an external party
  • An external penetration test and a platform DPIA
  • A coordinated vulnerability disclosure policy
  • A reporting process under the EU Cyber Resilience Act

The platform is still in its validation phase. These steps are planned and not yet completed.

Questions about security?

Design partners get access to the security design and help shape the choices.