Internet & Telephone Voting
Secure internet and telephone (IVR) voting platform for municipal elections — cryptographic ballot secrecy, multi-channel double-voting prevention, ML anomaly detection, and blockchain-style audit trails per MEA s.42.
System Availability
Multi-Channel Sync
DDoS Resilience
AODA/WCAG
Purpose-Built for Canadian Municipalities
Purpose & Scope
What this module owns
Clear ownership boundaries prevent duplication and ensure every capability has exactly one authoritative home.
Owns
11Delegated to
4Voters list & candidate data, results consolidation
Penetration testing & threat monitoring
Credential delivery & confirmation
Responsive web portal
These capabilities are handled by dedicated modules and consumed via stable API contracts — keeping boundaries clean and ownership unambiguous.
Core Capabilities
What it does
4 capability groups comprising 11 discrete capabilities — each with API surface, business rules, and data ownership.
Unique single-use PIN with secondary verification (DOB, shared secret, OTP), physical mail or digital delivery, and anti-guessing protection.
PIN Generation
Unique single-use PIN with randomness/guessing prevention measures.
Secondary Verification
DOB, shared secret, or OTP for two-factor authentication.
Secure Delivery
Physical mail (scratch-off/tear-off security) or digital delivery.
Internet (PIN + secondary) and IVR (keypad PIN + secondary) authentication with 3-attempt lockout and real-time voters list check.
Internet Auth
PIN + secondary verification via web portal.
IVR Auth
PIN via keypad + secondary verification via touch-tone.
Lockout
3-attempt lockout; credential recovery via help desk with identity verification (no voting status reveal).
Adaptive authentication per risk score (device, location, time) with escalating verification requirements.
Risk Scoring
Risk score based on device fingerprint, location, and time of access.
Adaptive Auth
Low-risk = standard (PIN+DOB); elevated = additional (security questions, email/SMS codes).
Logging
All authentication events logged with risk scores for audit.
Every module owns a single bounded context, exposes stable APIs, and can be composed into any Civic product — that's the architecture that scales.
Krutik Parikh
Creator of Civic
Data Model
Entity Architecture
4 entities with 3 relationships — the authoritative schema for this bounded context.
Entities
Select an entity to explore its fields and relationships
API Surface
Integration Endpoints
7 RESTful endpoints across 5 resource groups — plus 5 domain events for async integration.
/api/v1/voting/authenticate
Voter authentication
Ecosystem
Products that depend on this module
2 Civic products consume Internet & Telephone Voting — making it one of the most critical platform services in the ecosystem.
Technical Specifications
Performance, Compliance & Configuration
System Availability
Ballot Secrecy
Multi-Channel Sync
Authentication
DDoS Resilience
Results Accuracy
AODA/WCAG
FAQ
Frequently Asked Questions
Ready to Integrate
Build on Internet & Telephone Voting
Request an architecture brief, integration guide, or live demo environment for your team.