1. What Is Principles of the eDonor Bill of Rights?
The Principles of the eDonor Bill of Rights are nine ethical expectations for online fundraising, published by the Association of Fundraising Professionals (AFP). They supplement the original Donor Bill of Rights with safeguards for electronic giving. The “e” refers to electronic; it is not an acronym.
For nonprofit organizations, the framework offers a practical way to examine whether digital fundraising respects donors throughout the giving process. The executive question is specific: can someone understand who is requesting a gift, where the money goes, how their information is handled, and what communications they are agreeing to receive?
This is a fundraising ethics and stewardship framework, not a revenue-optimization model. Consultants can translate it into an evidence-based review of donation channels, donor records, platform relationships, and internal responsibilities.
2. Origin and Background
Origin: AFP publishes and promotes the eDonor principles; its current official page does not establish their first-publication date. The underlying Donor Bill of Rights dates to 1993 and was created by AFP, the Association for Healthcare Philanthropy, the Council for Advancement and Support of Education, and the Giving Institute.
The electronic extension addresses concerns arising from Internet charitable giving. It complements, rather than replaces, the earlier document. That original document covers broader stewardship expectations, including appropriate gift use, financial transparency, acknowledgment, confidentiality, and truthful answers to donors’ questions.
For executive teams, the useful adaptation is to move from publishing a statement of principles to testing actual behavior. A website promise should have a corresponding operational control and an accountable owner.
3. How Principles of the eDonor Bill of Rights Works
For management purposes, treat each principle as an acceptance criterion. Ask three questions: what should the donor experience, what process makes that experience possible, and what evidence demonstrates that the process works?
The nine expectations
- Organizational identity: Immediately disclose the solicitor’s identity, status, mission, and purpose.
- Alternative contact: Offer an accessible contact route beyond websites and email.
- Authentic symbols: Keep third-party endorsements and identifying symbols accurate, current, justified, and explained.
- Deductibility: Explain whether gifts qualify for deductions and applicable limits.
- Protected transactions: Safeguard online payments and donors’ personal information.
- Gift routing: Explain whether contributions reach the charity directly or through intermediaries.
- Privacy disclosure: Make information collection and use understandable through an accessible policy.
- List-sharing choices: Clearly explain opportunities to decline list sale, rental, sharing, or transfer.
- Communication permission: Obtain opt-in before unsolicited communications or solicitations.
Translate expectations into observable controls
Use giving journeys—not donor wealth tiers—as the primary units of analysis. Review website donations, recurring gifts, peer-to-peer campaigns, and external fundraising platforms separately. A satisfactory experience on the main donation page should not establish confidence in every other channel.
Build an assessment matrix with principles as rows and channels as columns. For each intersection, record evidence, gaps, ownership, and corrective actions. Labels such as “demonstrated,” “partially demonstrated,” and “not demonstrated” can support discussion. This matrix is a practical adaptation, not an AFP-prescribed scoring system.
Test list-sharing choices separately from permission to receive fundraising messages. Within the donor database, consider recording communication purpose, channel, date, and source of permission rather than relying on one ambiguous “contact allowed” field.
4. When to Use Principles of the eDonor Bill of Rights
Use the framework before launching a digital campaign, replacing a fundraising platform, introducing recurring giving, or connecting donor systems. It is particularly useful when development, finance, communications, and technology teams have divided responsibilities without testing the complete donor experience.
The minimum useful inputs are donation forms, privacy notices, receipts, communication preferences, platform contracts, gift-transfer records, and relevant staff interviews. Include a donor-perspective walkthrough: internal familiarity can conceal confusing language or inaccessible contact options.
Validate U.S. deduction statements against recipient eligibility and applicable tax rules. Do not assume that describing an organization as nonprofit establishes the deductibility of every payment, particularly where donors receive benefits.
A targeted workshop can identify gaps, but assurance requires operational testing. The framework is not suitable for choosing program priorities or predicting fundraising returns. It can mislead when teams assess written policies without examining system settings, transfers, or actual communications.
5. How to Apply Principles of the eDonor Bill of Rights: Step-by-Step
Clarify the decision and scope. Define whether the review supports campaign approval, platform selection, or remediation. Specify legal entities, countries, channels, campaign types, and the next operating period. Include outsourced activities rather than stopping at the organization’s website.
Gather evidence and trace the flows. Collect forms, notices, contracts, receipts, preference records, and complaints. Trace both money and information from donation submission to settlement, acknowledgment, database entry, and subsequent appeals. Identify assumptions that require vendor confirmation.
Define the giving journeys. Separate materially different processes: direct gifts, recurring gifts, event-linked contributions, and gifts through intermediary charities. Select representative journeys, including donors who decline appeals or request anonymity.
Construct the assessment matrix. Evaluate all nine principles for each journey. Attach screenshots, test results, documents, and named owners. Distinguish missing evidence from confirmed failure; uncertainty should remain visible rather than becoming an assumed pass.
Interpret gaps by donor consequence. Prioritize misleading recipient information, unsupported deduction claims, exposed information, and unwanted solicitation. Avoid averaging away serious weaknesses. A strong identity disclosure does not compensate for a failed permission control.
Translate findings into implementation. Assign actions across development, finance, technology, and communications. Where preferences disappear between fundraising forms and appeal systems, CRM process optimization can address database workflows, integration rules, and suppression testing. CRM means customer relationship management; here, the records concern donors.
Test alternative conditions. Repeat tests for mobile devices, declined marketing permission, changed preferences, recurring transactions, and delayed transfers. Ask whether conclusions survive a platform change or staff absence. Use test records rather than unnecessary exposure of real donor information.
Align owners and retest. Review findings jointly, resolve conflicting interpretations, and agree closure evidence. Development should coordinate stewardship, while finance validates gift handling and technical owners verify system controls. Retest after material changes and review unresolved issues regularly.
For the security principle, supplement donor-facing inspection with technical checks. Consider multi-factor authentication for administrative accounts, access appropriate to job responsibilities, and removal of access when staff leave. These are implementation measures, not additional eDonor principles.
6. Example: Principles of the eDonor Bill of Rights in Action
Fictional example: Harbor Community Food Network is preparing a year-end appeal. It accepts direct website gifts, monthly contributions, and donations through an external giving platform. Its development director wants to expand fundraising without creating inconsistent donor experiences.
The team selects the eDonor principles because its immediate concern is stewardship across these three journeys—not which audience will generate the most revenue. It reviews forms, receipts, vendor agreements, preference records, and settlement reports.
The review reveals that a direct donor who declines fundraising emails is nevertheless added to an automated appeal sequence. The external platform’s campaign page also leaves unclear which entity initially receives the gift. Separately, the website displays an outdated endorsement badge.
The organization pauses the affected email automation, corrects its integration logic, clarifies recipient and transfer information, and removes the badge pending verification. Finance reconciles platform transfers; development owns preference testing; communications owns disclosure accuracy.
The board receives a concise report showing outstanding gaps and closure evidence. Success is defined by verified gift routing, permissions that survive system transfers, and accurate disclosures—not by a promised increase in donations.
7. Strengths and Limitations
Strengths
- Donor-centered clarity: The principles focus discussion on what a supporter should understand and control.
- Cross-functional usefulness: An assessment can connect fundraising promises with finance processes, database behavior, and vendor responsibilities.
- Practical prioritization: Evidence-based review makes stewardship gaps visible before campaign expansion.
Where findings reveal unclear board oversight, board advisory support can help establish reporting expectations, committee responsibilities, and escalation thresholds. Management should retain responsibility for daily implementation.
Limitations
The framework does not prescribe a complete cybersecurity architecture, legal compliance program, vendor contract, or incident-response process. Nor does it assess program effectiveness, beneficiary outcomes, or whether fundraising costs are justified.
Third-party giving deserves particular scrutiny. A platform charity may receive and hold donations, issue receipts, and subsequently send funds to the intended organization. Consequently, review the actual recipient, transfer arrangements, and responsibilities rather than treating every provider as merely a payment processor.
Finally, an assessment is only as credible as its evidence. Policy statements and vendor assurances should inform testing, not replace it.
8. Common Pitfalls and How to Avoid Them
- Posting instead of implementing: A published commitment proves little about practice. Pair each promise with a control, owner, and test.
- Confusing permissions: A preference to avoid shared lists should not be treated as equivalent to permission for appeals. Keep the decisions separately identifiable.
- Ignoring intermediaries: Reviewing only the charity’s website leaves external journeys unexamined. Include recipient disclosures, transfer records, and platform communications.
- Testing only happy paths: Successful donations conceal failures involving changed preferences or recurring gifts. Test exceptions deliberately.
- Promising absolute confidentiality: Avoid language that operational arrangements cannot support. Review actual disclosures, vendor access, and legitimate recordkeeping needs before drafting promises.
- Optimizing away safeguards: Do not remove clarity or permission choices simply to shorten checkout. Test usability within stewardship boundaries.
- Closing issues without evidence: A configuration change is not proof of resolution. Retest the journey and preserve the result.
9. How Principles of the eDonor Bill of Rights Relates to Other Frameworks
Before: Donor journey mapping
Start by mapping discovery, donation, acknowledgment, preference changes, and later appeals. Use that map to establish where each principle should be tested. Mapping can reveal confusing experiences; the eDonor principles provide the ethical questions against which to examine them.
Alongside: The original Donor Bill of Rights
Use both documents together. The original addresses broader stewardship, including intended gift use and organizational transparency; the electronic extension sharpens expectations around online giving. Prefer the original as the starting point for an organization-wide stewardship policy, then apply the eDonor principles to digital channels.
After: Cybersecurity risk assessment
Where the review identifies security uncertainty, commission a deeper risk assessment rather than stretching this framework into a technical audit. NIST’s Small Business Information Security guidance offers a supporting reference for organizations needing a more structured security review.
10. Key Takeaways
- Use the principles to evaluate digital donor stewardship, not forecast fundraising returns.
- Assess complete giving journeys, including outsourced channels.
- Separate disclosures, permissions, system controls, and supporting evidence.
- Do not let satisfactory results conceal one serious donor-protection failure.
- Turn findings into owned actions, then verify their effectiveness.
11. FAQs About Principles of the eDonor Bill of Rights
Is the eDonor Bill of Rights legally binding?
It is ethical guidance, not a standalone statute or a substitute for compliance review. Treat applicable fundraising, privacy, and tax obligations separately, with qualified advice where needed.
Does making a donation provide permission for future appeals?
Do not use the donation itself as your operational evidence of opt-in. Capture a clear communication choice, preserve its source, and test that subsequent appeal systems honor it.
What should a small nonprofit do first?
Walk through its main donation journey, confirm recipient information, check contact options, and test a donor who declines appeals. Correct verified gaps before purchasing additional technology.
Can a nonprofit delegate the review to its fundraising platform?
The platform can provide evidence about its own processes. The nonprofit should still assess its complete donor journey, including internal database imports, acknowledgments, appeals, and reconciliation. Assign responsibilities explicitly and verify the handoffs.
