I'm building an AI tool to auto-generate GDPR complaints when companies leak my email. Too aggressive?

Why I’m Building an "Email Condom" over the weekend?

The problem: I sign up for B2B services, and weeks later I get spam. I never know who leaked my email.

The solution:

I generate a unique alias for every service (zoom@sentry... , notion@sentry... ).
If that alias receives email from a different domain, the system flags a Data Breach.
(Here is the fun part) It offers to auto-generate a GDPR Article 33 complaint against the original service provider.

Tech Stack: CF Email Routing -> Workers -> Gemini 2.0 Flash (to analyze spam) -> My Inbox.

Discussion: Is the "GDPR Complaint Generator" too aggressive as a feature? I feel like accountability is zero right now. Companies sell data because they can. If we automate the "fighting back" part, maybe they'll stop?

I'm launching the MVP Monday. Would you use this?

Alexey Anshakov

on January 23, 2026

Say something nice to alexey_anshakov…

Post Comment

1
Not too aggressive — exactly the right friction.

Companies leak data because there's no cost. The "fight back" button changes the economics.

A few thoughts:

On the concept:
- The per-service alias approach is solid. I've used similar setups manually ([email protected]), but automating the tracking and flagging is the real value.
- The GDPR complaint generator is the hook that makes this more than just another alias tool.
On positioning:
- "Email Condom" is memorable but might limit you in B2B contexts. Worth A/B testing a more "professional" alternative (though the viral potential of the current name is real).
Questions:
1. How do you handle legitimate third-party services? (e.g., payment processors, analytics) — false positives could get noisy.
2. What's the actual complaint workflow? Auto-file or review-then-file?
3. Pricing thoughts? Per-alias, flat subscription, or freemium?
I'd try this. The "who leaked my email" question is something I've wondered about for years.
yamamoto7

·
9 hours ago
·
Reply