LocalCMP

Why I built it

Most consent interfaces optimize for legal defensibility or conversion while asking users to interpret deliberately confusing controls.

The LocalCMP thesis is that privacy software should be locally understandable: the site owner can inspect what runs, the visitor can understand the choice, and the implementation can be audited without relying on a black box.

What I built

• A starter application with scanner, compliance manifests, snapshots, checklists, and deployment documentation.
• Product and pricing material that separates technical implementation from legal validation.

What it taught me

• Compliance interfaces should explain the decision instead of merely adding another banner.
• A software product must state clearly where technical assurance ends and legal advice begins.