SecureCallOps: Building a Privacy-First Phone-Banking Tool
I was volunteering for a phone-banking campaign. The setup was typical: someone shared a Google Sheet with the team. Names, phone numbers, a notes column. Everyone on the calling team could see and download the entire list. It worked, but I kept thinking about what we were actually doing - handing dozens of volunteers unrestricted access to hundreds of people's personal phone numbers. Anyone could copy the sheet, forward it, or just leave it open on a shared computer. And once that data was out, there was no way to pull it back.
The thing is, no individual caller needed all that data. They needed one name and one phone number for the call they were about to make, and everything else was unnecessary exposure.
So I built a replacement and used it for the campaign. After that, I stripped out anything organisation-specific, wrote up the threat model and deployment...
Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE
