Prinect Bridge — Plugin Terms

These Plugin Terms supplement the ChromaChecker End-User License Agreement (the "EULA") and apply only if you install or use the Prinect Bridge Plugin. Capitalised terms not defined here have the meaning given in the EULA. In the event of conflict, these Plugin Terms prevail for matters specific to this Plugin; the EULA governs everything else (EULA §2.4).

Acceptance. These Plugin Terms are accepted by an administrator of your Organisation, not by individual operators: using this Plugin means connecting ChromaChecker software to your Heidelberg Prinect installation with credentials your Organisation holds, and it can carry production data — including personal data — onto your network and into your ChromaChecker account.

1. What this Plugin does

Prinect Bridge reads press information from a Heidelberg Prinect installation on your network and makes it available inside CC Capture. It can:

• browse the fleet of press devices your Prinect installation exposes, and show their live status;
• track the devices you select, polling them on a fixed schedule;
• attach selected production values to colour measurements CC Capture sends, so a measurement carries the job it belongs to; and/or
• publish those values to an MQTT broker your Organisation operates.

Attach and publish are chosen per device and per parameter, and both are off unless you switch them on.

This Plugin only reads from Prinect. It issues HTTP GET requests and never writes to, configures or controls your press or your Prinect installation.

2. Heidelberg is your supplier, not ours

ChromaChecker builds and supplies the Bridge. You obtain the Prinect API licence and the credentials from Heidelberg.

• Access to the Prinect API requires the ADI Prinect licence and a Prinect user account with the API right. Both are issued by Heidelberg, or by your Heidelberg dealer, directly to you.
• Heidelberg may charge a fee for that licence. Any such fee, and the terms on which it is granted, are a matter between you and Heidelberg. ChromaChecker receives no part of it and cannot obtain, extend or renew the licence on your behalf.
• Heidelberg's own terms govern your use of Prinect and of its API. ChromaChecker is not a party to them.
• If the licence is absent or expired, or the account lacks the API right, Prinect refuses the request and this Plugin reports it as a configuration fault and stops polling. That is the expected behaviour, not a defect.

3. What data leaves your computer, and where it goes

Three destinations, and they are separate decisions:

(a) To your Prinect server — only requests. Authentication (HTTP Basic) and the identifiers of the devices and jobs being queried. No measurement or colour data is sent to Prinect.

(b) To your MQTT broker — only if you enable publishing, and only the parameters you tick. The catalogue is production context: device status, speed, activity, totalizer, workstep identifier and name, job identifier and name, job customer name, and employees assigned to the device. Published to prinect/<device>/state (retained), prinect/<device>/event, and an availability topic under prinect/bridge/<machine>/availability, where <machine> is an identifier derived from this computer's network adapter address.

Colour and measurement data are never published to MQTT. That restriction is built into the Plugin, not left to configuration.

(c) To ChromaChecker — only if you enable attach, and only the parameters you tick. The selected values travel as a small production-context block (soft-capped at about 2 KB, individual values truncated) inside the measurement your operator sends. Values older than the configured freshness limit are dropped rather than attached.

3.1 Personal data — read this before enabling

Two parameters in the catalogue are not machine telemetry:

• employees — the people assigned to the press. This is personal data about your staff.
• job customer — the name of the customer whose job is on press. This is your commercial-relationship data, and may be confidential to that customer.

Enabling either of them for publish or attach means that data leaves this computer. Your Organisation is the data controller for it, and is responsible for having a lawful basis, for informing the people concerned, and for any confidentiality obligation owed to your own customers. Both are off by default. If you have no need for them, leave them off.

4. Credentials, and where they are stored

• The Prinect password is stored in the operating system's credential store — macOS Keychain or Windows Credential Manager — under the service name CCCapture-prinect_bridge, with the account <host>|<username>. The username and the server address are kept in the application's own settings.
• Fallback, disclosed deliberately: if the operating system's credential store is unavailable on a machine, the Plugin stores the password in the application's settings instead, and records a warning in the log. This keeps the Plugin usable on a locked-down workstation, but the password is then held with the protection the settings file has, not the keychain's. If that is not acceptable on your site, ensure the credential store is available before configuring the Plugin.
• Use a dedicated Prinect account with only the API right, rather than an administrator account.

5. Security and network behaviour (EULA §7.5)

Outbound, on your local network:

• No inbound ports. This Plugin opens no listening socket of its own.
• No background service. It runs only inside CC Capture, only while enabled.
• No traffic to ChromaChecker other than the production context attached to measurements CC Capture already sends (§3c).
• Rate limiting. The Prinect API is throttled site-wide to 2 requests per second, shared with every other integrator on your site. This Plugin spaces its requests at 600 ms or more so that it cannot exhaust that budget for other systems.
• Your MQTT broker is yours to secure. MQTT on its default port carries no encryption and no authentication unless you configure them. The payloads described in §3(b) — job names, customer names, employee assignments — would then be readable by anyone who can reach the broker on your network. ChromaChecker does not operate the broker and cannot secure it for you.
• Publishing requires the IoT Bridge Plugin, which owns the MQTT connection. Without it, publishing is unavailable and the Plugin says so; browsing, tracking and attach are unaffected.

6. Who administers what

• Heidelberg issues the ADI Prinect licence and the API credentials.
• Your Organisation's administrator decides whether this Plugin may be used, supplies the Prinect host and account, operates and secures the MQTT broker, and decides which parameters may be published or attached — including the two in §3.1.
• An operator selects which devices to track within those limits.

7. Licence and evaluation status

This Plugin is licensed under EULA §2.4: to your Organisation and assigned to a specific computer. During the evaluation period it is available for testing without a separate ChromaChecker fee. This is separate from, and does not replace, the Heidelberg licence described in §2 — you may hold one without the other, and neither party's licence covers the other's software.

8. Availability, support and liability

• Prinect availability is not a ChromaChecker defect. If your Prinect installation is unreachable, its licence lapses, its credentials change, or Heidelberg alters the API, this Plugin may stop working through no act of ChromaChecker. EULA §9 (Disclaimer of Warranties) and §10 (Limitation of Liability) apply.
• This Plugin is a reporting bridge, not a control system. It does not drive, adjust or stop a press, and nothing it reads should be relied on as a safety or interlock signal.
• ChromaChecker support covers the Bridge's own behaviour. It does not cover your Prinect installation, your Heidelberg licence, or your MQTT broker.

9. Removing the Plugin

Disabling or uninstalling this Plugin stops all polling and publishing from this computer immediately. Retained MQTT messages already delivered to your broker remain there until your broker clears them — the availability topic is published as offline on a clean shutdown, but retained state topics are yours to purge. Remove the stored password by clearing the credentials in the Plugin's settings before removal, or by deleting the CCCapture-prinect_bridge entries from your operating system's credential store afterwards. Nothing is deleted from your Prinect installation; ChromaChecker holds no copy of your Prinect data.

10. Changes to these Plugin Terms

These Plugin Terms are versioned. A new version replaces this text at the same address, and CC Capture asks your Organisation's administrator to accept it before the Plugin continues to be used. A change here does not alter the EULA or the terms of any other Plugin.

The version you accepted is recorded by the application, and every earlier version is kept below, so the text your Organisation agreed to can always be produced.

Revision history

ChromaChecker Corporation · 4324 Sanddollar Court, New Port Richey, FL 34652, USA · legal@chromachecker.com

Published at https://chromachecker.com/legal-plugin-prinect-bridge