Termly

Purpose: Helping website owners manage cookie consent and meet GDPR, CCPA, and other privacy requirements.

Inferred · not functionally tested

Audience: WordPress site owners and businesses managing website privacy compliance

Inferred · not functionally tested

Functions: Unknown

Interfaces: API: indicated (inferred, not tested) · MCP: unknown · CLI: unknown · Self-hosting: unknown

Recorded constraints: pricing: freemium · license: Proprietary · platforms: WEB · deployment: browser, cloud_managed

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: termly.io · wordpress.org. These links do not verify the individual claims.

In the Cookie consent & GDPR space, Termly takes a focused approach. Inferred · not functionally tested: It focuses on helping website owners manage cookie consent and meet GDPR, CCPA, and other privacy requirements. Inferred · not functionally tested: Termly is a B2B product aimed at wordPress site owners and businesses managing website privacy compliance. Basis unknown · not verified: Termly follows a freemium model. Basis unknown · not verified: It runs on the web.

Termly builds and maintains Termly, and it first shipped in 2012. Inferred · not functionally tested: Key capabilities include cookie banner, consent preferences, and automatic blocking. The interface is available in 4 languages, including English, Spanish, and Dutch. Inferred · not functionally tested: Catalogued interfaces include a public API.

Summary written by a language model from the project’s public pages.