Data residency
Customer data is processed and stored in Supabase Postgres on AWS infrastructure scoped to a single region. Backups stay in the same region. We do not replicate across borders without your signed approval.
Security and compliance
Every result, tracked from the polling station to your tally.
Every number in your campaign vote count is tied to a polling station, the agent who submitted it, a server timestamp, and the original photo of the result form. Below is the path each number takes, and the checks that hold each step in place.
Security and compliance
Built for the lawyers, not just the operators.
If your legal team cannot defend the chain of custody, the rest of the platform does not matter. Here is the posture we ship with.
Encryption at rest and in transit
AES-256-GCM for stored records and uploads. TLS 1.3 for every connection between agent device, our edge, and the database. Photo uploads use short-lived presigned URLs that never proxy through our API.
Retention schedule
Operational records held for the full petition window plus seven years. Photos and audit logs follow the same retention. Export and deletion requests honored on documented timelines.
Audit logging
Every state change on a result, every export, every role grant is written to an append-only audit log. Logs are queryable by your manager and by the legal desk.
RFC 3161 timestamps
Critical evidence artifacts are sealed with cryptographic timestamps from an external trusted timestamp authority. The seal is verifiable independent of our infrastructure.
IEBC posture
We do not transmit on IEBC's behalf and we do not claim to be an official source. Election Edge is your campaign's parallel operational record - distinct from, but reconcilable against, the official tally.