Skip to content
privaci .io — home
Dansk

Changelog

What shipped, and when. The log is short because it only contains things that work in production today.

Nothing goes in the log until it actually works. Plans and wishes do not belong here. We write about those once they have shipped. If you are unsure whether something is in today, ask us.

  1. New website

    • privaci.io has been rebuilt from the ground up, with Danish and English content on separate addresses.
    • The site loads our own consent snippet from cdn.privaci.io. We run the same product we sell.

  2. Cookie policy and site identity

    • Site identity and cookie-policy versioning are now in place in the API.

  3. The crawler as an ordinary visitor

    • The crawler visits pages as a normal visitor and works within a realistic page budget.
    • Page URLs are normalised in one place, so two findings on one page are not counted as two pages.

  4. DNS findings in the report

    • DNS and email findings are now stored and shown on the scan page instead of only feeding the classification.

  5. Google Consent Mode v2

    • All four signals (ad_storage, analytics_storage, ad_user_data and ad_personalization) are mapped from the categories the visitor actually chose.
    • The signal mapping is configurable per site in settings.

  6. Team access

    • Per-site invitations with read or edit rights, so an agency can manage several sites without sharing one login.

  7. Pre-consent blocking and the cookie jar

    • Pre-consent blocking: tracker scripts, iframes and pixels are parked before the browser fetches them. 148 tracker domains are built in, plus per-site rules from the scan.
    • HTTP-only cookies are read from the browser’s own cookie jar rather than through document.cookie.
    • The scan phase is stamped as a constant on every observation, so a finding cannot be reclassified afterwards.

  8. The scanner: browser, DNS and fingerprinting

    • Browser scanning: a Playwright-based crawl that runs JavaScript and lets the page behave the way it behaves for a visitor.
    • CNAME cloaking: the DNS chain behind every third-party host name is followed and reported.
    • Fingerprinting: Canvas, WebGL and AudioContext are reported as their own findings, not as a footnote under cookies.

  9. The consent log

    • Consent actions are recorded with a timestamp, a pseudonymous visit ID and the categories chosen, without IP address or user agent.