Fohrkast » Trust

Report a security issue

Version 2026-10-26 Updated 26 Oct 2026

How to report a security issue in Fohrkast, what is in scope, the rules for testing, and what happens after a report.

On this page

  1. 01 In scope
  2. 02 Out of scope
  3. 03 Rules
  4. 04 How to report
  5. 05 What happens next
  6. 06 Rewards
  7. 07 Good faith
Contents 7 sections
  1. 01 In scope
  2. 02 Out of scope
  3. 03 Rules
  4. 04 How to report
  5. 05 What happens next
  6. 06 Rewards
  7. 07 Good faith

01 In scope

  • » fohrkast.com and www.fohrkast.com.
  • » The signed in app.
  • » The public API (fohrkast.com/help/api).
  • » The scanner releases Fohrkast publishes.

02 Out of scope

  • » demo.fohrkast.com, which shows invented companies.
  • » staging.fohrkast.com.
  • » Status pages.
  • » Third parties, such as Amazon Web Services, Google and Razorpay.
  • » Findings that need physical access to a device, or a stolen device.

03 Rules

  • » Use only accounts the researcher owns.
  • » Reach no more data than needed to show the issue. On reaching personal data of anyone else, stop and report at once, and keep none of it.
  • » No denial of service, no high volume automated scanning, no spam, and no social engineering of Fohrkast staff or customers.
  • » Allow 90 days before any public disclosure, or less once the issue is fixed and the date agreed.

04 How to report

Write to tech@fohrkast.com with the URL or feature affected, the steps that reproduce the issue, the impact, and a contact for follow up.

05 What happens next

  • » Reports are acknowledged within 3 working days.
  • » Updates follow until the issue is fixed.
  • » Credit on this page for the researcher, if wanted.

06 Rewards

Fohrkast runs no paid bug bounty at present.

07 Good faith

Fohrkast will not pursue legal action against research done in good faith within these rules.

Sections and rules cited are of the Digital Personal Data Protection Act 2023 and the DPDP Rules 2025 unless stated.