---
title: "Vulnerability Disclosure Policy"
description: "Vulnerability Disclosure Policy — last updated November 9, 2026"
canonicalUrl: "https://zuplo.com/legal/security-policy"
pageType: "legal"
lastUpdated: "November 9, 2026"
---
This Vulnerability Disclosure Policy explains how to report security
vulnerabilities in Zuplo products and services, and the terms under which Zuplo,
Inc. ("Zuplo") welcomes good-faith security research. For information about
Zuplo's security and compliance practices, see our
[Trust Center](https://trust.zuplo.com) and
[security documentation](https://zuplo.com/docs/security).

## Reporting security issues

Zuplo takes the security of our software products and services seriously, and we
review every report we receive.

If you believe you have found a security vulnerability in any Zuplo-owned
repository, product, or service, please report it to us through coordinated
disclosure.

**Please do not report security vulnerabilities through public GitHub issues,
discussions, or pull requests.**

Instead, please send an email to
[security@zuplo.com](mailto:security@zuplo.com).

Please include as much of the information listed below as you can to help us
better understand and resolve the issue:

- The type of issue (for example, buffer overflow, SQL injection, or cross-site
  scripting)
- Full paths of source file(s) related to the manifestation of the issue
- The location of the affected source code (tag/branch/commit or direct URL)
- Any special configuration required to reproduce the issue
- Step-by-step instructions to reproduce the issue
- Proof-of-concept or exploit code (if possible)
- Impact of the issue, including how an attacker might exploit the issue

This information will help us triage your report more quickly.

## Rules of engagement

To be covered by the safe harbor below, you must:

- test only against accounts and projects that you own or have explicit
  permission to test;
- stop testing and report to us immediately if you access, or could access, data
  that does not belong to you, and do not view, copy, keep, change, or delete
  that data beyond what is needed to show the issue;
- not degrade or disrupt the Zuplo service or other customers, including through
  denial-of-service attacks, high-volume automated testing, or spam;
- not use social engineering, phishing, or physical attacks against Zuplo, its
  employees, or its customers; and
- give us a reasonable amount of time to investigate and fix the issue, and not
  disclose the issue, or any data you accessed, to anyone else without our prior
  written consent.

## Safe harbor

Gold Standard 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 that follows the rules of engagement
above to be authorized activity that is protected from adversarial legal action
by us. We waive any relevant restriction in our
[Terms of Service](/legal/terms), our
[Acceptable Use Policy](/legal/acceptable-use-policy), or any other agreement
you have with us that conflicts with the standard for Good Faith Security
Research outlined here, but only for that research.

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.

This safe harbor covers only Zuplo's own systems. It does not authorize testing
of APIs, Developer Portals, or other services that Zuplo customers run on the
Zuplo platform; for those, you need the permission of the customer that owns
them.

## Rewards

Zuplo **DOES NOT OFFER ANY FORM OF PAYMENT OR BOUNTY** for bug reports.
Legitimate reports are always appreciated.

## Scope exclusions

The following are out of scope:

- Findings from automated scanning tools without a demonstrated security impact.
- Clickjacking on pages with no sensitive actions.
- Unauthenticated/logout/login CSRF.
- Attacks requiring MITM or physical access to a user's device.
- Any activity that could lead to the disruption of our service (DoS).
- Content spoofing and text injection issues without showing an attack vector.
- Email spoofing.
- Missing DNSSEC, CAA, CSP headers.
- Lack of Secure or HTTP only flag on non-sensitive cookies.
- Weak SSL/TLS algorithms or protocols.
- Best practices violations (password complexity, expiration, re-use, etc.).
- Spam or Social Engineering techniques.
- Bugs that do not represent any security risk.
- Application or server error messages, stack traces.

## Changes to this policy

Zuplo may modify this policy at any time by posting a new version on this page
and updating its "Last updated" date. Changes apply to research conducted after
they are posted.