Browser Storage Check
Recognize technical storage and access signals such as cookies, LocalStorage, SessionStorage, IndexedDB and fingerprinting candidates.
Ideal for technical data protection checks beyond classic cookie lists.
Results
Technical pre-checking of a URL. For multiple URLs, templates and CSV exports, use the GDPR Tracking Audit.
Findings
Detailed hit
What the Browser Storage Check evaluated
The exam is deliberately fast and focused. It recognizes technical signals in headers, HTML, JavaScript and resources. Interactions with banners, login, forms and tag triggers should be additionally checked in the browser.
Differentiate memory access in code and stored data
Illustrative example · no measurement result of your website
localStorage.setItem('preferred_language', 'de');
A LocalStorage call is initially a technical memory signal. In the example, he could hold a language setting. However, the same memory can also contain identifiers. The tool does not read actual browser memory values.
Then check the results in the browser.
- Open the memory view of the browser developer tools and compare a fresh call with the state after an interaction.
- Document keys, value type and purpose for LocalStorage, SessionStorage and, if applicable, IndexedDB.
- Check which entries remain after rejection, revocation, logout and reopening of the browser.
What this check leaves open
Code notes are recognized in the delivered document, no executed memory operations. External scripts, dynamically composed calls and processes that can only be reached after login can be missing.
Evaluate cookie signals separately →From individual check to GDPR tracking audit
A tool shows a concrete symptom. The audit checks up to 500 URLs, prioritizes tracking, consent and form risks, and provides export data.
Targeted deepening of GDPR tracking
Check which cookies a URL technically shows, whether tracking cookie candidates appear and which attributes such as Secure, HttpOnly or SameSite are set.
Before consentRecognize tracking and third-party candidates who are already visible in the initial delivered page before a user actively consents.
Third party third partiesFind well-known tracking services, external script hosts, and third-party integrations that are relevant to consent, privacy, and tag governance.
Google Consent ModeCheck if Google tags have technical consent mode signals visible and if denied/granted hints appear in the code.
Consent UXCheck whether known consent management platforms and important banner signals such as rejection, settings and revocation are technically findable.
Web analysisCheck if a URL contains more frugal analytics candidates or marketing/tracking signals requiring consent.
Questions about Browser Storage Check
Is LocalStorage legal like a cookie?
Web storage can also be relevant for accessing information in the end device. Legal classification depends on purpose and necessity.
Can the tool read stored values?
No. It checks code and header signals of the URL. The actual memory values should be checked in the browser.
Is the individual check free of charge?
Yes. The standalone tools check a single URL. For larger crawls, complete tables and CSV export, the premium audit is planned.
Does the tool replace legal advice?
No. The tools provide technical pre-testing. Legal bases, contracts, information obligations and concrete consent flows must be subject to technical review.