Contact & support
One address, read by the person who writes the software. info@cysectek.com
There is no ticket system, no support tier and no response-time commitment — this is one person’s project, and pretending otherwise would waste your time. In practice, reproducible bugs get fixed and questions get answered.
Before you write
Where to look first
Not a deflection — most questions are answered faster by one of these than by waiting for a reply.
Something is broken
Check the troubleshooting guide first — it covers the errors people actually hit, and several of them are Windows permissions rather than faults in the app. If yours is not there, email it.
Troubleshooting →A question about what it does
The FAQ answers the common ones, including several with an honest 'no'. The documentation goes further, guide by guide.
Read the FAQ →A security issue
Report it privately first, with reproduction steps and the impact you think it has. You get an acknowledgement, an honest severity assessment, and credit in the release notes if you want it.
Disclosure policy →Deploying it somewhere large
Read the enterprise page, particularly the part about the unsigned installer and application-control policies. Then get in touch if you want to talk it through.
Enterprise deployment →Reporting a bug
What to put in the email
These four things are the difference between a bug that gets fixed and one that gets a reply asking for more detail.
- 1The version. On the About screen inside the app. Current release is 0.7.1.
- 2The exact message. Copy the text rather than describing it — the wording usually identifies which code path failed.
- 3What you were doing. Which screen, and what you had pressed.
- 4What the equipment is, where the answer depends on it — switch make and model for LLDP problems, the SSH server version for connection failures.
Do not send credentials
Get in touch
Bugs, questions, security issues, or a correction to something on this site that is not accurate.