One asset, one declaration, multiple destinations. Disclosure Router turns the same creative into a platform-by-platform action route for Amazon, Google, TikTok, YouTube, Meta and EU transparency rules.
The problem is shipping it. Every platform and jurisdiction can ask for something different: a native disclosure switch, a visible label, machine-readable provenance, metadata, or no action at all.
A single creative can face different requirements depending on channel, region and how the asset was produced.
Teams waste time re-checking support pages, policy updates and regional requirements for every campaign.
Creative, media and compliance teams often document the same AI-use facts repeatedly in different systems.
Disclosure Router is not an AI detector. Your team declares how the asset was made, and the product maps that declaration to each destination.
Instead of a generic “compliant / not compliant” score, you get the actual publishing route.
CAMPAIGN: Autumn Launch 26 ASSET: hero_v07.jpg AI USE: Fully generated · photorealistic synthetic person TARGET: Amazon + Google Ads + TikTok Ads + YouTube → AMAZON · AUTOMATABLE Prepare file automatically Then continue in Amazon → GOOGLE ADS · ACTION IN PLATFORM Open Google Ads View instructions → TIKTOK ADS · MANUAL ACTION View instructions → YOUTUBE · ACTION IN PLATFORM Open YouTube Studio View instructions EVIDENCE Declaration + rule version + timestamp saved
One payment, 12 months of Founder access. No lifetime promises. Founder customers keep the beta price for the first year while helping shape the product.
Professional use only: Founder Beta is intended for businesses, agencies, studios, freelancers and other professional users purchasing for business or professional purposes.
Founder Beta: purchase access for 12 months. Applicable taxes are calculated at checkout. Access instructions are sent automatically to the email used during payment.
Disclosure Router is designed around the publishing operation: what this asset needs on each destination, what can be automated, what must be done natively, and what evidence to keep.
The source of truth is the team's declaration plus technical provenance when available, not a probabilistic detector guessing how the content was made.
Every route is intended to reference the policy or rule version used so teams can later show what they relied on when publishing.
The current route flow reads the selected media in your browser. It sends asset metadata, a SHA-256 fingerprint and your declaration to create and save the evidence record; it does not send the raw media bytes in that route request.