When an application sends telemetry data to a monitoring provider, the IP address of the user is typically included in the provider’s server access logs. Under EU law (GDPR), an IP address is considered personal data.

This service acts as a proxy for telemetry requests and removes the user’s IP address before forwarding the data to a third-party monitoring provider.

The proxy ensures that

• The monitoring provider never receives the user’s IP address
• Only non-personal telemetry data is forwarded

The proxy itself does not store IP addresses (logging must be disabled or configured accordingly).

Telemetry data is sent to this proxy, which forwards the payload to the monitoring provider — in this case LogSnag.

LogSnag unfortunately does not provide an option to disable server access logs, which means that sending telemetry directly would expose user IP addresses. This proxy solves that issue by acting as an intermediary.

The flow looks like this:

flowchart LR
    App --> Proxy
    Proxy --> S[Telemetry Service]