Security and issue reporting

Security and issue reporting Report account, data-access and product-security issues through the appropriate channels. Legal & policies Contact us Protect research through everyd

Security and issue reporting Report account, data-access and product-security issues through the appropriate channels. Legal & policies Contact us Protect research through everyday practice. Privacy and information protection illustration At a glance Careful account, sharing and equipment practices help reduce mistakes and exposure. Clear records also help investigate unexpected behavior. This page covers everyday practices and issue reporting. For equipment in use, follow manual safety guidance and avoid enlarging an issue while investigating. Pause suspicious actions and retain the discovery time and necessary evidence. Limit further impact Describe the entry, version, steps and impact while hiding credentials and personal data. Provide a minimal reproduction Use the confirmed channel and avoid distributing unverified sensitive details. Help with the investigation Prepare in three steps 1. Account and data security Stop the relevant activity, keep necessary evidence and contact us about unusual sign-ins, permission errors, unintended sharing or suspected fraud. Never send passwords, verification codes or full payment credentials to another person. 2. Vulnerabilities and product issues Include the affected page or product version, a description, the minimum necessary reproduction steps and contact details. Do not access or copy other people’s data, increase impact or test services without authorization. Arrange a suitable secure channel before sending sensitive evidence. 3. Handling and communication We review reports, coordinate handling according to the issue and communicate through the provided contact channel. This page does not establish a bug-bounty program or promise a reward. General technical faults can also be submitted through customer support. 4. Check accounts, sharing and equipment Use strong, distinct passwords and avoid leaving sessions open on shared computers. Verify unusual sign-in or payment messages through known entry points. Review shared links and departing members’ access, redact tokens and research identifiers from logs, and follow equipment update guidance using trusted installers. 5. What to include in a report Include the affected page, feature or model, discovery time, version, reproduction steps and observed impact. Prefer redacted screenshots and minimal examples. Do not include passwords, private keys or full access tokens, access others’ information, continue scanning or disrupt services to gather evidence. Use the contact page for faults or suspected security issues. Details Never send passwords, verification codes, private keys or full tokens. References and a minimal reproduction generally support investigation. Should I include my password? Use the contact page, distinguish safety concerns from functional faults and include the model and serial number. Can I report an equipment fault here? First report access, personal-data or exploitable details through the confirmed channel and limit sensitive distribution. Should I publish full details in a community? Questions you may have Report an issue Read the full details Privacy requests Read the full details Product safety Read the full details Related pages