Secure Pride
A privacy-first cybersecurity nonprofit for LGBTQ+ clinics, mutual aid orgs, and health services — people for whom a breach is not an inconvenience but an outing. I founded it and work on it as security engineer.
I work with teams whose infrastructure touches people who can't afford a leak.
I'm a security engineer, content strategist, and founder of Secure Pride — a privacy-first cybersecurity nonprofit for LGBTQ+ clinics, mutual aid orgs, and health services.
My work starts from three questions: who is this for, what can it see, and what happens when it fails them.
Orientation, not the record — /work carries that, with the evidence for each claim.
A privacy-first cybersecurity nonprofit for LGBTQ+ clinics, mutual aid orgs, and health services — people for whom a breach is not an inconvenience but an outing. I founded it and work on it as security engineer.
Security architecture, threat modeling, and the documentation that has to match it — for teams whose systems touch sensitive data or communities poorly served by default frameworks.
Not a fit for generic SEO content, compliance theater, or brand work without a technical foundation.
A local-first context framework in Swift: modeling what a system has learned about you over time, on-device, with a way to interrogate and correct what it thinks it knows.
Everything I do starts from an explicit sense of stakes, and from humans who are not an afterthought.
I left a neuroscience lab after years of measuring cognitive decline in aged macaques — work that produced clean numbers and publishable figures, but left a gap between the data and the animals I couldn't live with. Since then, Secure Pride, Context Synapse, and my client work have all been different ways of answering the same questions: who is this for, what can it see, and what happens when it fails them?
Labs, tools, podcasts, and past roles — the CV has the record in order, and /work has it with the evidence for each claim.
Outside of that: I make music — Ableton, Logic, a Universal Audio Volt 2, and a Martin acoustic-electric named Joni — and I write speculative fiction. Based in Durham, NC, working across time zones.
Security and infrastructure consulting for small teams, narrative and content strategy for developer tools, and collaborations with organizations whose systems touch vulnerable communities or sensitive data.
2–6 weeks. Threat modeling, control design, and incident runbooks for one critical system. Best for: small teams pre-SOC2, post-incident, or building something that touches sensitive identity or health data.
Ongoing or project-based. Positioning, technical docs, and security pages that reflect how your system actually behaves. Best for: infra and security products whose copy has drifted from their architecture.
Quarterly or monthly. Infra review, content audit, and AI governance check-in with an explicit human-risk lens. Best for: orgs that need a security + narrative voice without a full-time hire.