Report Security Issues

If you’ve found a security vulnerability on keeptee.com, we encourage you to message us immediately. We’ll review all legitimate vulnerability reports and do our utmost to quickly resolve the matter. Before you report, please review this document, including our fundamentals, bounty program, reward guidelines, and what shouldn’t be reported

Fundamentals

If you follow the principles below when reporting a security issue to keeptee.com, we will not initiate a lawsuit or law enforcement investigation against you in response to your report. We ask that: 1. You give us reasonable time to review and resolve the issue you report before making public any information about the report or sharing such information with others. 2. You don’t interact with a private account (which includes modifying or accessing data from the account) if the account owner has not consented to such actions. 3. You make a good faith effort to avoid privacy violations and disruptions to others, including (but not limited to) the destruction of data and the interruption or degradation of our services. 4. You do not exploit a security issue you discover for any reason. (This includes demonstrating additional risk, such as the attempted compromise of sensitive company data or trying to find additional issues.) 5. You do not violate any other applicable laws or regulations.

BOUNTY PROGRAM

We recognize and reward security researchers who help us keep people safe by reporting vulnerabilities in our services. Monetary bounties for such reports are entirely at keeptee.com's discretion, based on risk, impact, and other factors. To potentially qualify for a bounty, you must meet the following requirements: 1. Adhere to our fundamentals (see above). 2. Report a security bug: that is, identify a vulnerability in our services or infrastructure which creates a security or privacy risk. (Note that keeptee.com ultimately determines the risk of an issue, and many bugs are not security issues.) 3. Submit your report via email to our support team. Please don't contact employees directly. 4. If you inadvertently cause a privacy violation or disruption (such as accessing account data, service configurations, or other confidential information) while investigating an issue, please disclose this in your report. 5. We investigate and respond to all valid reports. Due to the volume of reports we receive, however, we prioritize evaluations based on risk and other factors, and it may take some time before you receive a reply. 6. We reserve the right to publish reports.

REWARDS

Our rewards are based on the impact of a vulnerability. We will update the program over time based on feedback, so please give us feedback on any area of the program you think we can improve on. 1. Please provide detailed reports with reproducible steps. If the report isn’t detailed enough to reproduce the issue, the issue won’t be eligible for a bounty. 2. When duplicates occur, we award the first report that we can completely reproduce. 3. Multiple vulnerabilities caused by one underlying issue will be awarded a single bounty. 4. We determine the bounty reward based on a variety of factors, including (but not limited to) impact, ease of exploitation, and quality of the report. The specific bounty rewards are listed below. 5. Amounts below are the maximum we’ll pay per level. We aim to be fair, and all reward amounts are at our discretion.

Critical Severity Vulnerabilities ($200):

Vulnerabilities that cause a privilege escalation on the platform from unprivileged to admin, allow remote code execution, financial theft, etc. Examples: • Remote Code Execution • Remote Shell/Command Execution • Vertical Authentication bypass • SQL Injection that leaks targeted data • Get full access to accounts

High Severity Vulnerabilities ($100):

Vulnerabilities that affect the safety of the platform including the processes it supports. Examples: • Lateral authentication bypass • Disclosure of important company information • Stored XSS for another user • Local file inclusion • Insecure handling of authentication cookies

Medium Severity Vulnerabilities ($50):

Vulnerabilities that affect multiple users, and require little or no user interaction to trigger. Examples: • Common logic design flaws and business process defects • Insecure Direct Object References (IDOR)

Low Severity Vulnerabilities:

Issues that affect singular users and require interaction or significant prerequisites (MITM) to trigger. Examples: • Open redirect • Reflective XSS • Low sensitivity information leaks

Customer Contact:

• Phone: +1 (904) 595-7296 • Email: [email protected] • Address: 9300 S. Dadeland Blvd. Suite 600, Miami, Fl 33156, United States • Support Hours: 09:00 AM - 5:00 PM (EST), Mon - Fri