https://quollix.org/docs/contact/Recent content in Contact on QuollixHugoen-ushttps://quollix.org/docs/contact/commercial-support/Mon, 01 Jan 0001 00:00:00 +0000https://quollix.org/docs/contact/commercial-support/<p>Commercial support and paid project work are available for Quollix. This can include deployment help, custom feature work, technical consulting, training, presentations, or related work around Quollix. Quollix remains open source software. Paid work helps fund continued development and maintenance. Commercial work is handled from Bremen, Germany, with remote collaboration available.</p> <p>If you are interested, contact <a href="mailto:quollix-commercial@mailbox.org">quollix-commercial@mailbox.org</a> with a short description of what you need.</p> <p><button type="button" class="feedback-draft-button" onclick="window.openCommercialSupportMail()">Open draft</button></p> <script> window.openCommercialSupportMail = () => { const body = `Hi Quollix team, I want to contact you about commercial support. What I need help with: Organization, if relevant: Preferred contact details: ` window.location.href = `mailto:quollix-commercial@mailbox.org?subject=${encodeURIComponent('Quollix commercial support')}&body=${encodeURIComponent(body)}` } </script>https://quollix.org/docs/contact/feedback/Mon, 01 Jan 0001 00:00:00 +0000https://quollix.org/docs/contact/feedback/<p>We appreciate feedback about:</p> <ul> <li>Quollix and the website</li> <li>Positive experiences with the project</li> <li>Legal and policy texts that are unclear, too broad, or missing important context</li> <li>The topics listed below</li> </ul> <table> <thead> <tr> <th>Topic</th> <th>Use this for</th> <th>Action</th> </tr> </thead> <tbody> <tr> <td>Security vulnerability</td> <td>Responsible disclosure or suspected vulnerabilities in Quollix. Please read the <a href="https://quollix.org/docs/contact/security/">Security Policy</a> first.</td> <td><button type="button" class="feedback-draft-button" onclick="window.openSecurityFeedbackMail()">Open draft</button></td> </tr> <tr> <td>Bug report</td> <td>Reproducible behavior that seems incorrect.</td> <td><button type="button" class="feedback-draft-button" onclick="window.openBugFeedbackMail()">Open draft</button></td> </tr> <tr> <td>Suggest an improvement</td> <td>Feature ideas, additional official apps, <a href="https://quollix.org/docs/project/community/contributing/website/">website text improvements</a>, and workflows that feel confusing or slow.</td> <td><button type="button" class="feedback-draft-button" onclick="window.openImprovementFeedbackMail()">Open draft</button></td> </tr> </tbody> </table> <script> window.openFeedbackMailWithTemplate = (subject, body) => { window.location.href = `mailto:quollix-feedback@mailbox.org?subject=${encodeURIComponent(subject)}&body=${encodeURIComponent(body)}` } window.openSecurityFeedbackMail = () => { const body = `Hi Quollix team, I want to report a potential security vulnerability. Summary: Affected area or version: Steps to reproduce: 1. 2. 3. Potential impact: Suggested disclosure handling: ` window.openFeedbackMailWithTemplate('Quollix security: Vulnerability report', body) } window.openBugFeedbackMail = () => { const body = `Hi Quollix team, What I did: What I expected: What happened instead: Steps to reproduce: 1. 2. 3. How often it happens: Always / Sometimes / Once ` window.openFeedbackMailWithTemplate('Quollix feedback: Bug report', body) } window.openImprovementFeedbackMail = () => { const body = `Hi Quollix team, What I am trying to do: What feels missing, confusing, or frustrating today: Suggested improvement: How this would help me: ` window.openFeedbackMailWithTemplate('Quollix feedback: Improvement suggestion', body) } </script> <h2 id="miscellaneous">Miscellaneous</h2> <p>Feedback can also be sent directly to <a href="mailto:quollix-feedback@mailbox.org">quollix-feedback@mailbox.org</a>.</p>https://quollix.org/docs/contact/security/Mon, 01 Jan 0001 00:00:00 +0000https://quollix.org/docs/contact/security/<p><em>Last Updated: 24.05.2026</em></p> <p>We welcome good-faith security research on Quollix and appreciate responsible vulnerability reports. You may investigate Quollix software, especially by reviewing the source code or testing your own self-hosted Quollix server.</p> <p>Please test responsibly. Do not target other users&rsquo; deployments, third-party systems, or data that is not yours without explicit authorization. Limited testing against Quollix-operated public services is acceptable when done carefully and without disrupting availability. Do not perform denial-of-service attacks, degrade service availability, misuse the service, retain unauthorized access, publish secrets, or continue exercising a vulnerability after you have confirmed it.</p>