Skip to main content

Telemetry Behaviour and Options

PDFxStream makes very limited use of remote telemetry, strictly to ensure licensing compliance and to help us improve the product and provide the best possible technical support.

Specifically, PDFxStream will occasionally communicate with Snowtide servers to:

  1. Check the validity of the registered license file and its associated subscription. These checks are performed as rarely as possible, asynchronously, and at the lowest possible thread priority so as to not impose any interfering load on the host runtime.
  2. Send usage statistics, error messages, exception/error stack traces, and limited contextual information to Snowtide servers in order to facilitate debugging efforts and technical support services.

Handling of sensitive data

We recognize that PDFxStream is often used to facilitate access extremely sensitive data. With that in mind, its telemetry takes great care to never allow that sensitive data to leave your application and runtime:

  • No documents or portions of documents are ever included in telemetry
  • No extracted data is ever included in telemetry
  • Any error messages and stack traces are sanitized to include only data pertaining to PDFxStream itself (e.g. sent stack traces only include stack frames "below" the outermost public PDFxStream API entry point that your application called)

If you remain concerned about the operation of PDFxStream's telemetry, please note below the options available to configure and disable it.

Configuration and options

PDFxStream's telemetry can be controlled and disabled via the pdfxs.telemetry configuration option.