Established Fact
Binary analysis of EPBHostService.exe — the poll book host service deployed to all 44 Livonia precincts on Election Day 2020 — reveals a RestoreDatabase API endpoint capable of overwriting the entire active voter database (EPB.accdb, 79 MB) at runtime. Calling this endpoint during an election would replace all voter check-in records accumulated since polls opened — erasing voting-status data and potentially allowing already checked-in voters to re-appear as unchecked-in. No access controls, authentication requirements, or API call logs for this endpoint were produced in any FOIA or subpoena response. The security perimeter of this API on Election Day 2020 is therefore unknown.
Citations
Livonia 2020 Election Precinct Anomalies Report, https://drive.google.com/file/d/1k_ovJlMXpRM62kGP7IilK50nBajg04_x/view?usp=drive_link
Anomaly 23 Detailed Report, 2020 Livonia Election Analysis, https://drive.google.com/file/d/1HjMwF2GTTYelptDD97F3NNgEHJQM6vNT/view?usp=drive_link
The RestoreDatabase API is, by its architecture, a self-erasing capability. The examination of its binary code reveals that the full API surface exposed by EPBHostService.exe includes: api/voters/BackupDatabase/ — creates a backup, api/voters/RestoreDatabase/ — overwrites the active database, and api/voters/CloseDatabaseConnection/ — closes the connection. None of these three administrative endpoints appear in any logging path. Calling RestoreDatabase at runtime would replace EPB.accdb wholesale — overwriting every voter check-in record, every ACTIONHISTORY entry, every VOTINGSTATUS record — and leave no trace of the call itself anywhere in the system. If it was called on Election Day 2020, no record of that call survives in any system accessible through FOIA. The only potential forensic path is the encrypted EPB.accdb itself — if decrypted, a gap in ACTIONHISTORY timestamps or an anomalous reset of VOTINGSTATUS entries mid-election would be circumstantial evidence of a Restore call having occurred.