Hosting
Code of Conduct Appendix D, dealing with hosting specifics
I - Abide by local laws
This one should be self-explanatory. Please inform yourself regarding any laws that might apply to yourself as well as any EU and/or German laws related to your deployment.
Reason
Ask captain obvious.
Repercussions
Legal action will be taken as necessary.
II - Encryption
Any communication done via WAN (aka, any communication done via "the Internet") MUST be encrypted whenever personal data is concerned.
Reason
Dictated by law as well as common sense.
Repercussions
Hosting of deployments which handle personal data and transmit it in an unencrypted manner is immediately seized and legal action may be taken if necessary, in adherence to the GDPR.
III - Source Availability
Our hosting service is limited to projects which expose their source code to our community (Visibility "Internal") on our Gitlab instance and are actively developed therein. Mirrors are not eligible. As such, only builds done via the CI/CD in our Gitlab instance are applicable to be hosted, and actually able to do so from the get go.
Reason
The hosting is meant to support community-developed projects. Additionally, lightening up on this would foster abuse and make it more likely for malicious code to make it into our hosting.
Repercussions
Once availability of the source is being restricted, the hosting is seized.