STATIQLightning fast NL

Responsible Disclosure

Responsible Disclosure: report a vulnerability

We take the security of webshops and customer data seriously. Did you find a vulnerability in one of our services? We would like to hear about it, so we can fix it before anyone else abuses it.

How to report a vulnerability

Send an email to hello@statiq.shop with the subject “Responsible Disclosure”. Please do not use any other channel for your report.

Describe where you found the vulnerability, how we can reproduce it and what you think the impact is. One vulnerability per report. Without contact details we cannot reply to you or reward you.

What you can expect from us

  • You get a response to your report within three working days.
  • We keep you informed about the progress and tell you when the vulnerability has been fixed.
  • We only use your details to communicate with you, unless the law forces us to share them.
  • If you act in good faith and follow these rules, we will not file a report with the police and will not take legal action against you.
  • If you wish, we name you as the reporter after the vulnerability has been fixed.

Rules

  • Keep the vulnerability confidential until we have fixed it and do not make it public.
  • Show clearly how the vulnerability can be exploited, with as few actions as possible.
  • Do not copy, change or delete data of others and do not look further than needed to demonstrate the problem.
  • Do not use social engineering, backdoors, brute-force attacks or attacks that take the service down.
  • Do not share any access you obtained and do not try to break in more often than needed.
  • Respond to our requests for more information.

What is in scope

Our own services and all webshops built with Statiq are in scope: the website statiq.shop, the dashboard at cockpit.statiq.shop, the public API at api.statiq.shop and the webshops themselves, with their themes, cart and checkout. Think of cross-site scripting, SQL injection, bypassing login or permissions, and weaknesses in the secure connection.

What is out of scope

  • The content that shop owners post themselves, such as texts, images and products. We are not responsible for that.
  • Services of other parties, such as our status page, payment providers, email providers and the POS system.
  • Complaints, reports that a site is briefly unavailable, fraud, phishing emails and malware. For those, please contact us in the usual way.

Bonus policy

We appreciate your help. Whether you receive a reward, and how large it is, depends on the risk and impact of the vulnerability. A reward can range from a thank-you or some merchandise to a payment in cash. There are no fixed amounts and we cannot promise that an earlier reward will be the same in future.

A reward only applies to new, serious security problems. If a vulnerability was already reported, the first reporter receives the reward. One vulnerability earns one reward, for one person. Reports with a low risk or without a security impact usually receive no reward. Anonymous reports receive no feedback and no reward.

Usually not rewarded

  • An HTTP status code other than 200, version numbers in headers and public files without sensitive content.
  • Clickjacking or CSRF on forms without login.
  • Missing security headers or cookie flags without a demonstrable impact.
  • Findings about the SSL certificate, SPF, DKIM, DMARC or DNSSEC without a demonstrable impact.
  • Outdated software without a working exploit, and general best practices.
  • Tabnabbing and similar reports with a very low risk.

More about this policy

This policy is based on the guidance of the Dutch National Cyber Security Centre (NCSC) on responsible disclosure: getting started with a responsible disclosure policy (opens in a new window). Last updated on 18 November 2026.