How it works
A monitoring loop purpose-built for Data Protection Officers who need to keep pace with what production actually ships.
Seqlense GDPR is a monitoring loop purpose-built for Data Protection Officers who need to keep pace with what production actually ships. From an unknown surface to an auditable one, in four steps.
The scan-and-diff loop
Register your sites
Add the domains you are responsible for. Each one belongs to your organization.
Declare your vendors
Build the register of third parties you already know about, with vendor name, category and purpose.
We scan
Each site is rendered in a real browser and its full network waterfall captured. Every request host is resolved to its registrable domain.
We diff
Detected third parties are matched against your register. Anything undeclared is flagged with the exact request that introduced it.
Why it matters
A single undeclared Google Font call, analytics beacon or ad pixel can turn a compliant page into a data-transfer liability. Seqlense GDPR turns that from a periodic manual audit into a continuous, auditable signal.
Where the data lives
Two stores, split by shape and volume.
| Store | What it holds |
|---|---|
| Control plane | Your accounts, monitored sites and vendor register live in a relational database. |
| Scan data | Every captured request and third-party hit lives in a dedicated analytics store, partitioned by month for fast historical queries. |
Ready to automate it? See the full API Reference.
Overview
Seqlense GDPR - continuous third-party and consent monitoring for Data Protection Officers. Know every third party on your site, before your regulator does.
Security & data
How Seqlense GDPR handles access and data - SSO-delegated authentication, opaque sessions, and per-organization data scoping at every layer.