01Our commitment
We hold ourselves to the standards we ask of our clients. If you discover a vulnerability in a system we own, we want to hear about it so we can fix it quickly and protect the people who rely on us.
We will treat good-faith reports seriously, work with you openly, and respect the time and skill that goes into finding and documenting an issue.
02Scope
This policy applies only to systems that SECUREK owns and operates. If you are unsure whether something is in scope, ask us at security@securek.com before testing.
Never test a client's systems while claiming to act on our behalf. We test client environments only under signed authorization and agreed rules of engagement. If anyone claims to be testing a client's systems for SECUREK and you have doubts, please contact us.
- In scope: https://www.securek.com and other web properties owned and operated by SECUREK.
- Out of scope: third-party services we use, such as our hosting, email, form-processing, or font providers. Report issues in those directly to the provider under its own policy.
- Out of scope: any system belonging to our clients, partners, or other organizations, even if it is connected to our work.
03How to report
Email your report to security@securek.com. Please write in English if you can, and send one report per vulnerability unless several issues are closely linked.
If you would like to encrypt your report, ask us at the same address and we will arrange a secure way to send it. Please do not share vulnerability details through social media, public issue trackers, or our general contact form.
04What to include
A clear report helps us confirm and fix the problem faster. Where possible, please include the following:
- The affected URL, page, or component.
- The type of vulnerability and its likely impact.
- Step-by-step instructions to reproduce it, including any requests, payloads, or configuration needed.
- Proof of concept, such as screenshots or a short video, limited to what is needed to show the issue.
- The date and time of your testing and the IP address you tested from, so we can match your activity in our logs.
- How you would like to be contacted and credited, if at all.
05Rules for researchers
To stay within this policy, your research must be in good faith and must avoid harm to us, our users, and our data. In particular:
- Only test systems that are in scope.
- Do not access, copy, change, or delete data beyond the minimum needed to demonstrate the issue.
- If you come across personal or confidential information, stop testing, do not keep or share it, and report it to us straight away.
- Do not run denial-of-service tests or anything that could degrade the availability or performance of our systems.
- Do not use social engineering, phishing, or pretexting against our staff, clients, or partners.
- Do not attempt physical access to our offices, equipment, or facilities.
- Do not use automated scanners in a way that generates heavy traffic.
- Keep the details confidential and give us reasonable time to investigate and fix the issue before any public disclosure.
06Coordinated disclosure
We support public disclosure once an issue has been fixed. Please agree the timing and content of any write-up with us in advance, so that users are not put at risk while a fix is still being prepared.
If we cannot agree on timing, we will explain why and keep talking with you to reach a reasonable outcome.
07What you can expect from us
When you report a vulnerability under this policy, we will:
- Acknowledge that we have received your report.
- Review it, confirm whether we can reproduce the issue, and let you know our assessment.
- Keep you informed as we work on a fix and tell you when it has been resolved.
- Credit you publicly for the discovery if you would like us to, and only with your permission.
- Treat your report and your personal details confidentially, and not share them with third parties without your agreement unless the law requires it.
08Safe harbor
If you research and report a vulnerability in good faith and in line with this policy, we will consider your activity authorized and will not take legal action against you or ask law enforcement to do so, to the extent we are able.
We cannot authorize testing of systems we do not own, and we cannot bind third parties or public authorities. If legal action is started against you by someone else for activity that followed this policy, we will make it known that your research was authorized by us.
09No bug bounty
We do not currently run a bug bounty program and do not offer payment or rewards for reports. Submitting a report does not create any employment, contract, or payment obligation. We are grateful for your help and are happy to recognize your contribution publicly if you wish.
10Contact
Send vulnerability reports and questions about this policy to security@securek.com. For anything unrelated to security, please use contact@securek.com. We may update this policy from time to time; the date at the top of this page shows when it last changed.