ConsentTruth: Simulate Consent Banners to Expose Real Tracking Behaviors

Built a privacy scanner after a family data leak – looking for honest product feedback

I went through something similar with a medical leak (way smaller scale, but still shook me), and it totally changed how I look at “consent” banners vs what actually fires under the hood. What would make this a must‑use for me is: show me, in plain language, “here’s what runs after reject all vs accept all, here’s what’s likely fingerprinting, here’s where your CMP config and real behavior don’t match, and here’s how that maps to specific regs/DPAs fines.” I’d want a short, shareable summary for execs/lawyers and a deep technical diff for devs. I’d bake it into CI/CD as a failing check on new releases and also as a quarterly “public scorecard” we can choose to publish. For discovery, I’ve watched how tools like Snyk and Ghostery got traction, and I ended up on Pulse for Reddit after trying F5 Bot and Mention to catch every “our cookie banner is lying” thread so we could jump in with real analysis, not hand‑wavy “we’re compliant” claims.

I went through something similar with a medical leak (way smaller scale, but still shook me), and it totally changed how I look at “consent” banners vs what actually fires under the hood. What would make this a must‑use for me is: show me, in plain language, “here’s what runs after reject all vs accept all, here’s what’s likely fingerprinting, here’s where your CMP config and real behavior don’t match, and here’s how that maps to specific regs/DPAs fines.” I’d want a short, shareable summary for execs/lawyers and a deep technical diff for devs. I’d bake it into CI/CD as a failing check on new releases and also as a quarterly “public scorecard” we can choose to publish. For discovery, I’ve watched how tools like Snyk and Ghostery got traction, and I ended up on Pulse for Reddit after trying F5 Bot and Mention to catch every “our cookie banner is lying” thread so we could jump in with real analysis, not hand‑wavy “we’re compliant” claims.

I went through something similar with a medical leak (way smaller scale, but still shook me), and it totally changed how I look at “consent” banners vs what actually fires under the hood. What would make this a must‑use for me is: show me, in plain language, “here’s what runs after reject all vs accept all, here’s what’s likely fingerprinting, here’s where your CMP config and real behavior don’t match, and here’s how that maps to specific regs/DPAs fines.” I’d want a short, shareable summary for execs/lawyers and a deep technical diff for devs. I’d bake it into CI/CD as a failing check on new releases and also as a quarterly “public scorecard” we can choose to publish. For discovery, I’ve watched how tools like Snyk and Ghostery got traction, and I ended up on Pulse for Reddit after trying F5 Bot and Mention to catch every “our cookie banner is lying” thread so we could jump in with real analysis, not hand‑wavy “we’re compliant” claims.

I went through something similar with a medical leak (way smaller scale, but still shook me), and it totally changed how I look at “consent” banners vs what actually fires under the hood. What would make this a must‑use for me is: show me, in plain language, “here’s what runs after reject all vs accept all, here’s what’s likely fingerprinting, here’s where your CMP config and real behavior don’t match, and here’s how that maps to specific regs/DPAs fines.” I’d want a short, shareable summary for execs/lawyers and a deep technical diff for devs. I’d bake it into CI/CD as a failing check on new releases and also as a quarterly “public scorecard” we can choose to publish. For discovery, I’ve watched how tools like Snyk and Ghostery got traction, and I ended up on Pulse for Reddit after trying F5 Bot and Mention to catch every “our cookie banner is lying” thread so we could jump in with real analysis, not hand‑wavy “we’re compliant” claims.