First-class event retention (TTL) and arbitrary event deletion for self-hosted product analytics
Operators of self-hosted PostHog can delete a known person and their associated events, but they still lack first-class event retention windows and arbitrary event/event-name deletion for cleanup, retention-policy enforcement, and compliance edge cases. Demand is hot and current: two long-running open issues are collecting fresh +1s from users and customer-facing support threads.
It reads like a feature request but it's really an operations/compliance product: the +1s cite retention policies, privacy requirements, bad event cleanup, and ballooning ClickHouse storage. The hard part isn't a delete button, it's propagating TTL and targeted deletion across partitions and materialized views, which is precisely why a retention/cleanup layer for self-hosted event stores has room to exist.
landscape (3 existing solutions)
Self-hosted product-analytics stores let you ingest unlimited events but still give operators no first-class way to expire old events or delete arbitrary bad/sensitive event sets. Deletion across a columnar event store with materialized views is genuinely hard, which is why TTL and targeted cleanup stay underbuilt.