Short explanation for the selection
Emergency-alert systems sit at the intersection of public safety, privacy, and digital design — which makes them rich material for a dissertation that combines technology studies and gendered harm. These systems are intended to protect populations, yet their default behaviors (automatic, attention-grabbing, location-aware) can produce asymmetric harms for people experiencing intimate partner abuse. Studying them lets you analyze concrete technical design choices, policy trade-offs, and ethical responsibilities, and to propose technically feasible mitigations grounded in survivor needs and human-rights frameworks.
Additional technology-focused points tied to abuse (concise)
- Notification modality design
- Problem: Audible/vibrating alerts and lock-screen previews are engineered to maximize attention; on monitored devices they signal presence or location.
- Abuse link: Triggers discovery of hidden phones, alerts nearby abusers, or provokes interrogation.
- Research/design angle: Evaluate alternative modalities (silent, haptic patterns only for trusted devices, discreet LED-only, or authenticated unlock reveal) and trade-offs for reach and timeliness.
- Targeting granularity and geofencing logic
- Problem: Highly precise geo-targeting increases effectiveness but also pinpoints survivors.
- Abuse link: An abuser can infer a victim’s location even from small-cell targeting or repeated localized alerts.
- Research/design angle: Model harms vs. benefits of coarse vs. fine-grained geofences; propose default coarse targeting with escalation criteria and dynamic anonymization.
- Channel and delivery architecture
- Problem: Alerts are usually broadcast via cellular networks/SMS or system-level push; these channels surface on all registered devices.
- Abuse link: Devices registered to a shared account or controlled SIM will receive alerts; presence of alternate "safe" channels is limited.
- Research/design angle: Explore multi-channel designs (secure consented apps, webhooks to nominated devices, wearable-only channels) and secure enrollment protocols that resist coercion.
- Enrollment, consent, and account-management flows
- Problem: Enrollment UX often assumes individual autonomy and visibility; account recovery and SIM swaps can be coerced.
- Abuse link: An abuser who controls accounts can change settings or force opt-in/opt-out, undermining survivor preferences.
- Research/design angle: Propose survivor-aware enrollment flows (silent registrations, third-party-verified safe-profiles, delayed notification of setting changes) and threat models for account compromise.
- Metadata and side-channel leakage
- Problem: Even when content is minimal, metadata (time, frequency, cell-id) and notification timing leak information.
- Abuse link: Abusers analysing patterns can detect routines or presence, or correlate alerts with movement.
- Research/design angle: Study metadata minimization, batched/indistinguishable broadcasts, and randomized timing to reduce inferability.
- Device ecosystems and shared accounts
- Problem: Family/shared devices, children’s profiles, and paired wearables complicate per-person preferences.
- Abuse link: Survivors using shared devices cannot safely receive alerts or change settings without detection.
- Research/design angle: Design per-user profiles on shared devices (secure user contexts, hidden app modes) and evaluate platform API capabilities (Android/iOS).
- Authentication, pairing, and secondary devices
- Problem: Current systems lack secure, easy ways to pair private devices for sensitive alerts.
- Abuse link: Survivors cannot reliably maintain a private communication channel if pairing is visible.
- Research/design angle: Prototype low-friction, stealthy device pairing methods (QR in person, one-time physical tokens, or service-mediated safe pairing) that leave minimal logs.
- Failover, escalation rules, and message content policy
- Problem: Escalation logic (when to broadcast, what detail to include) is often static.
- Abuse link: Overly detailed messages (shelter locations, escape routes) can be exploited by abusers.
- Research/design angle: Create context-aware content policies that balance actionable guidance with safety, and adaptive escalation that respects registered safety profiles.
- Auditability, logging, and forensics
- Problem: Systems log deliveries and setting changes for accountability.
- Abuse link: Logs accessible to cohabitants or via shared accounts can expose survivor actions.
- Research/design angle: Recommend secure, privacy-preserving logging (encrypted logs, survivor-controlled deletion windows) and retention policies aligned with safety.
- Platform/vendor constraints and regulatory environment
- Problem: Mobile OS and carrier constraints limit what governments can change (e.g., overriding do-not-disturb).
- Abuse link: Survivors cannot reliably silence emergency messages on controlled devices.
- Research/design angle: Map technical constraints of iOS/Android/carrier protocols, identify feasible points of intervention, and propose regulatory or standards changes.
- Integration with domestic-violence services and threat assessment
- Problem: Alerts rarely integrate survivor-support workflows.
- Abuse link: Lack of contextualized help means alerts can increase panic without offering safe next steps.
- Research/design angle: Design API-level integrations so approved support services can register safe profiles, push discreet safe-help options, or temporarily suppress audible alerts with consent.
Methodological approaches you can use
- Threat modeling: create attacker profiles (coercive partner, shared-account abuser) and map system attack surfaces.
- Usability/security experiments: test stealth-mode prototypes with survivors and advocates (ethically recruited).
- Policy & standards analysis: examine emergency-alert standards, telecom rules, and privacy law constraints.
- Ethnographic interviews: with domestic-violence practitioners to ground technical choices in lived needs.
- Simulation & analytics: quantify trade-offs between alert reach/timeliness and privacy/risks using simulated geofencing and delivery models.
Relevant references to start with
- Stark, E. (2007). Coercive Control: How Men Entrap Women in Personal Life.
- Woodlock, D. (2017). The abuse of technology in domestic violence and stalking.
- World Health Organization (2017). Responding to intimate partner violence and sexual violence against women: WHO clinical and policy guidelines.
- UK Home Office materials on emergency alerts and mobile network provider protocols.
If you want, I can draft a one-page problem statement or a concise threat model diagram outline you could drop into your dissertation.