Last Updated: June 9, 2026
At QueueWatch, we take telemetry security, isolation, and privacy seriously. This policy documents how we collect, process, and safeguard the diagnostic telemetry streamed from your application queues.
QueueWatch monitors operational events in your asynchronous workflows. The data collected by our client-side SDK is strictly limited to metadata required for operational diagnostic analysis, including:
Note: We do NOT collect credit card numbers, passwords, PII, or raw business data payloads. We recommend using payload filters or hash configurations to mask sensitive fields inside job logs.
All telemetry streamed to our event ingestion brokers is encrypted in transit using TLS 1.3 and encrypted at rest using AES-256. Database segments and job logs are isolated using logical workspace partitioning to prevent cross-tenant access.
By default, detailed job execution logs and stack traces are retained for 14 days on our standard tiers to facilitate incident triage, after which they are permanently pruned. Aggregate metrics are stored for up to 90 days. We do not sell, rent, or share your telemetry metadata with third-party advertisers.
If you have any questions regarding telemetry data isolation, security auditing, or compliance certificates, please contact our SRE operations team at security@queuewatch.io.