Skip to content

Black Friday 50% off your first year on all premium plugins and the Suite.

See the deals
Legal

Security overview

How to report a vulnerability, and how we handle one.

Last updated 5 November 2026

1. Reporting a vulnerability

Email contact@bytekeel.com with the subject Private security report. Please include:

  • the plugin or service and its version;
  • your WordPress, PHP and theme or builder versions;
  • steps that reproduce the problem on a test site you own, and what an attacker could do with it.

Please do not open a public issue or post details before a fix is released. Do not send passwords, API keys, licence keys or customer data, and do not test against websites you do not own.

2. What happens next

  • We confirm by email that the report arrived, then reproduce it on a test site.
  • A confirmed issue is fixed in a new release. The fix is listed in the public changelog with its version and date, without exploit details.
  • If you would like credit, tell us the name to use and we will add it to that changelog entry.

Reports are handled by email. As with support, no fixed response or resolution time is promised.

3. Scope

In scope: the plugins listed on ByteKeel products, this website, and the licence and download service the plugins use for updates.

Out of scope: other vendors' plugins and themes, payment pages run by Paddle (report those to Paddle), social engineering, and load or denial-of-service testing.

4. How the plugins are built

  • Every release is listed in the changelog with its version and date, and planned work is on the public roadmap.
  • Licence responses from the licence service are signed, and the plugins check the signature before trusting them.
  • If the licence service cannot be reached, a licensed plugin stays licensed for the rest of its paid term; an outage on our side does not switch it off.
  • The plugins do not send your visitors' data to ByteKeel.