Skip to content

A Danish software house behind a consent platform

Privaci is a Danish product built by a small software house. We would rather write down what does not work than have you find it after you have paid. So here is both the story and the honest status.

The company behind it

Company
bon.do ApS
Registration
43473425
Location
Svendborg, Denmark

Why we built it

Privaci started with a measuring instrument, not a banner. We wanted to know what a website actually sets in a browser, not what the source code says.

That turned out to be harder than it sounds. A scanner that reads through JavaScript cannot see the cookies the server marked HttpOnly. It cannot see a tracker answering on your own subdomain through a DNS record. And it cannot see fingerprinting at all, because there is no cookie to find.

So we built that part first: a real browser that opens the page once, as a visitor who was never asked, and a cookie jar read directly rather than through document.cookie. Because no banner is ever clicked, every finding is observed before consent, not inferred from whether a banner exists. The rest of the product (the banner, the log, the documentation) is built on top of that.

Privaci is developed and operated by bon.do ApS in Svendborg. The product is built for the Danish and Nordic market, and all operations and all data sit in the EU.

How a tracker is held back The tag sits in the markup without an address to fetch from. On consent it gets its address back and loads. On refusal the address is never restored, and the request never leaves the browser. In the markup <scriptsrc="tracker.js"> Parked type="text/plain" no address tofetch from Visitor decides Accepts Refuses Released andfetched tracker.js Blocked 0 requests The request never leaves thebrowser
The method behind the scan: one run, no consent click. Everything is therefore observed before consent.

Running in production today

Each line is a capability in service, with the bound we know about. We state the bound because a capability without its limitation is a claim rather than a fact.

This list is not a roadmap. Everything below is built and in use on privaci.io itself, and every line can be checked in the product.

11 capabilities in service

Status as of September 2026

  1. 01 Browser scanning A Playwright crawl that runs JavaScript like a real visitor
  2. 02 HTTP-only cookies Read from the browser cookie jar, not from document.cookie
  3. 03 CNAME cloaking The DNS chain behind every third-party host, per page
  4. 04 Fingerprinting Canvas, WebGL, AudioContext and OffscreenCanvas
  5. 05 Pre-consent blocking 148 tracker domains built in, plus per-site rules
  6. 06 Google Consent Mode v2 All four signals mapped, with no plan gate
  7. 07 Cookie declaration Generated from the scan and hosted on your own domain
  8. 08 Monthly scan cadence The site rescans itself every month, with backoff if a run fails
  9. 09 Consent log Timestamps and a pseudonymous id, without IP address or user agent
  10. 10 Team access Invitations with read or edit permission
  11. 11 WordPress plugin Installs the snippet and the declaration from wp-admin. Not yet on wordpress.org

Built by bon.do

Privaci is developed and operated by bon.do ApS, a Danish software house in Svendborg that builds software for regulated environments. We do not build generic SaaS products: every product solves a bounded problem for a bounded group of people, and this is one of them.