I built a SaaS that automatically purges ghost subscribers from Beehiiv using AES-256-GCM encrypted API keys and Inngest background jobs

Jun 3, 2026 · 2:14 AM UTC ·7 min read · 0 reactions · 0 comments · 36 views

TL;DR · WeSearch summary

Rodrigue Shema developed a SaaS called ListTrim to automatically remove ghost subscribers from Beehiiv. The tool addresses the issue of inflated subscriber counts that lead to higher billing tiers and negatively impact email deliverability. ListTrim uses a multi-signal qualification method to accurately identify ghost subscribers while minimizing false positives.

Key facts

▪ListTrim was created to help newsletter owners reduce costs by purging inactive subscribers from their lists.
▪Ghost subscribers can inflate billing tiers and negatively affect email engagement metrics.
▪The tool employs a unique method to identify ghost subscribers, ensuring that genuine Apple Mail users are not incorrectly flagged.

About this source

DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.

All DEV.to (Top) coverage →

Original article

DEV.to (Top)

Read full at DEV.to (Top) →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	DEV.to (Top)
Canonical URL	https://dev.to/listtrim_founder/i-built-a-saas-that-automatically-purges-ghost-subscribers-from-beehiiv-using-aes-256-gcm-encrypted-32jp
Publication time	Wed, 03 Jun 2026 02:14:28 +0000
Retrieval time	2026-06-03T02:41:48.967Z
Last seen	2026-06-03T02:41:48.967Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	5FBkfeCv9TfQ
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3965533) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Rodrigue Shema Posted on Jun 3 I built a SaaS that automatically purges ghost subscribers from Beehiiv using AES-256-GCM encrypted API keys and Inngest background jobs #typescript #saas #webdev #security I run a newsletter on Beehiiv. About six months ago I noticed my open rates were sliding while my subscriber count was growing. The two numbers were moving in opposite directions and I could not figure out why until I pulled the raw data.

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed

Discussion

0 comments