Back to Bug Bounty Program

Program Rules & Legal Terms

Last updated: December 2024

This document outlines the complete rules, guidelines, and legal terms governing participation in the SindrX Bug Bounty Program. By participating, you agree to abide by all terms herein.

1. Eligibility Requirements

To participate in the SindrX Bug Bounty Program, you must meet the following requirements:

Age Requirement

You must be at least 18 years of age, or have verifiable parental or legal guardian consent if you are between 14-17 years old. Participants under 14 are not eligible.

No Affiliation

You must not be a current or former (within the last 12 months) employee, contractor, or consultant of SindrX or any of its subsidiaries. Immediate family members of such persons are also excluded.

Legal Compliance

You must not reside in a country under U.S. sanctions (including but not limited to: Cuba, Iran, North Korea, Syria, and the Crimea region). You must be legally permitted to participate in security research activities in your jurisdiction.

Tax Compliance

You must be able to provide valid tax documentation if required. For U.S. persons, this includes a W-9 form. For non-U.S. persons, a W-8BEN or equivalent may be required for payments exceeding $600 USD.

2. Program Scope

In-Scope Assets

AssetTypePriority
*.sindrx.comWeb ApplicationCritical
api.sindrx.comREST APICritical
SindrX iOS AppMobile ApplicationHigh
SindrX Android AppMobile ApplicationHigh
Authentication SystemsIdentity & AccessCritical

Qualifying Vulnerability Types

Remote Code Execution (RCE)
SQL Injection / NoSQL Injection
Authentication Bypass
Authorization Bypass / Privilege Escalation
Cross-Site Scripting (XSS) - Stored
Cross-Site Request Forgery (CSRF) - Sensitive Actions
Server-Side Request Forgery (SSRF)
Insecure Direct Object References (IDOR)
XML External Entity (XXE) Processing
Directory Traversal / Path Traversal
Sensitive Data Exposure
Security Misconfiguration with Impact
Cryptographic Failures
Business Logic Vulnerabilities

Out-of-Scope Assets

  • Third-party services, plugins, or integrations not owned by SindrX
  • Any asset not explicitly listed in the in-scope section
  • blog.sindrx.com (managed by third-party)
  • status.sindrx.com (managed by third-party)
  • Corporate email and internal systems
  • Physical security of SindrX offices or data centers

Non-Qualifying Issues

  • Missing security headers without demonstrated impact
  • Self-XSS (XSS that only affects the attacker)
  • CSRF on non-sensitive functionality (logout, public actions)
  • Clickjacking on pages with no sensitive actions
  • Version disclosure or banner grabbing
  • Missing rate limiting without demonstrated impact
  • SPF/DKIM/DMARC issues without mail spoofing demonstration
  • SSL/TLS best practices without exploit
  • Verbose error messages without sensitive data
  • Open redirects without additional impact
  • Theoretical vulnerabilities without proof of concept
  • Issues requiring physical access to a user's device
  • Social engineering attacks against SindrX employees

3. Rules of Engagement

All security research must be conducted in accordance with the following rules. Violation of these rules may result in immediate disqualification, forfeiture of rewards, and potential legal action.

Minimal Impact Testing

Only access data or systems to the extent necessary to confirm the vulnerability exists. Do not access, modify, delete, or exfiltrate any data beyond what is strictly necessary for demonstration.

No Privacy Violations

Do not access, view, copy, or store personal data of any SindrX user. If you inadvertently encounter personal data, stop immediately, do not save it, and report it to us.

No Service Disruption

Do not perform any testing that could degrade, disrupt, or deny service to SindrX or its users. This includes but is not limited to: DoS/DDoS attacks, resource exhaustion, and automated scanning at high rates.

Use Test Accounts Only

Only test against accounts you own or have explicit permission to test. Create your own test accounts for research purposes. Never attempt to access other users' accounts.

Prompt Reporting

Report vulnerabilities to SindrX as soon as reasonably possible after discovery, ideally within 24 hours. Do not attempt to exploit the vulnerability beyond initial verification.

Confidentiality

Do not publicly disclose any vulnerability details before receiving explicit written authorization from SindrX. Coordinated disclosure is typically permitted 90 days after the fix is deployed.

Good Faith

Act in good faith throughout your research. If you are uncertain whether an action is permitted, ask us first at security@sindrx.com before proceeding.

4. Prohibited Activities

The following activities are strictly prohibited and will result in immediate disqualification, forfeiture of any pending rewards, and may result in legal action:

  • Accessing or attempting to access data that does not belong to you
  • Exfiltrating, copying, or storing any user data, credentials, or sensitive information
  • Performing denial of service attacks or any testing that impacts service availability
  • Conducting social engineering, phishing, or physical attacks against SindrX or its employees
  • Accessing SindrX systems using stolen credentials or session tokens
  • Installing backdoors, malware, or persistent access mechanisms
  • Testing on production systems with real user data without authorization
  • Automated vulnerability scanning without prior written approval
  • Public disclosure of vulnerabilities without authorization
  • Selling or transferring vulnerability information to third parties
  • Threatening SindrX or its employees in any way
  • Any activity that violates applicable laws or regulations

5. Reporting Guidelines

High-quality reports help us understand and fix vulnerabilities quickly. Please include the following information in your report:

Required Information

  • Clear, descriptive title summarizing the vulnerability
  • Affected asset(s) - specific URLs, endpoints, or applications
  • Vulnerability type and your severity assessment
  • Detailed description of the vulnerability and its root cause
  • Step-by-step reproduction instructions that our team can follow
  • Proof of concept (screenshots, videos, code snippets, HTTP requests)
  • Impact assessment - what could an attacker do with this vulnerability?
  • Your contact information for follow-up questions

Optional (But Appreciated)

  • Suggested remediation or fix recommendations
  • CVSS score calculation with justification
  • References to similar vulnerabilities (CVEs, blog posts)
  • Working exploit code (responsibly disclosed)
  • Your PGP public key for encrypted communication

6. Reward Structure

SeverityCVSS RangeReward Range
Critical9.0 - 10.0$10,000 - $15,000
High7.0 - 8.9$5,000 - $10,000
Medium4.0 - 6.9$1,000 - $5,000
Low0.1 - 3.9$100 - $1,000

Bonus Multipliers

+25%First report of a new vulnerability type
+25%Exceptionally detailed and well-written report
+50%Working patch or fix included with report
+100%Chained vulnerabilities demonstrating significant impact

Payment Terms

  • • Payments are processed within 14 business days of vulnerability validation
  • • Available payment methods: Bank transfer (ACH/Wire), PayPal, Cryptocurrency (BTC/ETH)
  • • Minimum payout threshold: $100 USD
  • • Tax documentation may be required for payments exceeding $600 USD
  • • SindrX reserves the right to adjust rewards based on actual impact and quality of report

7. Safe Harbor Policy

SindrX is committed to working with security researchers in a constructive, collaborative manner. We believe that security research conducted in good faith should be protected.

Our Commitments to You

  • We will not pursue legal action against researchers who follow these program rules
  • We will not report researchers to law enforcement for good-faith security research
  • We will work with you to understand and resolve issues quickly
  • We will recognize your contribution publicly (with your permission)
  • We will provide a reasonable timeline for fixes and keep you informed
  • We will pay bounties promptly and fairly based on severity and impact

Conditions for Safe Harbor

Safe Harbor protections apply when the researcher:

  • • Complies with all rules and guidelines in this document
  • • Reports vulnerabilities promptly and does not exploit them
  • • Does not access or exfiltrate user data
  • • Does not disrupt SindrX services or operations
  • • Acts in good faith throughout the research process

9. Confidentiality

All vulnerability reports and related communications are considered confidential information. By participating in this program, you agree to:

  • Not disclose vulnerability details to any third party without SindrX's written consent
  • Not publish vulnerability details publicly until authorized by SindrX
  • Destroy any data accessed during testing after the vulnerability is resolved
  • Coordinate disclosure timing with SindrX (typically 90 days after fix deployment)

SindrX may publicly acknowledge your contribution (with your consent) and may publish sanitized details of resolved vulnerabilities in security advisories.

10. Policy Changes

SindrX reserves the right to modify these program rules at any time. Changes will be effective immediately upon posting to this page. The "Last updated" date at the top of this document indicates when the most recent changes were made.

Significant changes to scope, rewards, or legal terms will be announced via email to active researchers and on our security blog. Your continued participation in the program after changes are posted constitutes acceptance of the modified terms.

Reports submitted before a policy change will be evaluated under the terms in effect at the time of submission.

Thank You for Helping Us Stay Secure

Security researchers play a vital role in keeping SindrX and our users safe. We appreciate your dedication to responsible disclosure and look forward to working with you.