MediaMask.ai
Creative-layer cloaking
One system that rewrites the asset, generates the safe page and makes the routing decision at the edge. The thing platforms match — the creative signature — is what changes.
Comparison
Three architectures that get shortlisted together and solve different problems. A redirect script decides a destination. A tracker reports on the click. Neither one changes the creative signature that automated review actually matches. Here is the whole difference, line by line, with the numbers we publish everywhere else.
38ms p95 decision · 41 anycast regions · 14,208 ASN ranges
MediaMask.ai
One system that rewrites the asset, generates the safe page and makes the routing decision at the edge. The thing platforms match — the creative signature — is what changes.
Redirect scripts on a VPS
A PHP or Node script that picks a destination from an IP list. It decides what happens after the click and never touches the creative sitting in the ad account.
Attribution platforms
Measurement, not filtering. They tell you what happened after the click in useful detail, and change nothing about what an automated reviewer sees.
Synthesis matrix
The three rows marked are the differences that decide the choice: the decision latency, whether the creative container is rebuilt at all, and what the decision runs on.
| Capability | MediaMask.ai | Traditional link cloakers | Cloud-based trackers |
|---|---|---|---|
| Routing decision | |||
| p95 decision latency | 38ms, measured at the terminating edge node | 180–450ms through a single origin | 300ms or more across two redirect hops |
| Where the decision runs | 41 anycast edge regions, closest node per request | One to three origin servers you rent | In the visitor’s browser, after the page loads |
| Reviewer scoring signals | Canvas and WebGL entropy, TLS cipher order, header sequence, ASN, headless traces, request timing | IP blocklist and user-agent string | None — measurement only, no filtering |
| Network intelligence | 14,208 ASN ranges, with residential proxies scored apart from datacenters | Hand-maintained IP lists, updated when someone remembers | Not applicable |
| Creative layer | |||
| Automated creative container rebuilding | Yes — the container is rebuilt per platform encoder profile on every job | Not attempted; the uploaded file is untouched | Not attempted |
| Image signature rewrite | Luma map, chroma grid and metadata container rebuilt at 0.81% median visual delta | None | None |
| Video masking | Per-frame jitter and re-grain, audio fingerprint drift, signed HLS delivery, up to 4K and 180s | None | None |
| Perceptual hash families addressed | pHash, dHash, aHash and block-mean | None | None |
| Safe-page generation | 50+ niche templates, editable, published to a domain you control | Bring your own HTML and hosting | Not applicable |
| Isolation and hosting | |||
| Serverless proxy isolation | Each decision runs in its own short-lived isolate — no shared origin to fingerprint | A shared VPS: one IP and one TLS fingerprint across every customer on the box | A third-party script executing inside your own page |
| Footprint on your landing page | None — no third-party script to load | A redirect hop | Tag manager plus vendor script |
| Creative retention | Static images are masked in the browser and never uploaded; server-side assets purged after 30 days | Varies by operator; usually indefinite | Retained for the full attribution window |
| Billing surface | Crypto settlement, no card on file | Card — routinely frozen in this category | Card, with annual commitments |
| Operations | |||
| Response to flag signals | A standby variant is promoted in about 90 seconds, unattended | Manual swap once you notice | Not applicable |
| Platform coverage | Eight: Meta, Google, TikTok, Snapchat, Pinterest, native networks, YouTube, X | Link destinations only — nothing platform-specific | Measurement across any platform |
| Time to first masked creative | About fifteen minutes — account, plan activation, first job | A VPS, a domain and a weekend of configuration | A container tag and an internal review cycle |
| API and white-label | REST API, white-label dashboard and safe-page domains on Cloaklord | Rare, and usually undocumented | Read-only reporting API |
Scroll the table sideways on narrow screens. Latency figures for the other two columns are the range we measure when buyers migrate off them, not vendor claims. Everything in the MediaMask column is the same number the dashboard reports.
Quick answers
The questions that come in before a trial, answered in a sentence or two each. The longer versions live in the guides.
MediaMask.ai is a creative-layer cloaking platform. It masks image and video ad creatives, then routes every click at the edge so reviewers and audiences land on different pages.
The engine re-samples the pixels, drifts luma and chroma below the perceptual floor, strips every metadata block and rebuilds the container, then publishes to 41 anycast edge regions.
Smart links decide at the edge in 38ms at p95, measured across all 41 anycast regions. Your audience sees one redirect; filtered traffic gets the safe page.
A link cloaker only chooses a destination. MediaMask also rewrites the creative itself, which is where platform enforcement now matches assets against previously actioned files.
Meta, Google, TikTok, Snapchat, Pinterest, native networks, YouTube and X. Stealth covers Meta and Google; Phantom and Cloaklord cover all eight.
Static images are masked in your browser and never reach our servers — only the job record is kept. Server-side video assets are purged after thirty days.
Mask an asset, read the before and after hashes, then check the routing decision in the analytics stream. The numbers on this page are the ones you will see, and the originals are never modified.