Poliogo writes the code and opens a PR. You review and merge.

Policy updates shouldn't arrive as emails. Poliogo pushes a branch with the updated documents and banner wiring, opens a pull request with a plain-English explanation of what changed and why, and waits for your review.

Included on FreeGitHub · GitLab · BitbucketNothing lands unreviewed

Start free — no credit card See pricing

pull requests opened by Poliogo

Compliance update: new analytics tool detected

PostHog added to Privacy and Cookie Policy

Open

Install: privacy pages and consent banner

First-time setup — 5 files

Merged

Compliance update: AI provider detected

OpenAI retention disclosure added

Merged

A diff you can actually read

The pull request Poliogo opens when it finds a new analytics tool. The body explains what changed and which detected service triggered it, so approving is a normal merge.

poliogo/compliance-2026-09-10 → mainOpen

Compliance update: new analytics tool detected

Poliogo bot wants to merge 1 commit into main

What changed, and whyPostHog was found in package.json on 10 September. Your Privacy Policy named no analytics processor, so section 4 is rewritten and PostHog is added to the sub-processor schedule.

app/legal/privacy.mdx+6 −1

## 4. Analytics and tracking

We do not use third-party analytics.

We use PostHog to understand how the product is used.

PostHog acts as our processor under a written agreement

and stores data in the European Union.

Data collected: page views, device type, country.

## 5. How long we keep your data

All checks passed · detected from package.jsonMerge pull request

How the PR flow works

Compliance changes go through the same review your code does.

01

Included on the Free plan

Free plan

Git OAuth and automatic pull requests are on every plan, including Free. Connect a repo and your first documents arrive as a PR.

02

A diff you can actually read

The PR body explains what changed, why it changed, and which detected service triggered it — in plain English, above the file diff.

03

Its own branch, always

Poliogo writes to its own poliogo branch and opens the PR from there. Changes reach your default branch only through a pull request you approve.

04

GitHub, GitLab and Bitbucket

The same flow on all three. On GitHub it runs through a read-scoped App installation; writes are limited to Poliogo's own branch and the PR itself.

05

Triggered by real changes

A scan that finds a new tracked dependency or outbound call opens a PR; one that finds nothing legally relevant opens nothing. You trigger scans yourself on Free — paid plans run them in the background, weekly, daily, or in real time.

06

Multi-repo on Agency

Agencies can connect several repositories to a single project and get one coherent set of documents across them.

Get your policies in your repo

Connect a repo on the free plan and merge your first compliance PR today.

Start free — no credit card

Poliogo is an automated code analysis and document display tool, not a law firm. Poliogo does not provide legal advice, representation, or guarantees of statutory compliance, ADA/WCAG certification, or legal immunity. Your documents are generated from the information you and your site provide, and all legal responsibility for your site, your documents and your practices rests with you. Visual banners and generated documents are advisory tools and do not substitute for professional legal review.