About Just In Charge

Smart charging should be easy to understand.

Just In Charge gives drivers control over when their car charges, what each session costs and which services handle their data.

Contact Beau

Beau Everaert

I am the Lead and Founder behind Just In Charge and a developer of charging equipment. The project originates in Lucerne, Switzerland, and grows from hands-on experience with the technology behind electric charging.

Lucerne, Switzerland

Have a question, an idea or simply want to talk about charging? I would be glad to hear from you.

Our providers

External Services

Keeping user data private is a core priority for bzero.ch. We share only what each function needs. The flag shows where the provider is based; the description explains what the integration receives.

  • Hetzner

    πŸ‡©πŸ‡ͺ

    Hosts the production application, application databases and charging services in Germany. Hetzner processes the account, charger, session, support and operational data needed to run Just In Charge.

    Hetzner privacy information
  • Hanko

    πŸ‡©πŸ‡ͺ

    Provides account sign-in and security through Hanko Cloud. Identity and security data is stored in Germany and processed within the EEA. Charging and session data is not sent to Hanko.

    Hanko privacy information
  • Geoapify

    πŸ‡¨πŸ‡Ύ

    Receives an address or coordinates when a charger location is searched, saved or reverse-geocoded. Requests use Geoapify's API and include technical request metadata, but do not include account or charger IDs.

    Geoapify privacy information
  • Open-Meteo

    πŸ‡¨πŸ‡­

    Receives coordinates and date ranges for solar forecasts and historical irradiance. No account or charger ID is sent. Open-Meteo says API logs may contain coordinates and are deleted after 90 days.

    Open-Meteo privacy information
  • BKW public tariff service

    πŸ‡¨πŸ‡­

    Provides BKW's public dynamic-tariff feed. The current feed contains feed-in remuneration rather than charging prices, so Just In Charge does not use it as a consumption price. No user, charger or session data is sent.

    BKW public tariff service privacy information
  • CKW public tariff service

    πŸ‡¨πŸ‡­

    Provides CKW's public dynamic grid-price data. Requests contain the tariff and time range, not user, charger or session data.

    CKW public tariff service privacy information
  • EKZ tariff API

    πŸ‡¨πŸ‡­

    Provides EKZ's public dynamic electricity and grid-price data. Requests contain the tariff and time range, not user, charger or session data.

    EKZ tariff API privacy information
  • Groupe E tariff API

    πŸ‡¨πŸ‡­

    Provides Groupe E's public dynamic electricity tariff data. Requests contain the tariff and time range, not user, charger or session data.

    Groupe E tariff API privacy information
  • Primeo Energie tariff API

    πŸ‡¨πŸ‡­

    Provides public dynamic tariff data for Primeo Energie, AVAG and ELAG. Requests contain the tariff and time range, not user, charger or session data.

    Primeo Energie tariff API privacy information
  • City of Zurich Open Data

    πŸ‡¨πŸ‡­

    Provides the public hourly grid, energy and combined prices for EWZ's NNE-H home-charging pilot. Just In Charge downloads the published dataset without sending user, charger or session data.

    City of Zurich Open Data privacy information
  • Apple Push Notification service

    πŸ‡ΊπŸ‡Έ

    Delivers opt-in Web Push notifications to Safari. Apple receives a device-specific endpoint and an end-to-end encrypted notification payload.

    Apple Push Notification service privacy information
  • Google Web Push

    πŸ‡ΊπŸ‡Έ

    Delivers opt-in Web Push notifications to Chromium-based browsers. Google receives a device-specific endpoint and an end-to-end encrypted notification payload.

    Google Web Push privacy information
  • Mozilla Web Push

    πŸ‡ΊπŸ‡Έ

    Delivers opt-in Web Push notifications to Firefox. Mozilla receives a randomized delivery identifier and an end-to-end encrypted payload, and says it retains delivery IP addresses for 90 days.

    Mozilla Web Push privacy information
  • Let's Encrypt

    πŸ‡ΊπŸ‡Έ

    Issues the TLS certificates used by the production service. Certificate requests include service domain names and technical validation data. Issued domain names are published in public Certificate Transparency logs; user, charger and session data is not sent.

    Let's Encrypt privacy information