This page is also available in French. Switch to French

This page is also available in Spanish. Switch to Spanish

How Kinethra protects chargers, payments and data

TLS for the app, the admin and the API, encryption at rest, separate environments, limited production access, card payments through Stripe, and privacy practices built for GDPR, PIPEDA, Quebec's Law 25 and US state privacy laws.

Illustrative interface. Sample data.

Access and activity logs

  • Roles

    Owner, Administrator, Manager, Technician and Read Only.

    Operations
  • Activity log

    User actions, including Ethra's, are recorded in an activity log.

  • Charger timeline

    Every charger event is logged: going online or offline, sessions, status changes, errors and firmware.

  • Ethra follows your rolesEarly Access

    Ethra respects the user's role. For example, it takes no actions for Read Only users.

  • Ethra keeps a recordEarly Access

    Ethra logs every action and who asked for it.

  • Ethra asks firstEarly Access

    Ethra asks for confirmation before actions that interrupt a charger or affect charging and money.

Open standards

  • OCPP 1.6 and 2.0.1

    Kinethra supports both versions.

    OCPP in detail
  • OpenADR

    Kinethra integrates with utility systems through open standards, including OpenADR.

  • ISO 15118

    Kinethra supports Plug & Charge (ISO 15118) with compatible chargers and vehicles.

  • Your systems

    Integrations are tailored to your systems. Talk to us.

    Integrations

Security

Three separate raised floors with server cabinets: development and staging behind, their cabinets unlit; production in front inside a glass enclosure, the only one with a live data line, a lock on the door of the cabinet it feeds. The card reads: Production, live, stored data encrypted at rest.
Development Staging Production ProductionLiveEncryptedat restStored data
  • TLS/HTTPS

    The app, the admin and the API use TLS/HTTPS.

  • Encryption at rest

    Stored data is encrypted at rest.

  • Separate environments

    Development, staging and production run in separate environments.

  • Limited production access

    Production access is limited to selected engineers and protected with two-factor authentication.

  • A key for every charger

    Every charger has its own unique OCPP authentication key.

  • Secure charger channel

    Chargers talk to the platform over a secure WebSocket channel (WSS).

  • The platform, 24/7

    Platform health and errors are monitored automatically, 24/7.

  • Chargers in real time

    Chargers are monitored in real time: status, errors, online or offline.

Privacy and data

  • Privacy practices

    Privacy practices are built for GDPR, Canada's PIPEDA, Quebec's Law 25 and US state privacy laws.

  • Servers in North America and Europe

    The Kinethra platform runs on servers in North America and Europe. Canadian customers' data stays in Canada.

  • Website on Cloudflare

    The website and its forms run on Cloudflare.

  • Your data is yours

    Customers' data belongs to the customers.

  • Personal-data requests

    Send them to privacy@kinethra.com.

Payments

A pedestal charges a car, the driver's payment card at its screen. From the floor under the card the money runs as its own line straight to the door of the organization's building; the platform's servers stand apart, the other way, tied to the charger by a data line only.
48 ACharging Driver paymentsGoes toYour payment accountCard detailsNot stored
  • Card payments through Stripe

    Card payments are processed by Stripe under its PCI DSS certification. Kinethra does not store card details.

  • Money goes to the owner

    Each organization links its own Stripe account. Drivers pay the organization directly; Kinethra never holds the money and never stores bank details.

Ask a security question

  • 40,000+ chargers onlineOn the Kinethra platform.
  • OCPP 1.6 and 2.0.1Kinethra works with OCPP chargers from any manufacturer.
  • No commission on charging revenueKinethra takes none.

We use your details to answer your request. See our Privacy Policy for details.