Privacy policy
This is a translation for convenience. The German version prevails.
Controller
The controller responsible for processing personal data on this website (charger-support.com) within the meaning of the General Data Protection Regulation (GDPR) is:
Sebastian Böttger – IT and EV charger supportFalkenweg 4
82069 Schäftlarn
Germany
Phone: +49 151 67029006
Email: kontakt@charger-support.com
Summary
- No cookies, no tracking, no analytics or advertising services.
- No third-party content: fonts, images and scripts are served exclusively from this server.
- The web server logs requests with truncated IP addresses only and deletes the logs after 7 days.
- Form entries and uploaded files are stored encrypted and deleted after 30 days at the latest if no engagement results.
- The OCPP check stores technical data of the charge point you connect only – no charging card identifiers – and deletes it no later than 14 days after the last contact.
- No automated decision-making, including profiling, takes place.
Hosting
This website is hosted by: IONOS SE, Elgendorfer Str. 57, 56410 Montabaur. IONOS SE processes data solely on my behalf and according to my instructions. The connection between your browser and the server is encrypted via HTTPS (TLS).
Server log files
Each time this website is accessed, the web server automatically processes the following data:
- IP address, truncated before storage: IPv4 addresses to the first 24 bits (/24), IPv6 addresses to the first 48 bits (/48)
- date and time of the request
- requested address (URL), HTTP method and status code
- amount of data transferred
- previously visited page (referrer), if your browser transmits it
- browser identification (user agent)
The purpose is to deliver the website and to ensure stability and security, in particular to detect and prevent misuse and to analyse errors. The legal basis is Art. 6(1)(f) GDPR; my legitimate interest lies in the secure and error-free operation of the website. Log files are deleted automatically after 7 days. They are not combined with other data sources.
Web server error messages relating to a request are written to the server's system log. There, too, the IP address is stored in truncated form only, and the system log is deleted after 7 days at the latest.
Cookies, tracking and third-party content
This website does not set cookies and does not use tracking, analytics or advertising services. No third-party content is embedded – no external fonts, content delivery networks, maps, videos or social media plugins. Visiting this website therefore does not transmit any data to third parties.
External links
This website contains links to external services, for example to my personal profile at sebastianboettger.de (with its own privacy policy) or to the website of the ALTCHA spam protection (altcha.org). No data is transmitted to these providers when you visit this website. Only when you click such a link does your browser connect to the respective provider; from then on, that provider's privacy policy applies.
Contact by email or phone
If you contact me by email or phone, I process the details you provide (for example name, email address, phone number and the content of your enquiry) in order to handle your request. The legal basis is Art. 6(1)(b) GDPR where your enquiry relates to a contract, otherwise Art. 6(1)(f) GDPR (legitimate interest in answering enquiries). I delete the data as soon as it is no longer required for this purpose, unless statutory retention obligations apply.
Emails to kontakt@charger-support.com and to other addresses under charger-support.com are stored in mailboxes operated on my behalf by IONOS SE as processor.
Contact form and pilot form
If you use the contact form or the pilot form, I process the details you enter (for example name, company, email address and a description of your request) in order to handle your enquiry and prepare an offer. The legal basis is Art. 6(1)(b) GDPR (pre-contractual measures) or Art. 6(1)(f) GDPR (legitimate interest in handling enquiries). Providing the details is voluntary; without them, however, I cannot process your request.
Entries are stored encrypted on the server. I am notified of new entries by email; notifications are sent via the email service of IONOS SE acting as processor. If no engagement results from your enquiry, I delete the data after 30 days at the latest. If an engagement results, I keep it for the duration of the collaboration and in line with statutory retention obligations.
File upload in the pilot form
The pilot form lets you upload files such as log files or protocol traces. Please upload pseudonymised data only – remove or replace personal data such as names, email addresses, charging card and contract identifiers or vehicle identification numbers beforehand.
Uploaded files are stored encrypted, used exclusively to handle your request and deleted according to the same periods as form entries. The legal basis is Art. 6(1)(b) GDPR or Art. 6(1)(f) GDPR.
Case-specific upload link
For a commissioned case, I send you a personal upload link. You use it to transmit raw data such as log files, OCPP traces or configurations – only after a non-disclosure agreement and, where personal data is involved, a data processing agreement (DPA) have been concluded.
If the files contain personal data, for example about your company's end customers, I process it as a processor solely on your behalf and according to your instructions (Art. 28 GDPR); your company is the controller for this data. The details are set out in the DPA.
The link is valid for one case only, for a limited time and a limited volume. The access key is in the part of the address after “#”; this part does not appear in the web server logs. Uploaded files are stored encrypted on the server and deleted there once collected, after 30 days at the latest. Further processing and deletion are governed by the DPA.
Spam protection with ALTCHA
To protect the forms against automated submissions, I use ALTCHA. ALTCHA is self-hosted on this server: before submitting, your browser solves a small computational task (proof of work). No cookies are set, no third-party content is loaded and no data is passed on to third parties. The legal basis is Art. 6(1)(f) GDPR; my legitimate interest lies in protection against misuse.
Request limits
To prevent mass submissions, the form service counts requests per IP address (for IPv6, per address range of the first 64 bits). For this purpose the address is held in memory only, is neither written to disk nor logged, and is discarded after 10 minutes. The legal basis is Art. 6(1)(f) GDPR; my legitimate interest lies in protection against misuse.
OCPP check (self-service diagnosis of a charge point)
On the home page and under “OCPP check” I offer an OCPP check: you can temporarily connect a charge point to an OCPP backend operated by me at wss://charger-support.com/ocpp/<charge point ID>. The charge point then sends the messages defined by the OCPP protocol on its own (for example BootNotification, StatusNotification, Heartbeat, MeterValues); after registration the service additionally requests the charge point's configuration (OCPP 1.6: GetConfiguration and TriggerMessage; OCPP 2.0.1: TriggerMessage). You retrieve the result on the website by entering the charge point ID.
Data processed: the charge point ID you chose; vendor, model, serial number and firmware version of the charge point; connection status with the times of first and last contact and connection drops; per connector the status, error codes, vendor-specific error codes and additional text; selected configuration values; the last meter reading per connector; OCPP version and heartbeat interval. Not stored: charging card identifiers (idTag/idToken), data on individual charging sessions, and any credentials the charge point may send via HTTP basic authentication; authorisation requests are answered generically without checking or storing the identifier. The charge point's IP address appears only in the web server's access log – truncated as described above and for 7 days; in the requested address recorded there, the charge point ID is replaced by “-”. The service itself logs neither IP addresses nor charge point IDs in clear text.
Purpose and legal basis: the purpose is the technical assessment of the charge point that you initiate. The legal basis is Art. 6(1)(b) GDPR (providing the check you requested) and otherwise Art. 6(1)(f) GDPR (legitimate interest in secure operation and protection against misuse). I am the controller for this processing because you use the check yourself and without an engagement. The data usually relates to a device, not a person; please choose a charge point ID that contains no name, email address or other personal details.
Retention: the data is held in the service's memory and in a backup file on the server and is deleted automatically no later than 14 days after the charge point's last contact. To have it deleted earlier, send an informal email stating the charge point ID.
Limits and request limits: the OCPP check is a diagnostic tool, not a charging backend: no billing, no load management, no activation of charging cards, not for permanent operation. To limit misuse, the service counts connections and queries per IP address (for IPv6, per address range of the first 64 bits); the address is held in memory only and discarded after 10 minutes (Art. 6(1)(f) GDPR). Anyone who knows a charge point ID can retrieve its result; therefore use an ID that is hard to guess – the website suggests a random one.
Your rights
Under the GDPR you have the right to
- access the data processed about you (Art. 15),
- rectification of inaccurate data (Art. 16),
- erasure (Art. 17),
- restriction of processing (Art. 18),
- data portability (Art. 20) and
- object to processing (Art. 21).
Right to object: where processing is based on Art. 6(1)(f) GDPR, you may object to it at any time on grounds relating to your particular situation.
An informal message to kontakt@charger-support.com is sufficient for any request.
Right to lodge a complaint
You have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR). The competent authority is: Bayerisches Landesamt für Datenschutzaufsicht (BayLDA), Promenade 18, 91522 Ansbach.
Last updated: 17 October 2026