# Security For Accounts 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: 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://documentation.opencollective.com/advanced/security-for-accounts.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.