Privacy Policy
Charge Ledger Privacy Policy
This policy describes the web version of Charge Ledger. The native app stores its data locally on your device.
Effective date: 2026-06-19
Purpose of the App
Charge Ledger helps Zaptec users get deeper insight than the provider interface offers by synchronizing chargers and charge sessions, inspecting charging history, filtering sessions, calculating costs, and restoring personal view settings between visits.
Data You Provide
When you log in, you provide your Zaptec email address and password to request an access token from Zaptec. Charge Ledger does not store your Zaptec password.
Data Stored Server-Side
In web mode, Charge Ledger stores the following data in secure server-side storage:
- Customer identifier and email address associated with the active server session.
- Server session expiry metadata.
- Zaptec charger metadata such as charger id, name, serial number, and installation id.
- Synchronized charge sessions, including session id, charger id, charger name, user name when supplied by Zaptec, start time, end time, energy, duration, and cost data when available.
- Saved filters, including selected period, time field, date range, and charger selection.
- Settings such as kWh price, currency code, and charge session table column order and visibility.
Data Not Stored Server-Side
- Zaptec passwords are not stored in the server database.
- Zaptec access tokens are not stored in the server database.
- Payment card data is not collected or stored.
Browser Storage
The web app stores the Zaptec access token in browser sessionStorage. This keeps the token available only for the active browser session. The server session id is stored in an HTTP-only cookie.
How the Data Is Used
Stored data is used to show charge history, totals, filters, settings, and the customized charge session table. The Zaptec access token is sent to the server only when a synchronization action needs the server to call the Zaptec API.
Data Sharing
Charge Ledger calls the Zaptec API when you log in or synchronize data. The app does not sell personal data and does not provide advertising profiles.
Deleting Server-Side Data
In the web app, open the settings menu and use the server-side data deletion option. This removes stored chargers, charge history, user-specific filters, settings, table column setup, and server session data for the active user.
Security
The web server requires a valid server session for the app and protected API routes. Session cookies use HttpOnly and SameSite=Strict, and are marked Secure when served through HTTPS.
Contact
For privacy questions, contact the operator of the Charge Ledger deployment you use.
Source Code
The Charge Ledger source code is available on GitHub at ronaldderksen/chargeledger.