OCPP DebugKit

Anonymize

The ocpp-debugkit anonymize command strips sensitive fields from a trace file, making it safe to share for debugging or support purposes.

Usage

# Output to stdout
ocpp-debugkit anonymize trace.json

# Write to file
ocpp-debugkit anonymize trace.json -o trace-anon.json

What Gets Anonymized

  • idTag — replaced with "anonymized"
  • chargePointSerialNumber / chargeBoxSerialNumber — replaced with "station-anon"
  • stationId — replaced with "station-anon"
  • transactionId — replaced with sequential integers (1, 2, 3...)
  • identifier — replaced with "anonymized"
  • Email addresses — replaced with [redacted-email]
  • Phone numbers — replaced with [redacted-phone]
  • IP addresses — replaced with [redacted-ip]

Privacy Considerations

Anonymization is performed locally — no data is uploaded. The anonymized trace is safe to share in issue reports, support tickets, or public forums.

Note: Anonymization is a best-effort process. Always review the output before sharing to ensure no sensitive data remains.

What Is NOT Anonymized

  • Timestamps — preserved for debugging timeline issues
  • OCPP action names — preserved for structural understanding
  • Meter values — preserved for analysis (they don't identify users)
  • Error codes and descriptions — preserved for debugging