> 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/donor-support/faq/donor-security-and-account-safety.md). # Donor Security and Account Safety Anedot protects your donation information with industry-standard encryption, PCI compliance, and passwordless login options. This guide is written for donors. Anedot protects your donation information with industry-standard encryption, PCI compliance, and passwordless login options. ### Financial Data * All forms use TLS encryption. * Your financial data is used to process transactions and is not shared with additional third parties. * Transactions are processed under Payment Card Industry (PCI) Level 1 compliance. * If you save payment data for future gifts, it is stored in a PCI Level 1 compliant facility. ### Personal Data * Anedot never sells or shares your personal information. * Your personal data is used to process transactions and is not shared with additional third parties. ### Secure Login Anedot uses passwordless login. Instead of a password, you sign in with a one-time code sent to your email. Enter the email you use for donations, check your inbox for the code, and enter it on the login screen. Because no password is stored for your Donor Account, this reduces the risk of stolen or reused credentials. #### Passkeys For faster, more secure sign-in, set up a passkey from the **Security** tab in your Donor Account. A passkey uses your device's built-in security—such as Face ID, Touch ID, a fingerprint reader, or a hardware security key. When you add a passkey, your device stores a unique cryptographic key used only for your Anedot account. Next time, you can authenticate with your device instead of an email code—faster and more phishing-resistant. --- # 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/donor-support/faq/donor-security-and-account-safety.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.