Seqlense GDPR loads your pages in a real browser, the way a visitor does. Every request and every cookie is captured, each third party is named and checked against your register, and every fix is confirmed by a new scan.
Free plan: one scan a month, no card.
shop.example.com/checkoutFirst partyjs.stripe.com/v3Declaredfonts.gstatic.com/s/inter.woff2Undeclaredwww.googletagmanager.com/gtm.jsDeclaredanalytics.tiktok.com/api/v2/pixelUndeclaredshop.example.com/api/cartFirst partystatic.hotjar.com/c/hotjar.jsUndeclaredIllustration
Add a domain and its subdomains are listed. Choose the pages to scan on each host: trackers live on checkout, contact and account pages far more than on the homepage.
Each request is resolved to the company behind it and its purpose. Each cookie is classified: first or third party, session or persistent, its lifetime against the 13-month benchmark, and its security flags. Cookie values are never stored.
_gaGoogle Analytics400 dSecure_ttpTikTok395 dSecure_hjSessionHotjar30 minSecuresession_idexample.comSessionHttpOnlySecureDeclare the vendors you know, import the ones your tools already list, and declare a finding in one click. Anything that runs without being in the register is flagged.
Every undeclared or refused third party is a finding, scored out of 100. The score is the sum of written reasons, so it can be explained to a client, a manager or an authority.
Assign an owner and a due date, inside your team or outside it (your agency gets a personal link to that one task). When it is marked fixed, a scan checks the pages where it ran.
tiktok.comOwner: web agencyGive the URL of each host's cookie policy. The vendors and cookies it names are extracted, each with a quote from the page, and compared with the latest scan.
Every scan is kept with its date. See what appeared and what left, host by host, rebuild the site as it was on any day, and get an alert when something new and undeclared shows up.
tiktok.com on /checkout, absent from the previous scans.Every scan is kept with its date. Show the site exactly as it was on any past day, each host with the scan it comes from.
Who declared, blocked, accepted or fixed what, and when. Exportable for an audit.
CSV of every scan, its requests and its cookies, a PDF report, and the record of processing. The same data is available through the API.
Each check of a cookie policy quotes, word for word, the sentence it relies on, with the page and the date it was read.
No. Seqlense loads your public pages from the outside, like a visitor. Nothing to install, no tag to add.
Scans load each page as a first-time visitor who has not answered the cookie banner, so you see what runs before consent. Testing the "accept" and "refuse" paths is in development.
The addresses of the requests, the third parties and the cookies by name and attributes, never cookie values and never data about your real visitors. Scan data is deleted after a retention period, six months by default.
The whole product and one scan a month, on one page per domain. Enough to see what your homepage loads, and to try every screen.
Yes, each website is a project with its subdomains, and the dashboard ranks them all by risk. Firms advising many clients can read how firms use it.
Create a free account, add your domain, and see what it really loads.