docs: drop bug bounty wording, route disclosures to email

Author: PaulRBerg

README.md

@@ -104,8 +104,7 @@ The list of all deployment addresses can be found [here](https://docs.sablier.co
 The codebase has undergone rigorous audits by leading security experts from Cantina, as well as independent auditors.
 For a comprehensive list of all audits conducted, please click [here](https://github.com/sablier-labs/audits).
 
-For any security-related concerns, please refer to the [SECURITY](./SECURITY.md) policy. This repository is subject to a
-bug bounty program per the terms outlined in the aforementioned policy.
+For any security-related concerns, please refer to the [SECURITY](./SECURITY.md) policy.
 
 ## Contributing
 

SECURITY.md

@@ -2,8 +2,10 @@
 
 Ensuring the security of the Sablier Protocol is our utmost priority. We have dedicated significant efforts towards the
 design and testing of the protocol to guarantee its safety and reliability. However, we are aware that security is a
-continuous process. If you believe you have found a security vulnerability, please read the
-[Bug Bounty Program](https://sablier.notion.site/bug-bounty) and share a report privately with us.
+continuous process. If you believe you have found a security vulnerability, please report it privately by emailing
+[contact@sablier.com](mailto:contact@sablier.com).
+
+For the list of past audits, see the [sablier-labs/audits](https://github.com/sablier-labs/audits) repository.
 
 ## Protocol Assumptions