Browser-side blocking, tag cleanup, fingerprinting reduction, checkout pressure warnings, and receipts.
Install cloak. Join Founding 100.
cloak is live on the Chrome Web Store. Install the browser privacy extension now, then join the Founding 100 waitlist so Ray can send the paid activation link when we open checkout after the first 100 real people are queued.
Install is open. Paid checkout waits for a clean Founding 100 launch.
We are not filling this with fake testimonials or routing early money through messy personal-account plumbing. The right launch path is simple: install, waitlist, Stripe checkout, activation email, then real reviews from real users.
Stripe and paid activation are ready, but paid access opens after the launch list is ready.
No personal-payment workaround. No customer relationship starts before the business handoff is clean.
Start here if you want the quick version.
Launch explainer video: what cloak is, why the browser is the defense layer, what Ray blocks today, and why the first launch path is install, Founding 100, clean Stripe activation, then real user receipts.
See the extension before paid access opens.
The demo shows the actual cloak flow: install, Ray, the browser-side defense loop, and the kind of receipt a shopper can understand before checkout.
When Founding 100 opens, Ray sends the clean paid path.
The next paid step is not a manual payment workaround. It is Stripe access, activation code, install instructions, and a support path if anything breaks.
Start with shopping defense. Expand only after proof.
Chrome shopping privacy defense: trackers, fingerprinting signals, URL tracking, and checkout pressure warnings.
Stripe and paid activation are built. We open paid access after the Founding 100 list is ready to convert cleanly.
First-access notes help us prioritize the exact shopper pain segments and email warm users first.