Privacy Policy

Data Controller

DIGIFLO, Owner Florian Klaner
Katzenbach 34A, 4924 Waldzell, Austria
Email: [email protected]

Purpose of Processing

NocMate processes data to provide monitoring functionality, in particular for push delivery, monitoring alerts and the display of linked devices.

Data Processed

Depending on usage: instance URLs, technical push tokens, user keys, alert metadata such as host, service, status and timestamps as well as technical server logs.

Recipients

Push notifications are delivered via Apple Push Notification Service (APNs). During operations, technical service providers for hosting, reverse proxy, monitoring and logging may be involved.

Your Rights

You have the right to access, rectification, erasure, restriction, data portability and objection under the GDPR.

NocMate Connect (optional tunnel)

NocMate Connect is an optional feature that forwards app requests through the relay (api.nocmate.app) to a tunnel agent installed locally at the customer site, which executes the requests against the local Checkmk instance. You actively enable Connect by installing the agent on your server and pairing it with the app. Without that activation, no data is forwarded through the relay.

Data processed during Connect operation

While a request is being passed through, the relay technically sees the HTTP method, path and body of the request as well as the agent's response — this data is processed in memory only, is not persisted, is not written to logs, and is discarded immediately after delivery. Only the following routing metadata is persisted in the relay database:

• User key (random identifier, also used for push notifications)
• Instance ID (random UUID per connected site)
• Free-form display name of the site
• SHA-256 hash of the agent token (the token itself is never stored)
• Timestamp of the last connection (last seen)

For multi-user setups (multiple people pairing with the same Connect agent): one user key and one routing record per person. Every request is executed against Checkmk under each person's individual Checkmk user — visibility follows native Checkmk roles and contact groups, not an internal NocMate logic.

Encryption

All connections between app and relay as well as between agent and relay are transport-encrypted (TLS, HTTPS). Since the relay sees requests during forwarding, this is technically not classic end-to-end encryption. We do not, however, share data with third parties, run no content logging, and do not store bodies. Optional end-to-end encryption with ECDH key exchange between app and agent is planned as an extension.

Location and retention

The relay server is located in Germany (EU). No third-country transfer of Connect data takes place. Routing metadata is deleted as soon as the corresponding site is removed in the app. Requests and responses are not persisted.

Legal basis and data processing

The legal basis is Art. 6(1)(b) and (f) GDPR (contract performance and legitimate interests in operating the app feature). If you use Connect to process personal data of your customers, employees or patients, please conclude a Data Processing Agreement (DPA) with DIGIFLO in advance. We provide a DPA template on request: [email protected].

Revocation and deletion

You can disable Connect at any time by deleting the site in the app (Settings → Sites → Delete) and stopping the agent on your server. The associated routing metadata is then removed from the relay database.