The Cookie scanner detects the cookies and scripts active on a URL you provide and drafts a Cookie Policy clause for each category it finds. It runs a static fetch — no headless browser — so it catches cookies set in HTML, referenced by <script> tags, inline frames, and stylesheets, but not cookies injected by JavaScript after page load.
Running a scan
- Open Cookies in the dashboard sidebar.
- Enter the URL of your website (e.g.
https://yoursite.com). - Click Scan.
miniterms fetches the page, parses all <script>, <iframe>, <link>, Set-Cookie header, and inline script patterns, then matches vendor fingerprints against its internal library.
Scan results
Results are grouped by category:
| Category | Examples |
|---|---|
| Essential | Session ID, CSRF tokens, load-balancer stickiness |
| Functional | Language preference, UI state, remember-me |
| Analytics | Google Analytics, Plausible, Matomo, Hotjar |
| Advertising | Google Ads, Meta Pixel, LinkedIn Insight Tag |
| Social | Share buttons, embedded feeds |
| Support | Intercom, Crisp, Zendesk widget |
Each result shows the vendor name, the cookie name(s) detected, and the GDPR legal basis miniterms recommends for that category.
Generating a draft Cookie Policy
After reviewing the results, click Generate draft Cookie Policy. miniterms produces a Cookie Policy section covering every detected category, with consent and opt-out instructions per vendor. The draft respects your current jurisdiction settings from the Business profile.
Click Save as draft to store it — it appears in Documents as your Cookie Policy draft.
What static scanning cannot detect
JavaScript-set cookies (those added by document.cookie after page load) are not detected in the current release. A full dynamic scan that executes JavaScript arrives in v2. If your site sets cookies via analytics or tracking scripts that load asynchronously, add those vendors to the draft manually before publishing.