Contact

Please email us at .

We will answer as soon as we can, but we can not guarantee any response time. In the mean time search for answers on the Manual page or in the guides posted on the Resources page.

Please email us at .

Please email us at .

Provide us with as much information as you can. Screenshots can be very helpful, and if you did things in a certain order to trigger the problem.

Your program version and environment are also important. Copy and include the system information text from the Settings / About page if you can.

You are most welcome to suggest new features and improvements. Your feedback makes The PlanMinder better.

Thank you for helping us keep our software secure. If you have discovered a vulnerability or an incident affecting our software products, please report it to us by sending an email to:

.

If your report concerns an actively exploited vulnerability or severe incident, start the subject line with URGENT: to alert our on call incident team.

To help us investigate and remediate the issue as quickly as possible, please include the following information in your report:

• Product Information
• Product name and version
• Platform / Environment. (For The PlanMinder, copy the system information in Settings / About).
• Vulnerability Description
• Type of vulnerability: (e.g., Buffer Overflow, SQL Injection, Remote Code Execution, Privilege Escalation).
• Impact: A brief assessment of what an attacker could achieve by exploiting this vulnerability.
• Technical Details & Proof of Concept
• Step-by-Step Instructions: Clear, detailed steps to reproduce the vulnerability.
• Proof of Concept Code: If available, provide a minimal code snippet, script, or payload that demonstrates the issue.
• Screenshots/Logs: Attach relevant logs or screenshots that visualize the exploit or vulnerability context.
• Your Contact Information (unless you wish to remain anonymous).

Note:

Emails to this address not concerning vulnerabilities or security incidents will be ignored.

We do not operate a paid bug bounty program.

The following findings are considered out of scope and will not receive a manual response:

• Missing HTTP security headers (e.g., CSP, X-Frame-Options) without a working Proof of Concept (PoC) demonstrating an exploit.
• SPF/DKIM/DMARC configuration issues.
• Automated scanner reports without detailed, manual validation and an actionable PoC.

Please email us at .

You are welcome to email us at .