FFixout
Log inFree mini-audit
About · Methodology

Built to be checked. By your counsel.

Fixout exists because subscription law fragmented into a patchwork nobody can read by hand. We built an engine that walks flows the way a subscriber does, and a review process that keeps its findings honest.

How an audit runs
01
Walk

A scripted browser signs up, attempts to cancel, and collects renewal emails, exactly as a subscriber would. No code access, nothing installed.

02
Capture

Every step is screenshotted and timestamped. If a step cannot be captured (bot protection, broken flow), the report says so; its rules are dropped, never guessed.

03
Match

Findings run against one master rules file: state, requirement, effective date, source. The file feeds the engine and the public state-law table, so both stay current together.

04
Human sign-off

A reviewer confirms the crawler found the real path, catches what a bot misses, and verifies every citation before the report unlocks. This is why reports take 24–48 hours.

05
Re-check

Monitoring re-walks the flow when it changes and when the law changes. A new statute is a reason to re-check you, not a surprise.

The boundary

Fixout produces evidence and engineering findings, not legal advice. Every finding reads "this step appears to conflict with [law]". The master rules file is reviewed by outside counsel on a schedule, and we carry errors-and-omissions insurance. Your lawyer stays your lawyer; we make their job faster.

Security and privacy
Read-only walk of your public flow
Test accounts used, never customer data
Evidence stored encrypted, deleted on request
Who is behind it

A small team of engineers and UX auditors, with outside subscription-law counsel reviewing the rules file. We publish the methodology because the product is the proof, not the mystique.

Contact us →