A look behind the hoodies.

No. The conditions for the hackers should be as real as possible. Normally your productive system/network is tested directly. This allows you to find gaps that may be closed on the test server but still exist in production or in components that only exist there.

On our platform, you – and of course our hackers – will find a precise list of what is permitted and what is prohibited. You can include or exclude further points. We are also happy to assist you if you have any questions. However, if you are unsure, we recommend that you simply use the Hacky template, as it includes and excludes everything relevant and will certainly be ideal for you to start with.

We always try to communicate as clearly and simply as possible. It may happen that we use a term that you are not familiar with. We would therefore like to discuss how we define and interpret certain terms.

Hacker, Expert, White Hat, Ethical Hacker

A person who has excellent knowledge of computer security and specializes in finding vulnerabilities in networks, software and systems. We always act ethically and never exploit these vulnerabilities, but report them immediately to the individuals and companies concerned.

Bug Bounty

If a reward is paid to the finder for reporting a vulnerability or bug.

Bug, Vulnerability, Vulnerability, Gap

When a system or software does not behave as expected. This behavior of the software could then potentially alienate purpose.

(Hacker) Community

All hackers who search for possible vulnerabilities in the listed infrastructures on our platform and report them to us.

bounty, reward

If a hacker reports a valid vulnerability, they will receive a reward for it.

Scope

Defines the area or the systems that may be tested for bugs/vulnerabilities and the methods with which these tests are permitted.  

Safety is our top priority, that is clear. All registered experts are clearly made aware of our guidelines and confirm that they will adhere to them. Since our community consists of independent hackers who search for security vulnerabilities on their own, we cannot be held liable for their actions. Of course, we do not tolerate any misuse of our program, platform or offer. If our guidelines are seriously violated, the persons concerned will be blocked from our platform for an indefinite period of time.

The team currently consists of Manuel Lusti and Philipp Brügger. Both currently only receive a salary from their own web agency Codia. Hacky itself is not yet making any money, which is why the two of them invest their time and love in Hacky. This, of course, with the hope of being able to pay themselves a modest salary in early 2025 so that they can invest more of their workload in Hacky (and still have money for pasta and tomato sauce).

When the finished Hacky product is launched, every hacker should be able to report vulnerabilities. Regardless of whether the person is registered with Hacky or not, as the discovery and subsequent rectification of a vulnerability is the top priority. In the current test phase, we are working with hackers that we know and have already worked for us.

Our next goal is to validate our platform and our idea ourselves and find out whether there is a need for Hacky. We have created a prototype for this. Together with a few selected companies, we can use this to test our concept and identify and solve major problems. Once we know that Hacky really solves our customers’ problems, we will expand the platform and open it up to all companies. We assume that this will be the case in late summer.

We currently have a deficit of CHF -2’528.66, not including the countless hours of work. This was the result of various expenses. Tickets for events, participation fees for sponsorship programs or advertising materials, such as our green hoodies. Hacky is not generating any revenue at the moment, as we are still developing the prototype and cannot (yet) sell a finished product. Although a minus never looks good, it is not tragic for us and was planned for.

Hacky is a project, or rather a product, by Manuel Lusti and Philipp Brügger and is supported by Codia. Hacky’s home is Switzerland 🇨🇭.

Manuel Lusti and Philipp Brügger work together on Hacky. Their joint web agency, Codia, supports the two founders in the further development of Hacky. Codia and Hacky are self-financed by the two founders and all shares are owned by them, without investor:in, loan or credit. Hacky is currently a project by Manuel Lusti and Philipp Brügger, which is supported by Codia. Hacky, like Codia, is independent and has no external influencers.

We try to store as little data as possible about our users. However, in order to develop our prototype as efficiently as possible, we decided to integrate Microsoft Clarity. This tool enables us to understand how users use the platform and where problems and difficulties arise. We do not actively pass on your data and of course we do not sell it. However, there are some providers, such as our web server providers, to whom we inevitably pass on data. You can find a list of all these providers here: The prototype is developed with Bubble and hosted on their platform. (To Bubble’s privacy policy ) As far as we know, images are stored by Bubble using Amazon Web Services. In order to contact you by email, we use the email marketing tool loops.so and you can find their privacy policy here. Our website (hacky.ch) was implemented with WordPress, with the help of Elementor and is hosted on Metanet servers. We use Google Fonts and Google Analytics, as well as Microsoft Clarity. You can find the complete data protection provisions in “legalese” here: https://hacky.ch/datenschutz/

We are currently working on the general terms and conditions. You can find the provisional terms and conditions at https://hacky.ch/agb/.