Skip to content
Product For law firms Guides Pricing Sign in Start free
For law firms and external DPOs

Every client website.
One view. Evidence you can file.

Seqlense GDPR watches the websites of all your clients, every page and every subdomain. It ranks what needs your attention with a score you can explain, has the fixes verified by a scan, and keeps a dated record of what ran, when.

Free plan, no card. Scan data stored in the EU.

Domains by risk
shop.client-a.exampleRetail client
0
Critical
www.client-b.exampleInsurance client
0
High
portal.client-c.exampleHealth client
0
Medium
www.client-d.exampleIndustry client
0
Low
jobs.client-e.examplePublic body
0
Low
+2 undeclared since last scan
Fix verified by scan

Illustration with fictitious clients

Every page, every subdomainUp to ten pages per host, all hosts of a client in one project.
A score with its reasonsEach point written out, nothing guessed, unknowns shown as unknown.
Fixes proven by a scanA task closes only when the third party is gone.
A dated recordThe state of a site on any past date, ready for the file.

Your clients' sites change every week. Their records do not.

Marketing adds a tag, an agency installs a plugin, a theme update loads a font from a third-party server. Nobody tells the DPO, and the register describes a site that no longer exists.

Tags nobody declared

A tag manager loads an ad pixel on the checkout page only. It is not in the register, not in the cookie policy, and fires before consent.

Fonts and assets from abroad

A font served from fonts.googleapis.com sends every visitor's IP address to Google, the case the Munich court ruled on in 2022.

"Fixed" that is not

The agency says the tracker is gone. Six weeks later it is back after a deployment, and no one looked again.

From the portfolio down to the request that proves it

Risk, justified

A score out of 100, and every point explained

Findings are ranked by a score you can defend in front of a client or a supervisory authority. Each point has a written reason; what cannot be assessed is shown at zero, never guessed.

  • Category of the third party: advertising and session replay weigh most
  • Declared in the register, refused, or not declared at all
  • Cookie lifetime against the 13-month benchmark
  • How widely it runs, and whether its fix is overdue
doubleclick.net · why this score
Category: advertisingProfiling across sites
+40
Not in the vendor registerNo documented legal basis (Art. 30 GDPR)
+15
Cookie lifetime 540 daysLonger than 13 months
+15
Remediation overduePast its due date
+10
Runs on 2 hostsOne point per host
+2
ConsentNot assessed yet, shown as such
0
Total, critical0
Remediation

Fixes are verified by a scan, not taken on trust

Every finding is a task with an owner, a due date and a history. When someone marks it fixed, Seqlense scans the pages where the third party ran.

  • Closed only if the scan no longer sees it
  • Reopened on its own if a later scan finds it again
  • An accepted risk needs a justification and a date to reassess it
  • Every step dated, attributed and kept in the audit trail
Remediation task
OpenIn progressFixedVerifyingVerified
hotjar.comDue 28 Nov
[email protected] Removed the tag from the tag manager.
verification Scan of shop.client-a.example started.
Checking 4 pages where it ran...
Your client's agency

Assign the fix to the people who can make it

The owner of a task can be outside your firm and outside your client: their web agency or developer. They receive a personal link to that one task, with what to remove and where.

  • No account needed, no access to anything else
  • They comment and mark the task fixed; the scan decides
  • The link stops working when the task is reassigned or closed
Seqlense GDPR · Task assigned

Remove hotjar.com

You have been asked to remove a third party that is loaded without being declared in the organization's register.

WebsiteClient A (shop.client-a.example)
Due28 November
Open the task
Cookie policy check

What the policy says, against what actually runs

Point Seqlense to a site's cookie policy. It lists the vendors and cookies the page names, each with a quote from the page, and compares them with the latest scan.

  • Running but not in the policy: the finding
  • In the policy but never seen: the policy is out of date
  • Nothing invented: an item without a matching quote is dropped
Policy vs last scan
Named in the policy
Google Analytics
Stripe
Criteo
Seen by the scan
google-analytics.com
stripe.com
tiktok.com
tiktok.com runs on 3 pages and is not mentioned in the policy.
History and evidence

The site as it was on any date

Every scan is kept with its date. Pick a day and see the site as it was: which third parties and cookies ran, on which host, according to which scan. What changed between two scans is listed host by host.

  • Exports of every scan, its requests and its cookies
  • A record of processing (Art. 30 GDPR) built from the register
  • An audit trail of who did what, and when
  • Alerts by email, Slack or Teams when something new appears
Third parties per scan
Undeclared at the timeDeclared

From the first scan to continuous monitoring

Map the client

Add the client's domain: its subdomains are listed, and you choose the pages that matter, such as checkout, contact and account.

First findings

The first scan gives the list of third parties and cookies, ranked by risk, with the request behind each one.

Remediate together

Assign each finding to the client's team or agency, with a due date. Fixes are verified by a scan.

Keep watching

Scheduled scans and alerts catch what the next deployment brings, and the history keeps the proof.

Findings that map to the law, with the sources

Data in the EU

Scan data is stored on servers in the European Union. Every provider is listed with its role and location on the subprocessors page.

AI that shows its work

AI helps name unknown third parties and read cookie policies. It never decides alone, and its results are marked as AI, never presented as verified.

No visitor data

We load your clients' public pages ourselves, the way a visitor would. Cookie values are never stored, and we receive nothing about real visitors.

What firms usually ask

How many client websites can we monitor?

As many as you need. Each client website is a project with all its subdomains, and every project appears in the portfolio view ranked by risk.

How is it priced?

Usage is counted per scan. For a firm with a portfolio of clients we agree terms together: talk to us.

Can our clients log in?

Today your firm works in its own workspace, and your clients' teams or agencies receive personal links to the tasks assigned to them. Read-only access for clients is on our roadmap.

Does it test the consent banner?

Scans load each page as a first-time visitor who has not answered the banner, so what runs before consent is what you see. Clicking "accept" and "refuse" and auditing the banner itself are in development.

What language is the product in?

This website and the guides are in English, German and French. The application is in English today.

Where is the data, and who processes it?

Scan data is stored in the EU. The full list of providers, their role and their location is on the subprocessors page. Scan data is deleted after a retention period, six months by default.

See your own clients' websites in it

In 20 minutes we scan one of your clients' sites live and walk you through the findings, the score and the remediation.