A Minneapolis story
The Tuesday the donor list almost went out by text
the executive director of a 12-person nonprofit in the North Loop
It is a Tuesday in January, fourteen below at the bus stop, and the executive director of a North Loop nonprofit is at a funder's office in Saint Paul with her phone on silent. Back at the office the development director is finishing the year-end donor file: 4,800 names, home addresses, giving history, and the card numbers from the gala that never got deleted. It lives in a spreadsheet.
At 10:52 a text arrives on the development director's phone. It uses the executive director's name and reads the way she writes: in the funder meeting, need the full donor list for the board packet, send as attachment, thanks so much. There is a heart at the end, which she does sometimes.
The development director is loyal, quick and proud of the file. She attaches the spreadsheet to a reply. Downtown, the skyways are full of people who have not been outside since Sunday, and nobody is watching her screen.
Her thumb is on send when she notices the message came from a number, not from the name in her contacts, and she walks two blocks of skyway to the funder's office to ask in person.
What changes the ending
- Donor data kept in the donor system, with card numbers never stored and exports limited and logged, so the file cannot leave in a text reply (CIS 3 Data Protection)
- Training that covers the phone as well as the inbox, because the 2026 DBIR found mobile lures get clicked 40% more often than email, and a report button that works from a phone (CIS 14 Security Awareness and Skills Training)
- Multi-factor authentication and named roles on email and the donor system, so even a stolen password does not open the list (CIS 6 Access Control Management)