<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>RED — Security engineering notes from Hookay</title><description>RED is the public notebook of Hookay&apos;s security and privacy engineering work. We publish research findings, hard-won best practices, and blameless post-mortems — because privacy engineering for queer platforms is too important to keep proprietary. Everything here is generalized: lessons, not blueprints.</description><link>https://red.hookay.eu/</link><item><title>De-anonymizing the “anonymous”: how location aggregates leak identity, and how to design ones that don&apos;t</title><link>https://red.hookay.eu/posts/location-aggregates-leak-identity/</link><guid isPermaLink="true">https://red.hookay.eu/posts/location-aggregates-leak-identity/</guid><description>Aggregated location stats feel safe — “31 people in this area this week” names nobody. Our internal red-teaming shows how cell size, update cadence, and cross-time correlation can still single out individuals, especially in low-density regions. We walk through the attack classes, then derive concrete design rules: minimum cohort thresholds, net-delta updates, and why suppression must fail closed.</description><pubDate>Wed, 10 Jun 2026 00:00:00 GMT</pubDate></item><item><title>Why k-anonymity is a floor, not a feature</title><link>https://red.hookay.eu/posts/k-anonymity-floor-not-feature/</link><guid isPermaLink="true">https://red.hookay.eu/posts/k-anonymity-floor-not-feature/</guid><description>“Each user is indistinguishable from k−1 others” sounds like a guarantee. It is a starting assumption — and treating it as a finished privacy property is how anonymized datasets keep getting de-anonymized. The primer we wish every product spec linked to.</description><pubDate>Thu, 14 May 2026 00:00:00 GMT</pubDate></item></channel></rss>