Privacy

Your CSMS connection, credentials and OCPP messages stay in your browser and are sent directly to the CSMS endpoint you provide. This page explains what that means in practice.

What is not collected

Chargeflux.io does not send any of the following to its analytics or telemetry:

  • Your CSMS URL
  • Query-string tokens or credentials
  • Usernames or passwords
  • The station identity you enter
  • idTags
  • OCPP message payloads and message IDs
  • Vendor-specific data
  • Exported configuration and session logs

The browser opens the WebSocket connection directly to your CSMS. Chargeflux.io does not proxy, store or have access to that traffic.

What is collected

Chargeflux.io uses Vercel Web Analytics for privacy-conscious, page-level measurement such as page views and referring sources. This is used to understand which pages are useful and is not tied to your OCPP activity or the contents of your simulator session.

Local storage on your device

To make the simulator useful, some data is stored locally in your browser, never on a Chargeflux.io server:

  • localStorage holds small user preferences.
  • IndexedDB holds named charger configurations and larger local session logs.
  • Live credentials are kept in memory unless you explicitly choose to remember them on this device.

Secrets are not persisted by default, exports omit secrets by default, and log views redact configured secret values.

Clearing your local data

You can permanently remove all locally stored Chargeflux.io data at any time using the “Clear local data” control in the simulator settings. You can also clear site data for chargeflux.io through your browser settings, which removes both localStorage and IndexedDB entries.