Security and Vulnerability Disclosure
1. Reporting a problem
If you think you've found a security problem in Freqlab, email support@freqlab.co with "Security report" in the subject. Tell us what you found, where, and the steps to reproduce it. A proof of concept helps. Please don't include anyone else's personal data.
2. What's in scope
- freqlab.co and all its subdomains, including creator, distro, docs, api, lic (licensing), and assets and apps (downloads)
- The Freqlab Studio and Freqlab Express desktop apps
- Cloud builds, code signing and the licensing that Freqlab adds to built plugins
Plugins and other products that sellers make are their own: report a problem in one to its seller. If it puts buyers at risk, for example malware, report it to us too.
3. What's out of scope
- Denial of service, load or stress testing
- Social engineering or phishing of our staff, sellers or buyers
- Physical attacks on our offices or equipment
- Accessing, changing or deleting other people's accounts or data: use accounts you own or have permission to test
- Problems in other companies' own services we use, including the status and mail subdomains and our payment and email providers: report those to them. Software we run ourselves on our subdomains is in scope.
4. How to test
- Stop as soon as you have shown the problem. Don't keep or share any data you reach, and tell us if you reached any.
- Don't disrupt the service or degrade it for others.
- Give us a reasonable time to fix it before telling anyone else.
5. Safe harbor
If you follow this policy in good faith, we consider your research authorized. We won't take legal action against you or ask anyone to, and we treat it as permitted under our Terms of Service rule on security testing. If someone else takes legal action against you over research that followed this policy, we will make it known that it was authorized. If you are unsure whether something is allowed, ask us first.
6. What happens next
- We acknowledge your report within 3 business days.
- We tell you within 10 business days whether we confirmed it and how serious we think it is.
- We aim to fix confirmed problems within 90 days, and keep you updated.
- We publish or agree to publication about 90 days after a fix, or sooner if we agree with you.
We don't pay bounties. If you'd like, we will thank you by name when the problem is published.