SiteForge KitSearch, without the folklore
Privacy

Privacy policy

Last reviewed: 1 September 2026. The version published here is the one in force; earlier versions are superseded by it.

Identity of the controller

ELO Cloud GmbH
Tübinger Straße 43
70178 Stuttgart, Germany
Email: [email protected]

No data protection officer has been appointed, because none of the circumstances requiring one under Article 37 of Regulation (EU) 2016/679 applies. Any question about your data can be sent to the email address above.

Categories of data

Only the details you provide voluntarily through the contact form: name, email address, subject and the content of the message.

Reading requires no identification. There are no visitor statistics, no external cookies and no tracking technologies; nor are profiles built.

The sole purpose is to answer what you have raised. We rely on your express consent — the tick box on the form — as provided in Article 6(1)(a) of Regulation (EU) 2016/679. Your data serves nothing else.

Retention

We retain your message for the time needed to reply and up to a further twelve months, in case the exchange continues. Once that period passes, it is removed.

Processors and disclosures

There are no disclosures and no international transfers. Technical access is limited to the hosting and email provider, which acts as a processor under a contract complying with Article 28 of the Regulation.

Exercising your rights

You may at any time exercise your rights of access, rectification, erasure, restriction of processing, objection and portability, and withdraw the consent you gave. Write to [email protected] stating which right you wish to exercise. We reply within one month at the latest.

If you believe the processing does not comply with the rules, you may lodge a complaint with the competent supervisory authority. In the Netherlands this is the Autoriteit Persoonsgegevens; in Germany, the authority of the federal state in which the company has its registered office.

Information security

The site is served entirely over HTTPS. The form applies a submission limit per IP address and a bot trap, and no submitted value is used to construct mail headers. Messages are not stored in a database: they are forwarded by email and kept in the publisher's mailbox.