> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/get-started/security/data-security-at-anedot.md). # Data Security At Anedot How Anedot protects fundraising data: SOC 2 and PCI compliance, TLS encryption, privacy practices, and who owns supporter and organization information. How Anedot protects data: SOC 2 and PCI compliance, TLS encryption, privacy, and ownership. ## Secure By Design Anedot is **SOC 2** compliant and **PCI** compliant, and uses **TLS** encryption for data in transit. Cardholder data is never exposed to staff or users—payment information is encrypted in the browser before transmission. Security measures include: * Ongoing internal code and infrastructure audits * Monthly reviews by an external security analyst * Quarterly scans by an independent security firm ## PCI Compliance Guidelines (Organization Side) * Never write down, email, or text credit card numbers * If card data is recorded, destroy it immediately after processing Learn more: [PCI Compliance FAQ](https://www.pcisecuritystandards.org/faqs/all/) ## SOC 2 Compliance Anedot maintains an active **SOC 2 Type I** report. To request a copy, [contact Support](https://www.anedot.com/getsupport). ## Privacy And Data Ownership * Anedot does not sell or share personal information * Personally identifiable information (PII) is fully owned by the organization that collects it * Anedot is a direct payment processor—not a reseller—so organizations retain control over payment data * Data-sharing policies of fundraising organizations and integration partners are independent of Anedot—consult them directly ## Legal And Privacy Terms * [Terms of Service](https://www.anedot.com/terms-for-fundraising-organizations) * [Privacy Policy](https://www.anedot.com/privacy) --- # 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://docs.anedot.com/get-started/security/data-security-at-anedot.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.