Check the consent banner declares every active third-party actor
You have a banner. Skanopy compares what it declares to what actually fires, and places every exchange before or after the user’s choice. The gap between the two is precisely what an inspection comes looking for.
The banner, criterion by criterion
Every criterion recorded as the user actually meets it.
What the consent banner leaves undeclared.
You have installed a consent banner. But nothing tells you the app actually respects it. A banner collects a choice; it does not prove that choice is followed.
Skanopy compares what the banner declares with what actually leaves the device. The active actors it stays silent about surface at once. The analysis also captures what fires before any consent, what keeps going despite a refusal, and checks that the banner leaves a real choice: a refusal as simple as acceptance, access to the privacy policy, the ability to change one’s mind.
The need is real: research has shown that most apps contact trackers as soon as they open, before any interaction (University of Oxford study, 2021), and that among those that do show a banner, one in five still breaks a consent rule (CISPA study, 2022). A banner is not proof.
What Skanopy reveals.
Every point is a finding from the report: captured on a real phone, dated and verifiable.
What the banner leaves out
The actors actually active that the consent banner does not declare to the user.
Before consent
What fires before the user makes any choice, backed by the evidence.
A refusal respected
What keeps firing despite a refusal to be tracked.
The banner examined
A refusal as simple as acceptance, access to the policy, ease of changing your choice.
Your monetization, watched too
The actors that fire, and the ones that stay silent after an acceptance. A partner receiving nothing is measurement and attribution lost.
How Skanopy works.
Point us to the app
Two ways in:
- A Google Play Store link
- A .apk file, for a pre-release before it ships
Skanopy analyzes it
On real phones, a real journey replayed automatically:
- Tracking refused
- Signed in
- Article opened
- Form submitted
Every third-party actor that fires is mapped.
You receive your report
Every fact, named:
- Active third-party actors
- Identifiers shared
- Permissions requested
- Storage access
- Consent-banner compliance
Your questions, our answers.
Your banner collects users’ choices; it does not check, on a real phone, that the app respects them. Skanopy is that independent check. And studies show a banner often coexists with non-compliant transmissions.
Skanopy observes the very first launch and records what leaves before the user makes any choice, the window where most apps fire.
Skanopy replays a journey where everything is refused, and records what keeps going despite that refusal.
Skanopy lists the actors actually active and flags the ones the banner leaves undeclared.
Skanopy checks that both “accept” and “refuse” are actually applied by the app. A faulty setup is invisible from the outside.
Both directions are visible. The actors that fire when they should not, and the ones receiving nothing although the user accepted. The second case is revenue lost without the slightest legal upside.
The report is factual, dated and reproducible: findings, not opinions. Enough to document a compliance file.
The findings map to the recommendation’s expectations: consent before any non-essential collection, refusal as simple as acceptance, information at the right moment. Skanopy documents the facts; you judge.
I already have a consent banner. Why Skanopy on top?
Your banner collects users’ choices; it does not check, on a real phone, that the app respects them. Skanopy is that independent check. And studies show a banner often coexists with non-compliant transmissions.