Website Or Checkout Bug
Include the page URL, steps taken, expected result, actual result, time, device, browser, and a screenshot with private data removed.
Site Support
Report A Website Or Security Issue
Use the correct reporting route so ordinary website problems and potential security vulnerabilities receive the appropriate review. Never include passwords, card details, private keys, or unnecessary personal data.
Accessibility Problem
Describe the blocked task, assistive technology, browser, device, page, and the control or content that could not be used.
Security Concern
Provide a minimal reproducible description and impact. Do not access, alter, download, or expose other people’s information.
Responsible Reporting
Security Boundaries
- Do not use denial-of-service testing, automated high-volume scanning, social engineering, phishing, or physical attacks.
- Do not access accounts, orders, messages, payment information, or personal data that do not belong to you.
- Stop testing once you can demonstrate the issue safely and report it with the smallest necessary evidence.
- Allow a reasonable period for investigation before sharing details publicly.
- This reporting page does not promise a reward, bounty, safe-harbour determination, or response deadline.
Quick Answers
Frequently Asked Questions
Should payment details be included in a screenshot?
No. Redact card numbers, security codes, passwords, session tokens, addresses, and other information not required to understand the issue.
Where do I report an account login concern?
Select Security Report if you suspect unauthorized access; otherwise select Account Support for an ordinary login or profile problem.
Send A Clear Report
One concise report with reproducible steps is more useful than repeated messages or aggressive testing.
