Privacy Policy

This notice explains what personal data we collect when you use GreenCharge, why we collect it, who else sees it, how long we keep it and what you can ask us to do about it. It covers the website, the web app and the GreenCharge apps for iOS and Android, which are all the same service.

1. Who we are

The data controller is M.K. CYCHARGING LTD, Archiepiskopou Makariou III 172, 3027 Limassol, Cyprus. You can reach us at info@greencharge.com.cy for anything in this notice, including to exercise the rights in section 7.

GreenCharge is also the platform that other charging companies use to run their own stations. Those companies are separate businesses. An account works only at the stations of the operator it was created with: if you try to start a charge, or tap your card, at another company's station, the system refuses it. As a guest, without an account, you can charge at any station on the platform. Section 5 says what the operator of a station can see. If we ever arrange for an account to work at other companies' stations, we will set out here who answers which request before that goes live.

This notice is for people who charge with GreenCharge. If you sign in to the operator portal on behalf of a charging company, a site or a fleet, the data we hold about that account — your name, your work email address and your two-factor authentication details — is not covered here. Write to the address above and we will tell you what we hold.

We have not appointed a Data Protection Officer. We are not required to, and any question you would put to one should go to the address above.

2. What we collect

When you create an account. Your first name and email address, which are required, and your surname, phone number and address if you choose to give them. We create a customer number for you, and record that you accepted the terms, when, and which version.

When you charge. Which station and connector you used, when the session started and stopped, how much energy was delivered and what it cost. If you tap an RFID card, the identifier of that card.

When you pay in the app or on the web. We do not receive or store your card number or security code. Cards are entered on a payment page hosted by Worldline (Saferpay), who return a token we store in place of the number, together with the card brand, the last four digits and the expiry date. Your wallet balance and the credits and charges against it are kept on our side.

When you tap a card on a station's card reader. Some stations have a contactless reader. We do not receive or store your card number or security code here either — the card is read by the reader itself, which is made by Payter and talks to Payter directly. What reaches us is the last four digits, the amount reserved, the amount finally taken, and a reference Payter gives us for that payment. We also receive a code that stands in for your card. It is not your card number and it cannot be turned back into one, but it is the same code every time the same card is used, so it does make two taps of the same card recognisable as the same card. We keep it for 180 days, because that is how a payment you later dispute with your bank is matched to the charge it paid for, and then it is erased.

If you charge as a guest, without an account. We create a random reference for that session and nothing else that identifies you. If you paid through the app or by scanning the QR code on the station, two separate guest sessions cannot be linked to the same person by anything we hold. If you tapped a card on a station's reader, they can — for 180 days, by the stand-in code described above, and only as the same card rather than as a named person. If you ask for a receipt by email, we keep that email address against the session for 90 days and then erase it.

If you ask us for a charging card. Your name, email address and phone number, the postal address you want the card sent to, and anything you write in the optional note. We telephone you on that number to confirm the details before the card is posted. The charging company that issues the card handles this request and keeps a record that a card was issued.

If you report a problem with a station. Which station and connector, and which of the listed problems you picked from the menu — the app does not ask you to write anything, and sends only your choice. Your account is attached so the operator can come back to you.

If you turn on notifications. A token that lets us send a message to that device. In the apps we also record the type of phone (iPhone or Android) and the app's version. The token identifies the app on that device, not you, but we keep it with your account so that messages about your charging reach you. On the iPhone app the token comes from Apple's Push Notification service. On the Android app it comes from Google's Firebase Cloud Messaging. In a web browser it comes from the browser maker. To deliver a message, Apple or Google receives the token and the message itself — for example the station's name, the energy delivered and the cost. In a web browser the message is encrypted, so only your browser can read it.

In the Android app, even before you turn notifications on. The Android app contains Google's Firebase Cloud Messaging code, which is how notifications reach an Android phone. When the app starts, this code can register the app with Google. It creates an identifier for that installation of the app and sends it to Google, with the app's version and technical details of the phone, such as its make, model and Android version. This identifies the installed app, not you. We receive none of it: if you turn notifications on, we receive only the token described above. The iPhone app does not contain Firebase, and it registers for notifications only when you turn them on.

If you scan a QR code in the app. The iPhone and Android apps read the code with Google's ML Kit. On an iPhone it is built into the app. On Android it is provided by Google Play services on your phone. The camera picture is processed on your phone. It is not sent to us or to Google. The app receives only the text in the code, which on a charger is its web address. When you use the scanner, ML Kit sends Google technical information: the phone's model and system version, the app's name and version, an identifier for that installation of the app (not for you or the phone), and how quickly and how well the scan worked. Google uses this to check and measure its own software. In a web browser, the page reads the code itself and nothing is sent to Google.

Automatically, on our servers. Our web server records the IP address, page and browser of each request, in the ordinary way. Our charging system keeps the raw messages exchanged with the stations, and with the card readers, for 90 days. On the small number of messages that authorise a charge, that includes the identifier of the RFID card presented. A message from a card reader can include the last four digits and the stand-in code of a card that was tapped.

What we do not collect. We do not track your location. When you ask for the stations near you, the app asks your phone or browser where you are, so it can sort the stations by distance and centre the map. That position stays on your device and is never sent to us. We do not use advertising identifiers, and we do not build profiles or sell data to anyone. We run no analytics or tracking of our own. The only analytics in the apps is the technical information that Google's code sends to Google, described above.

3. Why we use it, and our legal basis

  • To give you the service you asked for — your account, starting and stopping a charge, taking payment, your history and your receipts. Performance of a contract, Article 6(1)(b).
  • To meet our obligations under Cyprus tax and VAT law — invoices and the session records that evidence them. Legal obligation, Article 6(1)(c).
  • To keep the service working and safe — diagnosing faults at a station, investigating a disputed charge, detecting abuse of our systems. This also covers using Google's code in the apps to read QR codes and to deliver notifications on Android, which sends Google the technical information described in section 2. Legitimate interests, Article 6(1)(f). We think this is fair because it is limited to what we need to run a reliable charging service, and you can object at any time.
  • To send you notifications about a charge finishing or a problem with a session. Consent, Article 6(1)(a) — you turn them on, and can turn them off.

4. What we store on your device

We use your browser's local storage to keep you signed in and to remember small preferences such as your language. The apps do the same. These are not advertising cookies, we set no tracking cookies, and there are no third-party trackers in the app. In the Android app, Google's Firebase code also keeps its installation identifier on the phone.

The map is served by Google Maps. Loading it means Google receives your IP address and, because the map is centred where you are, an approximate idea of where that is. That is Google's processing under their own privacy policy, and it happens whether or not you have an account.

Two other things come from outside services: the font used by the app and by these pages, from Google Fonts, and the open-source code that reads QR codes in a web browser, from jsDelivr. Like any website that sends you a file, each of them receives your IP address when the page loads.

5. Who we share it with

We do not sell personal data and we do not share it for advertising. The following receive it because the service cannot work otherwise.

  • Worldline (Saferpay) — our payment provider. They handle your card and hold the card data we deliberately do not. We send them the amount, a reference for the session and the stored token.
  • Payter — the Dutch company whose card readers are fitted to some stations. When you tap, their reader and their systems handle the card; they, and the bank they settle through, hold the card data we deliberately do not. We send them the amount to reserve and a reference for the session.
  • The operator of the station you used. Each charging company on the platform sees the sessions at its own stations: when, which charger, the energy and the amount. An account works only at the stations of the operator it was created with, and that operator can also see the account: your name, email address and the other details you gave us, and your sessions and invoices, so that it can help you. If you charge as a guest, the operator of that station sees the session and, only if you asked for one by email, the address you gave for the receipt. It receives nothing else about you. If you tap your card at another company's station the charge is refused, and that company sees the card's identifier in its own fault log, so it can tell a rejected card from a broken charger.
  • Fleet operators, where you charge on your employer's account. If your employer pays for your charging through us, they can see the sessions billed to them and the name and email address of the person who charged. They see nothing about your own private charging.
  • Site owners, where you charge at their location. A company that hosts a charger sees the sessions on it — when, how much energy and how much it cost — and nothing that identifies who was charging. Parking at someone's building does not make you their customer.
  • Microsoft — our email provider, for the messages and receipts we send you.
  • Apple and Google, for notifications. If you turn notifications on, a message to an iPhone goes through Apple's Push Notification service, and a message to an Android phone through Google's Firebase Cloud Messaging. They receive the device token and the message itself.
  • Google — also as the provider of the map, the font and the QR scanner in the apps (ML Kit), as described above.
  • jsDelivr — a free service that hosts open-source code. It sends the app the code that reads QR codes in a web browser, and sees only your IP address.
  • The national access point for electric vehicle charging, as required by EU Regulation 2023/1804 (AFIR). This receives where the public stations are, whether they are free, and what they cost. It does not receive any information about you or your charging.
  • Public authorities, where the law requires it of us.

Where your data goes

Our servers and our database are in Cyprus. Some of the recipients above are outside the European Economic Area. For each of the countries below, the European Commission has formally decided that the country protects personal data adequately. Your data is therefore protected in the same way as it would be inside the EU, and no further safeguard — such as standard contractual clauses — is required. GDPR Article 45.

  • Switzerland — Worldline (Saferpay). Your card is processed in Zurich. Switzerland has been recognised as providing adequate protection since Commission Decision 2000/518/EC, which the Commission confirmed as remaining in force in January 2024.
  • The United States — Google and Microsoft. Google, for the map, the font, the QR scanner and notifications on Android. Microsoft, for the email we send you. Both are certified under the EU–US Data Privacy Framework, which the Commission recognised as adequate in July 2023.
  • The United Kingdom — jsDelivr, which is run by a company registered in England and Wales. The Commission renewed its decision that the United Kingdom is adequate in December 2025.

Notifications to an iPhone go through Apple. Apple says that the personal data of people in the EEA is controlled by its Irish company, Apple Distribution International, and that Apple protects any transfer out of the EEA with the Commission's standard contractual clauses.

6. How long we keep it

  • Invoices, transactions and the sessions they evidence — six years from the end of the tax year, because Cyprus tax law requires it.
  • Your account — for as long as you have one. After three years of inactivity it is flagged for anonymisation.
  • Guest receipt email addresses — 90 days, then erased automatically.
  • Raw charging station and card reader logs — 90 days.
  • Meter readings — 180 days. The totals that your invoice is based on are kept with the invoice.
  • Notification device tokens — until you turn notifications off in the app or delete your account, or until Apple, Google or your browser tells us the token no longer works, for example because the app was removed. The apps renew their token each time they start. A token that has not been renewed for a year is deleted automatically. In a web browser, it is deleted a year after it was created.
  • Saved cards — we delete our record of a card when you remove it or close your account, and we cannot use the card again after that. Worldline (Saferpay) keeps the stored card on its side for about three years after it was saved, and then deletes it.
  • Contactless card taps — the last four digits and the stand-in code for the card, 180 days, then erased. The payment itself stays with its invoice for six years, as above, without anything identifying the card.
  • Card requests — until you close your account, at which point your name, email, phone number, delivery address and note are removed from the request. A dated record that a card was issued to the account remains, so the operator can revoke a card still in circulation.
  • Problem reports — until you close your account. They hold the station, the category you chose and your account, and nothing you wrote.
  • Records of operator actions on your account — two years. Where an IP address appears in one, it is anonymised after one year.

The dated periods above are enforced automatically by a job that runs every night, not by hand. The ones that run until you close your account are carried out at that point, by the deletion described in section 8.

7. Your rights

Under the GDPR you can ask us to give you a copy of your data, correct it, erase it, restrict what we do with it, or hand it to another provider in a portable form. You can object to any use we base on legitimate interests, and withdraw consent to notifications at any time. Write to info@greencharge.com.cy and we will answer within one month.

Two honest limits on erasure:

  • We cannot delete an invoice, or the session it is based on, before the six years that tax law requires. Your email address stays on an invoice already issued for the same reason. When you close your account we remove it from the account itself.
  • If you charged as a guest, we hold nothing that identifies you, so we cannot find your data to show you or erase it. That is a consequence of collecting as little as possible, not a refusal.

8. Deleting your account

You can delete your account from the app, under Settings. You do not need to install anything to do it — GreenCharge runs in any browser — and you do not need to ask us. If you cannot sign in, email info@greencharge.com.cy from the address on the account and we will do it. Full instructions, and exactly what is removed, are here.

Deleting removes your name, contact details, saved cards, notification settings and device tokens, your saved stations, any charging card registered to you, and the personal details on any card request you made — including the address it was posted to. The identifier of a card you tapped is erased from our charging records too. Invoices and the sessions behind them are kept for the tax period described above, and are no longer linked to your account.

9. Children

GreenCharge is for adults. It is not directed at children and we do not knowingly collect data about anyone under 18. If you believe a child has given us data, contact us and we will remove it.

10. Complaints

If you are unhappy with how we have handled your data, please tell us first so we can put it right. You also have the right to complain to the Cyprus supervisory authority, the Office of the Commissioner for Personal Data Protection (dataprotection.gov.cy), or to the authority in the EU country where you live.

11. Changes to this notice

If we make a material change we will tell you in the app. The version and effective date of the notice you are reading are shown at the top of this page, and previous versions are archived.