Responsible Disclosure Policy

Responsible Disclosure Policy

Last updated: Jul 26, 2022
Notion Labs, Inc. looks forward to working with the security community to find security vulnerabilities in order to keep our businesses and customers safe.
We only accept disclosure via HackerOne, you can submit using this link:

Response Targets

Notion Labs, Inc. will make a best effort to meet the following response targets for hackers participating in our program:
  • Time to first response (from report submit) - 3 business days
  • Time to triage (from report submit) - 10 business days
  • Time to bounty (from triage) - Varies
We’ll try to keep you informed about our progress throughout the process. Feel comfortable reaching out with any questions.

Disclosure Policy

  • As this is a private program, please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.

Program Rules

  • Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.
  • Submit one vulnerability per-report, unless you need to chain vulnerabilities to provide impact.
  • When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
  • Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
  • Social engineering (e.g. phishing, vishing, smishing) is prohibited.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with the explicit permission of the account holder.

In Scope Targets

  • Notion iOS app
  • Notion Android app

Out of Scope Vulnerabilities

When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug.

Note: Notion does not accept vulnerabilities in third-party services, unless specific mitigations from Notion are required to remediate the issue.

The following potential issues are not considered in scope:

  • Social engineering or phishing of Notion employees or contractors
  • Any attacks against Notion's physical property or data centers
  • Any attacks against Notion's users
  • Use of automated scanning tools
  • Lack of rate limiting on any resources
  • Password policy issues, including lack of upper limit on passwords
  • Banner or version disclosure of any kind
  • Presence of common public files, such as robots.txt or files in the .well-known directory
  • Self-XSS issues
  • Spamming
  • Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
  • Clickjacking on pages with no sensitive actions
  • Clickjacking issues, unless an exploit showing account takeover or disclosure of sensitive resources is provided
  • Cross-Site Request Forgery (CSRF) / Server-Side Request Forgery (SSRF) on unauthenticated forms or forms with no sensitive actions
  • Attacks requiring MITM or physical access to a user's device.
  • Previously known vulnerable libraries without a working Proof of Concept.
  • Comma Separated Values (CSV) injection without demonstrating a vulnerability.
  • Missing best practices in SSL/TLS configuration.
  • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
  • Rate limiting or bruteforce issues on non-authentication endpoints
  • Missing best practices in Content Security Policy
  • Missing security headers which don’t directly lead to a vulnerability or account compromise
  • Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
  • Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors)
  • Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis
  • Tabnabbing
  • Open redirect - unless an additional security impact can be demonstrated
  • Notion hosting malware / Spam / Phishing websites

Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.
Thank you for helping keep Notion Labs, Inc. and our users safe!
Got other non-security related questions? Message us in the app or email us at