Pull request & codebase audits

# Find privacy risks before they reach production

Privacy risks can live in every pull request and codebase change\. Inth helps you catch them before they reach production, without leaving your existing review workflow\.

[Run a free scan](/dashboard/sign-up) · [Talk to us](https://booking.inth.com/talk-with-inth)

**Code scan**
- **Open:** PII in request logs — api\-gateway
- **Review:** New tracker: pixel\.js — marketing\-site
- **Review:** New data flow to Segment — web\-app
- **Cleared:** SDK upgraded: stripe@14 — billing

01 / Workflow

## The pull request still has the context

The author, reason and technical detail are still present\. Inth uses that context to explain what changed and which company promise it may affect\.

- **Observe the change** — Read additions and upgrades that create new collection, storage, sharing, tracking, or vendor behavior\.
- **Explain the impact** — Show the data involved, where it moves, which vendor receives it, and why the change needs review\.
- **Resolve in context** — Route the finding, propose a code fix when possible, and preserve the decision beside the change\.

02 / Capabilities

## Give engineering and compliance the same change

Developers see the finding with the code\. Privacy, legal and compliance get the context they need in Inth\.

- **Data flow mapping** — Trace personal data from collection through processing, storage, and external destinations\.
- **Tracker and SDK detection** — Spot new analytics, advertising, identity, and vendor dependencies as they enter the product\.
- **Vendor call graph** — Connect outbound requests to the service, data category, consent state, and policy record they affect\.
- **Checks in CI** — Run privacy review in the delivery workflow before the change loses its technical context\.

03 / Evidence

## Every finding stays attached to the code that caused it

Each finding becomes a durable record of the source, review, fix and final decision\.

- **Source** — Commit, pull request, file, and data flow
- **Decision** — Owner, status, rationale, and approval
- **Evidence** — Fix history and the record that closed the finding

## Run a free scan and find your privacy gaps

Find the change, get it reviewed and keep the decision with the code of production event that caused it\.

[Run a free scan](/dashboard/sign-up) · [Talk to us](https://booking.inth.com/talk-with-inth)

**Inbox**

Privacy changes that need review