Partner brief · for web-governance platforms
Your platform tells customers whether their tags and consent setup follow the rules across thousands of pages. Faraday answers the question regulators and plaintiffs actually ask: when this person said no, did their data go anywhere?
The spirit of the law
Consent laws were passed because people's data was being shared against their wishes. Checking banner configuration, consent categories and tag rules is necessary. It doesn't show whether the data actually stayed put. Faraday is built to show that, and it does it without sending a single test request to a vendor.
Illustrative pairing. The re-identification is a real finding from Faraday's demo shop.
Where it fits
You cover the whole site, in production, at scale. Faraday goes deep on the pages that matter most, before release.
Your platform
Faraday
Ways to work together
These are proposals for discussion. None of these integrations exist yet.
Your audit flags a page with a consent rule failure. Faraday replays that page in the sealed browser and shows the exact payload, the script that sent it, and the consent phase it happened in.
Import your scripted journeys as Faraday journeys. Export Faraday's findings as rule results, so customers see them in the tool they already use.
Faraday runs in the customer's CI before a deploy, and your platform monitors production after it ships. Together they cover the full release cycle.
On the roadmap
Does an opt-out on one site actually stop the data from reaching that site's partners?
Foolia opts out on a host site, then visits that site's ad partners in the same browser profile. The test checks whether a partner's ad stack acts like it already knows her, or receives an ID only the host could have created. That would be direct evidence of the cross-business sharing that consent laws restrict.
Public seller and inventory files help pick which partners to test. They show who can sell a site's ad space. They don't show data sharing.
Partner sites aren't our customers. Before this ships, a lawyer reviews each in-scope site's terms of service, and the tool is limited to acting as an ordinary visitor: no bypassing bot checks and no non-public systems. Findings will be framed for the customer as "your vendors are leaking," never as an accusation against a third party.
What's hard to copy
Most features on a datasheet can be cloned. These parts take real time to get right.
The browser starts with every hostname resolving to nothing. Every byte passes through one interceptor. Stray preconnects, DNS-encoded data and peer-to-peer STUN requests fail closed.
Randomness is seeded and the clock is frozen inside the page. Record once, replay twice, and diff the requests. A finding you can rerun is one a customer can trust.
Fabricated persona values are searched for in every payload: raw, URL-encoded, base64 at any offset, hex, and three hash formats.
The ask
One hour with your product and solutions engineering teams to walk through the sealed engine and the demo shop. If it fits, run a joint pilot on one property that a shared customer authorizes in writing.
Faraday · closed beta · findings are evidence for a review, not legal advice · Product · Brand · Back to hord.brayden