City of Aurora seeks school partnership for $50 children’s savings accounts; board raises data-privacy concerns

City of Aurora officials asked the East Aurora School District 131 Board of Education on Monday to partner in Aurora’s Promise, a pilot children’s savings account (CSA) program that would seed resident kindergartners with a $50 contribution and additional incentives to encourage savings and financial‑literacy engagement.

The presentation was led by Viviana Ramirez, chief community services officer for the City of Aurora, and Martha Paschke, director of innovation and strategy in the city’s community services department. Ramirez said the program is intended to “establish in the youngest kids in our city that their city believes in them” and to spur savings habits through a digital platform managed by Operation Hope. Paschke said the pilot would start with kindergartners in Districts 129 and 131 and run about 18 months as an opt‑in program before the city seeks to move to opt‑out enrollment.

The nut graf: Board members pressed city officials on what student and family data would be shared, who would maintain it, whether incentive funds would earn interest, and what would happen to accounts if families moved or students left the district. Because several trustees raised unresolved concerns about the data‑sharing agreement and the legal risk of third‑party subpoenas, the board declined to take the motion and directed district staff to work further with the city to study data privacy and implementation details.

Board members and city staff described the program’s core features and partner roles. Operation Hope would provide the digital platform (the presentation named the vendor Vistashear as the database) and US Bank would be the banking partner; the city would maintain a pooled fund rather than opening individual bank accounts for children. Paschke said families would be able to deposit additional money, and those family deposits could be withdrawn by the family for emergencies, but the city’s incentive funds would remain restricted for postsecondary use and would be disbursed when a student reaches age 18 or graduates.

Paschke described the pilot incentives: the city’s $50 seed, a $10 activation incentive during the opt‑in pilot, and an additional $20 for students who qualify for the National School Lunch Program (the presentation said “my understanding is that all the children here in our district will qualify”). The presentation cited national research and local program examples, including San Francisco, where organizers reported a higher on‑time graduation rate and increased college enrollment among CSA participants. Paschke said average account balances observed in comparable programs have reached about $1,400 for some cohorts.

Several trustees focused on the data elements requested in the city’s data‑sharing agreement: “student first name, last name, birth date, school they’re in, state student ID number, parent/guardian names and education levels, mailing addresses, phone numbers, emails, primary language, and National Lunch Program status,” a board member read during the meeting. Trustees asked whether the vendor or bank could use student contact information for marketing, whether the pooled account would earn interest, and what protections exist if a family moves or a student is deported. City staff said US Bank would not receive student information unless families opened a separate bank account; Operation Hope would maintain the digital ledger and the city had vetted that vendor’s insurance and track record.

Trustees also raised legal concerns about subpoenas and control of records. One trustee explained the district can contest subpoenas when it retains records; the trustee said that if the district shared data directly with a third party, the district could lose the ability to resist a subpoena and urged contract language to preserve the district’s ability to intervene.

After extended questions, the board did not vote on the data‑sharing agreement or a partnership motion. Instead, the board instructed district staff to work with the city to review the data‑sharing terms, address the subpoena question and other privacy safeguards, and return with recommendations. “At this point, we are gonna go back and have the district work with the city and do some more studying with definitely with the way the data and everything is being captured,” a board member said.

City staff said they would take back the questions—including the subpoena issue—for further work and follow‑up with the board. The presentation materials identify Operation Hope as the proposed program operator and Vistashear as the digital database; the city described the pilot as opt‑in for kindergarten families for roughly 18 months before transitioning to an opt‑out model where, in the city’s description, every resident kindergartner would receive the seed contribution unless families opted out.

Ending: The board did not adopt the data‑sharing agreement or a formal partnership motion on Jan. 27; district staff will meet with city officials to refine data protections and implementation details before the board considers action.