From ec646e5193e0fa40fce475623b75370b88229996 Mon Sep 17 00:00:00 2001
From: GitHub Action <github-action@users.noreply.github.com>
Date: Tue, 16 May 2023 12:39:12 +0000
Subject: [PATCH] Update content of files

---
 data/web/core.telegram.org/bug-bounty.html | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/data/web/core.telegram.org/bug-bounty.html b/data/web/core.telegram.org/bug-bounty.html
index 573ffe0010..4cf5ba5f91 100644
--- a/data/web/core.telegram.org/bug-bounty.html
+++ b/data/web/core.telegram.org/bug-bounty.html
@@ -110,6 +110,8 @@
 
 ## Additional details:
 [Tools used, preconditions, media proof, session and timestamps as needed]</code></pre>
+<h5><a class="anchor" name="third-party-bug-bounty-platforms" href="#third-party-bug-bounty-platforms"><i class="anchor-icon"></i></a>Third-Party Bug Bounty Platforms</h5>
+<p>We ask for all submissions and correspondence to be sent <strong>directly</strong> to <a href="mailto:security@telegram.org">security@telegram.org</a> – Telegram currently does <strong>not</strong> maintain a presence on third-party bug bounty platforms or services.</p>
 <h3><a class="anchor" name="prize" href="#prize"><i class="anchor-icon"></i></a>Prize</h3>
 <p>Valid reports that result in a change of code or configuration are eligible for bounties, ranging from <strong>$100</strong> to <strong>$100,000</strong> or more, depending on the severity of the issue. We reserve the right to ultimately determine both the validity and the appropriate compensation for each report at our discretion.</p>
 <hr>