01 / 08Illustrative example
Baseline
Record how the page behaves before anything changes.
example.com/contactBaseline saved
tracker.example/collectNot observedNo tracker request observed before consent. Baseline saved.
Independent digital compliance assurance platform
Know what changed. Show the evidence.
Vakteye monitors privacy, accessibility and security as your website changes. Understand the impact, follow the fix and keep the evidence.
30-minute live site analysis.
example.com
Latest checkPrivacy monitoring
Monitoring
Independent website checks
Example findings3Findings
Needs attention2
Needs review1
FindingStatus
Tracker loaded before consent/Open
Cookie remains after rejection/contactOpen
Privacy notice needs review/privacyReview
EvidenceExample finding
Tracker loaded before consentNext stepReview consent setup
Follow-upRetest the affected page
Spot tracking before consent.
See what loaded, when it loaded, and which consent choice was in place.
- Observe
- Investigate
- Understand
- Alert
- Remediate
- Verify
- Prove
Selected checks related toGDPRePrivacyWCAG 2.1 AANIS2and more
The cost of non-compliance
€6.11 billion in GDPR fines.
Around €6.11 billion across 2,685 recorded fines in Europe since 2018, according to the CMS report. Reporting cutoff: 1 March 2026.
Source: CMS Enforcement Tracker Report 2026A new script or a changed consent banner can change where visitor data goes. Ongoing checks help your team spot the change.
See how Vakteye worksA real example · AvanzaSEK 15 million
In June 2024, IMY fined Avanza after personal data was transferred to Meta through incorrectly enabled pixel features.
Read the IMY announcement · 25 June 2024Pixel features enabled
Additional functions were enabled by mistake.
Customer data transferred
Data included account numbers and securities holdings.
The pixel is disabled
Avanza disabled it when the incident became known.
IMY issues its decision
The authority imposed a SEK 15 million fine.
When something changes, know what happens next.
Vakteye follows digital compliance issues from the first change to a checked fix, with evidence at every step.
Scroll to follow the finding
02 / 08Illustrative example
Something changes
A new tracker starts loading before a consent choice.
example.com/contactChange observed
tracker.example/collectA new tracker request appears before a consent choice.
03 / 08Illustrative example
Vakteye detects it
Compare with the baseline and flag the new request.
example.com/contactFinding detected
tracker.example/collectThe new request differs from the recorded baseline.
04 / 08Illustrative example
Evidence collected
Keep the request, page and consent state together.
example.com/contactEvidence attached
Tracker loaded before consent
Request URL, page and consent state saved with the finding.
05 / 08Illustrative example
Compliance impact explained
Explain why tracking before consent needs review.
example.com/contactReview needed
Tracker loaded before consent
A tracker ran before consent. Review its purpose and consent requirements.
06 / 08Illustrative example
Owner notified
Route the finding through your configured notification workflow.
example.com/contactNotification sent
Tracker loaded before consent
Case update sent to the configured webhook for routing to the owner.
07 / 08Illustrative example
Fix
Your team makes the change and reports the fix.
example.com/contactAwaiting retest
Tracker loaded before consent
Fix reported by your team. Verification is still pending.
08 / 08Illustrative example
Automatic retest
A connected deployment triggers a retest of the affected page.
example.com/contactResolution verified
tracker.example/collectNot observedDeployment triggered a retest. Tracker absent; required page coverage complete.
Illustrative privacy case with notifications and a deployment hook configured. The retest verifies this finding on this page, not the whole website.
Coverage
Know what your website is doing.
Watch privacy, accessibility and security. Keep the evidence connected as things change.
Privacy and consent
Compare trackers and browser requests across consent choices. Spot when a rejection is not respected.
Accessibility
Check labels, contrast and page structure. Find barriers that make your website harder to use.
A label is missing
Accessible nameNot provided
Without a name, a screen reader cannot identify what this field is for.
Website security
Check headers, TLS and exposed information. Give your security team a clear starting point.
GET /contact200 OK
01HTTP/2 200
02content-type: text/html
03strict-transport-security: …
04content-security-policy:—
Inspect the response to see which header needs attention.
Evidence ledger
Link each finding to the reported fix and retest. See what changed and what remains open.
VKT-00101
What the browser did
The request, page, and consent state captured together.
Interactive illustrations, not live scan results. Checks cover selected website behaviours and controls. Legal compliance and full accessibility conformance require broader assessment.
Findings your team can act on
Know what happened. Know what to do.
Each finding brings the evidence, suggested action and follow-up into one place.
Finding detailsIllustrative example
example.com / contact 01
A tracker loads before consent.
- What was found
- A request to a tracking service was recorded before a visitor made a consent choice.
- What to change
- Review the tracker configuration and the consent rules that control it.
- What happens next
- Report the fix and retest the same page and consent scenario.
Evidence stays attached to the finding.
Human review
Evidence first. Human judgement where it matters.
A browser records what happened. A reviewer considers the context. Keep both in view when deciding what needs attention.
Review recordIllustrative example
Privacy finding
A tracker loads before consent.
Observation
A tracking request was recorded before a consent choice.
Context to review
Tracker purpose, consent settings and the affected page.
Review status
Awaiting human assessment
Start with the recorded behaviour. The browser request is attached to the finding.
Observation and assessment stay distinct.
Vakteye observes and follows up
Monitor the agreed pages, collect evidence and retest reported fixes.
A reviewer assesses the context
Where human review is included, an analyst assesses findings that need judgement and records the decision.
Your team makes the change
Your website owner or development team implements the fix. The next check records the result.
Professional and Enterprise include human verification of lower-confidence findings by default. Essentials does not. Your agreed scope governs delivery. Compare review options.
Evidence ledger
Every change has a history.
See what was found, what your team changed and what the retest established. The original evidence stays connected.
Tracker loaded before consentIllustrative history
Open finding
An observation with evidence.
A browser request showed the tracker loading before a consent choice. The page, scenario, and capture time are recorded.
Browser request · Screenshot · Timestamp
Explore the retest outcome
A verified resolution applies to the specific finding and retest scope. It does not certify the entire website.
A note from KeyMan
After 25 years with Sweden's biggest organisations, I know what executives need to manage compliance risk.
At KeyMan, we've spent decades placing IT and security specialists with banks, government agencies, and municipalities across Sweden. Compliance has moved from a quiet legal concern to one of the most serious questions on the executive table.
Mats MårtenssonCEO, KeyMan
For leadership
A summary of what changed and what needs attention.
For the review team
Evidence and review status kept together.
For the next question
A recorded history to support internal and external reviews.
For legal, security and procurement
The details behind your decision.
Review how Vakteye handles information, what the service covers and which terms apply before you get started.
Data and retention
Read what information is collected, why it is processed and how retention is described.
Read the detailsHosting and subprocessors
Review the published functions and regions, and how to request the named provider schedule.
Read the detailsSecurity and reporting
Find our vulnerability reporting process and the security contact.
Read the detailsNeed to assess access controls, processing locations or retention for your deployment? Request the current supporting information with your scope review.
Data processing termsAsk a procurement questionBefore you start
A few practical answers.
What do we need to get started?
Start with your website address and the pages or journeys that matter. During the scope review we agree domains, monitoring frequency and review needs. Domain verification is part of activation.
How often does monitoring run?
Essentials defaults to monthly scans. Professional and Enterprise default to weekly scans. Daily monitoring can be agreed in a custom scope. Ongoing monitoring means repeated checks on that cadence, rather than an uninterrupted observation of every visit.
Who reviews findings and fixes issues?
Professional and Enterprise include human verification of lower-confidence findings by default. Your website or development team implements changes. Review coverage and any additional services follow the agreed scope.
What does a verified fix mean?
The relevant page and scenario have been checked again, the finding was not observed and the required check completed. Incomplete checks stay inconclusive. Verification applies to that check and time; it does not certify the whole website as legally compliant.
Start with your website
See what is changing on your website.
In a free, 30-minute analysis, we look at your website, explain the findings and discuss what to monitor next.