Privacy Policy

This Privacy Policy applies to the PixelWatch Alert gateway, the PixelWatch Alert Android and Wear OS applications, and the related browser-based tenant administration surfaces. Replace the bracketed operator fields before using this policy publicly in production.

What The Service Does

PixelWatch Alert receives alert events from Zabbix and compatible external systems, stores operational alert state, routes alerts to registered Android devices, records delivery and action telemetry, and optionally writes acknowledgements back to Zabbix. The service also provides passkey-based identity, tenant membership, and invite-based onboarding for responders and tenant administrators.

Data We Process

• Account and identity data: email address, display name, recovery email if supplied, tenant memberships, and passkey credential metadata.
• Operational alert data: event IDs, trigger IDs, host names, severity, timestamps, source URLs, and acknowledgement status.
• Device registration and delivery data: device IDs, FCM tokens, platform information, app version, device model/manufacturer, last-seen IP address, and delivery receipts.
• Integration data: tenant-scoped Zabbix webhook settings and Zabbix API endpoint details entered by tenant administrators.
• Audit and support data: activity logs, invite metadata, health checks, and support diagnostics records.

Why We Process This Data

• To authenticate users with passkeys and maintain tenant membership.
• To route alerts to the correct responders and devices.
• To provide acknowledgement, escalation, audit, and diagnostics features.
• To allow tenant administrators to configure Zabbix integration and invite users.
• To maintain service security, prevent abuse, and investigate operational incidents.

Data Sharing

The service may send or receive data from the following categories of processors or counterparties:

• Zabbix or other alerting systems configured by the platform operator or tenant.
• Firebase Cloud Messaging for mobile push delivery.
• Hosting, reverse proxy, monitoring, and infrastructure operators acting on behalf of the service operator.

We do not sell personal data. We only disclose data where needed to operate the service, comply with law, investigate misuse, or protect the service and its users.

Retention

• Active account, membership, passkey, tenant, and integration records are retained while the account and tenant remain active.
• Operational alert and delivery state may be retained for diagnostics, audit, incident review, and support purposes.
• Some data may be retained for legitimate reasons such as security, fraud prevention, legal compliance, backup integrity, or dispute investigation.

Security

• Passkey authentication is used for browser and tenant admin sign-in.
• JWT session tokens are used for authenticated API access.
• Tenant and identity state is stored in Redis in the current implementation.
• Transport security should be enforced with HTTPS/TLS on public endpoints.

Your Choices And Rights

Users can request access, correction, and deletion of their account and associated data, subject to legitimate retention requirements. Tenant administrators may also need to coordinate with the platform operator because some operational and audit records are maintained at the service level.

Account Deletion

To request account deletion and associated data deletion, use the public instructions at https://za.adepteo.net/account-deletion. If some data must be retained for legitimate reasons such as security, fraud prevention, or legal compliance, that retained data will be limited to the required scope and duration.

Children

PixelWatch Alert is intended for operational and business use by technical responders and administrators. It is not directed to children.

Changes

We may update this Privacy Policy to reflect changes in the service, legal obligations, or operational practices. The latest version will be published at this URL with an updated effective date.