# Security ### Brand promise Keeping users safe and secure is a top priority for us at social.plus. We welcome the contribution of external security researchers. ### Scope If you believe you’ve found a security issue in any software, service, or website governed by social.plus, we encourage you to notify us. Projects governed by social.plus can sometimes allow unsafe things by design. This unsafe behavior should be explicitly documented and, if it is, is not considered a security issue. There are no hard and fast rules to determine if a bug is worth reporting as a security issue or a “regular” issue. When in doubt, please do send us a report. ### How to submit a report Security issues can be reported by sending an email to , which will go to all relevant team members. The team will acknowledge your email within 48 hours and you will receive a more detailed response within a week. We will create a security meeting to discuss this internally, and if/when needed, invite you to discuss the issue with us. ### Safe harbor Amity supports safe harbor for security researchers who: * Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our services * Only interact with accounts you own or with explicit permission of the account holder. If you do encounter Personally Identifiable Information (PII) contact us immediately, do not proceed with access, and immediately purge any local information * Provide us with a reasonable amount of time to resolve vulnerabilities before any disclosure to the public or a third-party. * We will consider activities conducted consistent with this policy to constitute “authorized” conduct and will not pursue civil action or initiate a complaint to law enforcement. We will help to the extent we can if legal action is initiated by a third party against you Please submit a report to us before engaging in conduct that may be inconsistent with or unaddressed by this policy. ### Preferences * Please provide detailed reports with reproducible steps and a clearly defined impact. * Submit one vulnerability per report. * Social engineering (such as phishing, vishing, and smishing) is prohibited. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.social.plus/miscellaneous/support/security.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.