REPORT SECURITY ISSUES

1. You give us reasonable time to review and repair a haul 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 an honest faith effort to avoid privacy violations and disruptions to others, including (but not limited to) destruction of knowledge and interruption or degradation of our services.
4. You do not exploit a security issue you discover for any reason. (This includes demonstrating additional risk, like attempted compromise of sensitive company data or trying to hunt out additional issues.)
5. You do not violate the other applicable laws or regulations.

1. Adhere to our fundamentals (see above).
2. Report a security bug: that's , identify a vulnerability in our services or infrastructure which creates a security or privacy risk. (Note that amiactive.shop ultimately determines the danger of a drag , which many bugs aren't security issues.)
3. Submit your report via our security center. Please don't contact employees.
4. If you inadvertently cause a privacy violation or disruption (such as accessing account data, service configurations, or other confidential information) while investigating a haul , inform disclose this in your report.
5. We investigate and answer all valid reports. because of the number of reports we receive, though, we prioritize evaluations supported risk and other factors, and it's going to take a fast time before you receive a reply.
6. We reserve the proper to publish reports.

1. Please provide detailed reports with reproducible steps. If the report isn't detailed enough to breed the matter , the matter won't be eligible for bounty.
2. When duplicates occur, we award the primary report that we'll completely reproduce.
3. Multiple vulnerabilities caused by one underlying issue are becoming to be awarded one bounty.
4. We determine bounty reward supported a selection of things , including (but not limited to) impact, simple exploitation, and quality of the report. We specifically note the bounty rewards, these are listed under.
5. Amounts below are the utmost we'll pay per level. We aim to be fair, all reward amounts are at our discretion. Critical severity Vulnerabilities ($200): Vulnerabilities that cause a privilege escalation on the platform from unprivileged to admin, allows remote code execution, financial theft, etc.

• Example:

1. Remote Code Execution
2. Remote Shell/Command Execution
3. Vertical Authentication bypass
4. SQL Injection that leaks targeted data
5. Get full access to accounts

1. Lateral authentication bypass
2. Disclosure of important information within the corporate
3. Stored XSS for a further user
4. Local file inclusion
5. Insecure handling of authentication cookies

1. Common logic design flaws and business process defects
2. Insecure object of the verb References

1. Open redirect
2. Reflective XSS
3. Low sensitivity Information leaks

• Customer Support 24/7

 Email: support@amiactive.shop

Phone: (325) 283-7435