Consumer-law review for subscription paywalls

Audit your paywall before a regulator does

One screenshot in, one verdict out, in the law of every market you sell in.

Reviewed against

FTC Act §5ROSCADMCC Act 2024Consumer Contracts RegulationsUCPD 2005/29/ECCRD 2011/83/EUDSA Art. 25

Method

From one screenshot to a verdict cited in law

Submission

paywall-annual.pngPNG · 1.4 MBFine print in frame
MarketsUSEUUK
Ad hooks“Lose 10 kg in 30 days”“Plans from $0.44 a day”
01

Submit the evidence

One screenshot of the paywall as someone actually sees it, plus the context that makes it readable: the ad hooks that drive traffic there, your markets, and how billing and cancellation really work.

Session in progress

Node 8 of 10
01Scope gateDone
02ExaminerDone
I–VPattern checksDone
08Legal dossierWorking
09CounselWaiting
02

The council deliberates

Ten nodes work the submission. A scope gate confirms it is a paywall, an examiner reads the pixels, five pattern checks run in parallel, then the dossier routes the law of each market you sell in.

Verdict

Issues found

Risk

Medium
High severityUS · EU
Renewal price not disclosed before commitment
ROSCA §8403 · Directive 2011/83/EU, Art. 6
Medium severityEU
A paid add-on is preselected
Directive 2011/83/EU, Art. 22
03

You receive a verdict

A fixed eight-section report. Every finding carries the norm it breaches, the liability it creates, the correction that closes it, and a confidence line stating what could not be established.

Coverage

What the council reads, and what it leaves out

In scope

  • The paywall screenshot, read line by line, including the fine print.
  • The ad hooks you declare, checked against what the paywall promises.
  • Your declared billing and cancellation terms, checked against what is visible.
  • The law of each market you select: United States, European Union, United Kingdom.

Out of scope

  • Payment network and app-store policies.
  • Your contracts, terms of service or privacy policy text.
  • The checkout sheet and post-purchase receipts, unless you supply them.
  • Markets outside the three the engine routes today.

Scope

Three layers in every review

The patterns on the screen, the law they breach, and what a breach can cost.

68 patterns in 5 families

Each pattern carries detection cues and false-positive traps, so a finding rests on what the screen shows, not on a label.

Disclosure25
Pressure25
Upsell7
Consent6
Cancellation5

Three promises about your material

Privacy first

No client material is used to train models, and nothing is sold to data brokers.

Your data, your call

Screenshots are kept as paywall examples only, and detached from your account on request.

Not legal advice

Every finding cites its norm so your counsel can check the reasoning, not trust it.

Open source

Every rule the council applies is public

The council itself is open source under MIT: the engine that reads a paywall, the pattern catalogue, the legal norms, the routing between them and the tests that hold each verdict to its sources. Read how a finding is reached, run it yourself, or disagree with it in the open.

View on GitHub
patterns.yml68 patterns
norms.yml25 norms
jurisdiction_routes.yml40 routes
enforcement_outcomes.yml29 outcomes

Start with five free reviews

Five rounds are credited the moment you sign up. A review takes about a minute and is saved to your history, with no card and no sales call.

Sign up and start
AppLaw · Is your paywall legal?