> For the complete documentation index, see [llms.txt](https://documentation.opencollective.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.opencollective.com/advanced/security-for-accounts.md). # Security For Accounts We maintain the highest security standards to protect individuals and groups at Open Collectives. Learn more about security, and how you can help Security is hugely important to us here at Open Collective. We maintain the highest security practices to make sure that your individual and Collectives information is protected. We do not store credit card details, so they cannot be lost if our systems are compromised. Any details you supply are secured by Stripe, a provider trusted by many leading companies worldwide. [Learn more](https://stripe.com/docs/security/stripe) about Stripe’s security. We also invite and pay security researchers to test the resilience of our system and suggest improvements, in line with our security bounty policy. [You can find more information about our security policy on GitHub.](https://github.com/opencollective/opencollective/security/policy) If you find an error, don't hesitate to contact our security team at . Please do not disclose the issue publicly before we have resolved it. ### Find out more Discover how you can improve the security of your account to protect your information.

Learn more about how we protect your account

We recommend setting up 2FA to add an extra layer of security.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://documentation.opencollective.com/advanced/security-for-accounts.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.