{"id":21,"date":"2026-11-05T21:57:40","date_gmt":"2026-11-05T21:57:40","guid":{"rendered":"https:\/\/charge-it.io\/?page_id=21"},"modified":"2026-11-05T21:57:40","modified_gmt":"2026-11-05T21:57:40","slug":"security","status":"publish","type":"page","link":"https:\/\/charge-it.io\/?page_id=21","title":{"rendered":"Security"},"content":{"rendered":"\n<section class=\"phero dark glow\" aria-labelledby=\"t\">\n  <div class=\"wrap\">\n    <ul class=\"crumbs\"><li><a href=\"https:\/\/charge-it.io\/\">Home<\/a><\/li><li><a href=\"https:\/\/charge-it.io\/?page_id=22\">Company<\/a><\/li><li>Security<\/li><\/ul>\n    <p class=\"eyebrow\"><span class=\"dot pulse\"><\/span>Security<\/p>\n    <h1 class=\"h1\" id=\"t\" style=\"max-width: 20ch\">Secured from the charger&#8217;s socket <em>to the user&#8217;s screen.<\/em><\/h1>\n    <p class=\"lead\">Security in charging starts at the protocol, long before anyone logs in. ChargeIT secures each charger connection, each user&#8217;s access and each customer&#8217;s data separately.<\/p>\n  <\/div>\n<\/section>\n\n\n\n<section class=\"sec dark\" aria-labelledby=\"p-t\" style=\"border-top: 1px solid var(--d-line)\">\n  <div class=\"wrap\">\n    <div class=\"sec-head\"><div><p class=\"eyebrow\"><span class=\"dot\"><\/span>Charger connections<\/p><h2 class=\"h2\" id=\"p-t\">OCPP security profiles, set per charger.<\/h2><\/div><p class=\"lead\">Each charger runs at the profile it supports, and can be held to that profile or exempted one by one, with every change logged.<\/p><\/div>\n    <div class=\"profiles\">\n      <div class=\"prof warn\"><span class=\"lvl\">0<\/span><h3 class=\"h4\">Unsecured<\/h3><div class=\"bar\"><i style=\"width: 8%\"><\/i><\/div><p>Only for legacy chargers, and flagged with a warning.<\/p><\/div>\n      <div class=\"prof\"><span class=\"lvl\">1<\/span><h3 class=\"h4\">Basic authentication<\/h3><div class=\"bar\"><i style=\"width: 40%\"><\/i><\/div><p>A password per charger, stored hashed.<\/p><\/div>\n      <div class=\"prof good\"><span class=\"lvl\">2<\/span><h3 class=\"h4\">TLS + password<\/h3><div class=\"bar\"><i style=\"width: 72%\"><\/i><\/div><p>The connection encrypted, the charger authenticated.<\/p><\/div>\n      <div class=\"prof good\"><span class=\"lvl\">3<\/span><h3 class=\"h4\">Mutual TLS<\/h3><div class=\"bar\"><i style=\"width: 100%\"><\/i><\/div><p>Charger and platform both prove who they are with certificates.<\/p><\/div>\n    <\/div>\n  <\/div>\n<\/section>\n\n\n\n<section class=\"sec light\" aria-labelledby=\"a-t\">\n  <div class=\"wrap\">\n    <div class=\"sec-head\"><div><p class=\"eyebrow\"><span class=\"dot\"><\/span>Access<\/p><h2 class=\"h2\" id=\"a-t\">People see what they need, and nothing more.<\/h2><\/div><\/div>\n    <div class=\"grid-3\">\n      <article class=\"card\"><span class=\"k\">Scope<\/span><h3 class=\"h3\">Every customer in its own branch<\/h3><p>Each organisation sees its own branch of the customer tree and what&#8217;s below it. Widening one customer&#8217;s view never widens anyone else&#8217;s.<\/p><\/article>\n      <article class=\"card\"><span class=\"k\">Permissions<\/span><h3 class=\"h3\">Page by page, action by action<\/h3><p>Roles come from permission templates, and an admin can never grant more than they hold themselves.<\/p><\/article>\n      <article class=\"card\"><span class=\"k\">Accountability<\/span><h3 class=\"h3\">Help is recorded as help<\/h3><p>When your team works in a customer&#8217;s console through &#8220;view as customer&#8221;, the change is recorded as made on their behalf.<\/p><\/article>\n      <article class=\"card\"><span class=\"k\">Organisations<\/span><h3 class=\"h3\">Always an admin<\/h3><p>Every organisation keeps at least one admin, so access never depends on a single account that might disappear.<\/p><\/article>\n      <article class=\"card\"><span class=\"k\">Suspension<\/span><h3 class=\"h3\">One switch, everywhere<\/h3><p>Suspending a customer stops its users, its charging authorisations and its stations at once.<\/p><\/article>\n      <article class=\"card\"><span class=\"k\">Fail closed<\/span><h3 class=\"h3\">No answer means no<\/h3><p>When an authorisation can&#8217;t be decided, the charger is refused rather than left open.<\/p><\/article>\n    <\/div>\n  <\/div>\n<\/section>\n\n\n\n<section class=\"sec band light\" aria-labelledby=\"d-t\">\n  <div class=\"wrap\">\n    <div class=\"frow\">\n      <div>\n        <p class=\"eyebrow\"><span class=\"dot\"><\/span>Data<\/p>\n        <h2 class=\"h2\" id=\"d-t\">Your data stays yours.<\/h2>\n        <ul class=\"ticks\">\n          <li><span class=\"tick\" aria-hidden=\"true\"><svg width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2.5\"><path d=\"M20 6 9 17l-5-5\"><\/path><\/svg><\/span><div><strong>Exportable<\/strong><span>Customers can export their own data, including if they move to another provider.<\/span><\/div><\/li>\n          <li><span class=\"tick\" aria-hidden=\"true\"><svg width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2.5\"><path d=\"M20 6 9 17l-5-5\"><\/path><\/svg><\/span><div><strong>Drivers&#8217; data kept on our side<\/strong><span>When partners build their own app on our API, drivers&#8217; personal and payment data stay with ChargeIT, under GDPR controls.<\/span><\/div><\/li>\n          <li><span class=\"tick\" aria-hidden=\"true\"><svg width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2.5\"><path d=\"M20 6 9 17l-5-5\"><\/path><\/svg><\/span><div><strong>Payments through the provider<\/strong><span>Card payments run through the payment provider connected for that customer.<\/span><\/div><\/li>\n        <\/ul>\n      <\/div>\n      <div class=\"term\" aria-label=\"Example audit entries\">\n        <div class=\"term-head\"><span><span class=\"dot pulse\" style=\"margin-inline-end: 8px\"><\/span>audit \u00b7 example entries<\/span><span>per charger<\/span><\/div>\n        <ul style=\"list-style: none; margin: 0; padding: 12px 16px; display: grid; gap: 8px\">\n          <li style=\"display: flex; justify-content: space-between; gap: 12px\"><span>PROFILE-ENFORCE-OVERRIDE<\/span><span class=\"muted\">CP-014 \u00b7 held to profile 2<\/span><\/li>\n          <li style=\"display: flex; justify-content: space-between; gap: 12px\"><span>PROFILE-EXEMPT-OVERRIDE<\/span><span class=\"muted\">CP-003 \u00b7 legacy exemption<\/span><\/li>\n          <li style=\"display: flex; justify-content: space-between; gap: 12px\"><span>Authorization key rotated<\/span><span class=\"muted\">CP-022 \u00b7 two-phase<\/span><\/li>\n          <li style=\"display: flex; justify-content: space-between; gap: 12px\"><span>Change made via view as customer<\/span><span class=\"muted\">recorded as on their behalf<\/span><\/li>\n        <\/ul>\n      <\/div>\n    <\/div>\n  <\/div>\n<\/section>\n\n\n\n<section class=\"sec light\" aria-labelledby=\"l-t\">\n  <div class=\"wrap\">\n    <div class=\"sec-head\"><div><p class=\"eyebrow\"><span class=\"dot\"><\/span>Legal<\/p><h2 class=\"h2\" id=\"l-t\">Policies<\/h2><\/div><\/div>\n    <div class=\"legal-grid\">\n      <a class=\"card\" href=\"https:\/\/charge-it.io\/?page_id=21\"><h3 class=\"h3\">Privacy policy<\/h3><p>How we handle personal data.<\/p><\/a>\n      <a class=\"card\" href=\"https:\/\/charge-it.io\/?page_id=21\"><h3 class=\"h3\">Terms of use<\/h3><p>The terms for using this website.<\/p><\/a>\n      <a class=\"card\" href=\"https:\/\/charge-it.io\/?page_id=21\"><h3 class=\"h3\">Cookies<\/h3><p>What we store in your browser, and why.<\/p><\/a>\n      <a class=\"card\" href=\"https:\/\/charge-it.io\/?page_id=21\"><h3 class=\"h3\">Accessibility<\/h3><p>How this site works for everyone.<\/p><\/a>\n    <\/div>\n  <\/div>\n<\/section>\n\n","protected":false},"excerpt":{"rendered":"<p>Home Company Security Security Secured from the charger&#8217;s socket to the user&#8217;s screen. Security in charging starts at the protocol, long before anyone logs in. ChargeIT secures each charger connection, each user&#8217;s access and each customer&#8217;s data separately. Charger connections OCPP security profiles, set per charger. Each charger runs at the profile it supports, and [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":10,"comment_status":"closed","ping_status":"closed","template":"","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_chargeit_seo_title":"","_chargeit_seo_desc":"","_chargeit_seo_image":0,"_chargeit_noindex":false,"footnotes":""},"class_list":["post-21","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/charge-it.io\/index.php?rest_route=\/wp\/v2\/pages\/21","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/charge-it.io\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/charge-it.io\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/charge-it.io\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/charge-it.io\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=21"}],"version-history":[{"count":0,"href":"https:\/\/charge-it.io\/index.php?rest_route=\/wp\/v2\/pages\/21\/revisions"}],"wp:attachment":[{"href":"https:\/\/charge-it.io\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=21"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}