Gigs Vulnerability Disclosure Policy

Last Updated: September 10, 2025

1. Introduction

Gigs welcomes feedback from security researchers and the general public to help improve our security. If you believe you have discovered a vulnerability, privacy issue, exposed data, or other security issues in any of our assets, we want to hear from you. This policy outlines steps for reporting vulnerabilities to us, what we expect, what you can expect from us.

2. Systems in Scope

  • This policy applies to any digital assets owned, operated, or maintained by Gigs.

  • As a non-exhaustive list, this includes:

    • Gigs API

    • Gigs Blog

    • Gigs Connect

    • Gigs Dashboard

3. Out of Scope

Below is a non-exhaustive list of out of scope systems and activities:

  • Assets or other equipment not owned by parties participating in this policy. Vulnerabilities discovered or suspected in out-of-scope systems should be reported to the appropriate vendor or applicable authority.

  • Social engineering or phishing attacks targeting users or staff

  • Reports from scanners and automated tools

  • Email enumeration or revealing of the validity of an email being registered in our systems

  • Brute force attacks

  • Denial of Service attacks where the outcome is resource exhaustion

  • Missing HTTP security headers, unless accompanied by a detailed proof of concept exploit that leverages their absence

4. Our Commitments

When working with us, according to this policy, you can expect us to:

  • Respond to your report promptly, and work with you to understand and validate your report;

  • Strive to keep you informed about the progress of a vulnerability as it is processed;

  • Work to remediate discovered vulnerabilities in a timely manner, within our operational constraints; and

  • Extend Safe Harbor for your vulnerability research that is related to this policy.

5. Our Expectations

In participating in our vulnerability disclosure program in good faith, we ask that you:

  • Play by the rules, including following this policy and any other relevant agreements. If there is any inconsistency between this policy and any other applicable terms, the terms of this policy will prevail

  • Report any vulnerability you’ve discovered promptly

  • Avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience

  • Use only the Official Channels to discuss vulnerability information with us

  • Provide us a reasonable amount of time (at least 90 days from the initial report) to resolve the issue before you disclose it publicly

  • Perform testing only on in-scope systems, and respect systems and activities which are out-of-scope

  • If a vulnerability provides unintended access to data: Limit the amount of data you access to the minimum required for effectively demonstrating a Proof of Concept; and cease testing and submit a report immediately if you encounter any user data during testing, such as Personally Identifiable Information (PII), Personal Healthcare Information (PHI), credit card data, or proprietary information

  • You should only interact with test accounts you own or with explicit permission from the account holder

  • Do not engage in extortion.

6. Official Channels

Please report security issues via security@gigs.com providing all relevant information. The more details you provide, the easier it will be for us to triage and fix the issue. Our optional public PGP key can be found linked in our security.txt.

7. Safe Harbor

Safe Harbor supports the protection of organizations and hackers engaged in Good Faith Security Research. “Good Faith Security Research” is accessing a computer solely for purposes of good-faith testing, investigation, and/or correction of a security flaw or vulnerability, where such activity is carried out in a manner designed to avoid any harm to individuals or the public, and where the information derived from the activity is used primarily to promote the security or safety of the class of devices, machines, or online services to which the accessed computer belongs, or those who use such devices, machines, or online services.

We consider Good Faith Security Research protected from adversarial legal action by us. This means that, for activity conducted while this program is active, we:

  • Will not bring legal action against you or report you for Good Faith Security Research, including for bypassing technological measures we use to protect the applications in scope; and,

  • Will take steps to make known that you conducted Good Faith Security Research if someone else brings legal action against you.

You should contact us for clarification before engaging in conduct that you think may be inconsistent with Good Faith Security Research or unaddressed by our policy.

Keep in mind that we are not able to authorize security research on third-party infrastructure, and a third party is not bound by this safe harbor statement.

8. Access

We currently do not offer special access to the Gigs platform for security researchers.

9. Bounties

We currently do not maintain a formal bug bounty program. We will pay out bounties for outstanding submissions though.