Every verdict is explainable
If we filter a click, the log says which signal decided it — the ASN, the fingerprint mismatch, the request cadence. A black-box score is indistinguishable from a coin flip you cannot audit.
CloakShield Pro is a security layer for teams already routing traffic through Cloaking House, Keitaro, Voluum or something home-grown. It scores the click before your router sees it, and it watches the page after the click lands.
In 2021 the four of us were running acquisition for a payments client and losing about a fifth of the budget to traffic that was never going to convert — scraper fleets, compliance sweeps, residential proxy pools rented by the hour. The router did its job perfectly. It just had no idea what it was routing.
So we wrote a scoring service in front of it. Then we wrote it again for the next client, and again for the one after that, each time re-deriving the same ASN lists, the same TLS fingerprint checks, the same timezone-versus-carrier comparison. The fourth rewrite became the product.
The design constraint has never changed: we sit beside your stack, not on top of it. If you turn CloakShield Pro off tomorrow, your campaigns keep running. That is deliberate — a filtering layer you cannot remove is a filtering layer you cannot trust.
If we filter a click, the log says which signal decided it — the ASN, the fingerprint mismatch, the request cadence. A black-box score is indistinguishable from a coin flip you cannot audit.
We hold configuration, verdicts and integrity hashes. We do not store your landing pages, your creatives or your offer terms, so a breach of us is not a breach of your campaign strategy.
Onboarding is a CNAME. Offboarding is deleting it. There is no proprietary tag buried in your funnel and no migration project waiting for you at the end of a contract.
Plans are priced per month, not per click. A campaign that suddenly works should not generate a surprise invoice, and you should never have to choose between filtering traffic and affording to filter traffic. The multi-month discounts on the pricing page are the whole discount structure — there is no enterprise pricing conversation where the real numbers live.
Small enough that the person who answers your ticket wrote the code it is about.
Wrote the first scoring service in a hotel lobby in Kraków. Owns the edge runtime and the parts of the verdict pipeline nobody else wants to touch.
Ran paid acquisition for eight years before this. Decides what ships based on whether it would have saved her old budget, which is a harsher filter than it sounds.
Maintains the ASN and fingerprint corpus. Spends an unreasonable share of his week reading TLS handshakes and arguing that a heuristic is not evidence.
Runs the SOC 2 programme, the annual pen test and the subprocessor register. Also the reason shadow mode exists before every rule change.
Answers Telegram. Has migrated more Keitaro and Voluum setups than the rest of the team combined and will tell you honestly if yours is a bad fit.
Edge infrastructure, integrations, integrity monitoring and the on-call rotation across CET, GMT and PST.
Mail Cloakshield.pro@outlook.com with SECURITY in the subject. We acknowledge within one business day and give you a triage decision within five.
We will not pursue legal action against good-faith research that stays within a test account, avoids other customers' data, and gives us 90 days before disclosure. We credit reporters by name unless you would rather we did not.
Breach notification is 72 hours from awareness, to you and to the relevant supervisory authority, in line with the privacy notice.
Email and Telegram, answered within 24–48 hours on business days. Full documentation and the integration guides for every supported router.
Priority queue, first response inside 8 business hours, and a shared Telegram channel with the engineers on rotation rather than a ticket robot.
A named engineer, a 1-hour response target for anything affecting live traffic, and a quarterly review of your verdict mix against your conversion data.
Incidents affecting verdict delivery page the on-call engineer immediately, regardless of plan — a filtering layer that fails quietly is worse than no filtering layer. Status and postmortems go to every affected account by email, including the ones on Starter.
Tell us what you route with and where the traffic comes from. If we are a bad fit for it we will say so — that conversation is cheaper for both of us than a refund.
Create an account in two fields, choose a term, pay in crypto. Rolling back is deleting a DNS record.