CMP42 // TRUST // ZERO TRACKINGDEEP DIVE 03 OF 03
// Trust · Zero tracking

WE COUNT THE PAGE.
NOT YOU.

You did not click away a consent banner to read this page — because there is nothing to consent to. No cookies, nothing stored in your browser, nothing loaded from a third party. And we still know how many people read this. Those two facts are not in tension; most of the web just never tried.

// On this website

WHAT THIS SITE DOES NOT DO.

Every item below is a deliberate absence. None of it was removed after a privacy review — it was never added. What the site does do is count page views, and the list is the reason that needs no permission from you.

  • No cookies. Not for analytics, not for preferences, not for “essential” session state.
  • Nothing stored in your browser. No local storage, no session storage, no IndexedDB. Close the tab and nothing of this visit remains on your device.
  • No fingerprinting. No canvas, font or device probing to recognise returning visitors.
  • No third-party scripts. No tag managers, chat widgets, embedded videos or social buttons. The one script this site loads — the page counter — is served from this server, not from an analytics company.
  • No fonts from CDNs. Typefaces are served from this server, so no font provider learns your IP address.
  • No recognising you. The counter turns your IP address and browser version into a one-way hash with a salt that is thrown away daily. After 24 hours, nobody — including us — can tell that two visits were the same person. Across two devices, nobody ever could.
  • No profile, no funnel on a person. We see that an article was read 400 times and that 9 readers reached the application page. We cannot see which 9, or what any one of them did.
// How it is enforced

A POLICY THE BROWSER ENFORCES.

Promises in a privacy policy are easy to break by accident: one marketing tag added on a Friday, and the site tracks. So this website is served with a strict Content Security Policy — an HTTP header that tells your browser which sources it may load resources from.

The policy allows resources only from this site's own origin, and exactly one inline block identified by its cryptographic hash. Scripts injected from anywhere else are refused by the browser itself, inline style attributes are blocked, and connect-src 'self' means nothing on this page can open a connection to another host. Adding a tracker would not just be against our rules — it would visibly break.

The page counter lives inside that constraint rather than beside it: the script is fetched from this domain and its events are posted to this domain. Our server passes them on. That is why the network tab in step 3 below shows no analytics host — and why the policy did not need an exception for it.

Content-Security-Policy · production header (deploy/nginx/security-headers.conf)
default-src     'self';     # only this origin
script-src      'self'      # no script from any other host
                'sha256-…'; # plus one inline block, pinned by hash
style-src       'self';     # no inline styles, no CDN CSS
img-src         'self' data:;
font-src        'self';     # fonts served locally
connect-src     'self';     # events go here, never to an analytics host
object-src      'none';
frame-src       'none';
frame-ancestors 'none';
base-uri        'none';
form-action     'self' mailto:;
upgrade-insecure-requests
// Why this matters

NO STORAGE. NO CONSENT NEEDED.

In Germany, § 25 TDDDG (the Telecommunications Digital Services Data Protection Act, formerly TTDSG) implements the EU ePrivacy rules: storing information on a user's device, or reading information from it, requires consent — unless it is strictly necessary for the service the user asked for. Cookies, local storage, tracking pixels and fingerprinting all fall under that rule.

The consent banner that covers half the web is the result. It is not a feature; it is the legal cost of storing things on your device. This site stores nothing on your device and reads nothing from it, so there is no consent to ask for — and no banner. That is the whole trick, and it is available to anyone: the banner is not the price of knowing your numbers, it is the price of wanting to recognise people.

The GDPR points the same way. Data minimisation (Art. 5(1)(c)) means not collecting what you do not need. A page count tells us which article was worth writing. Knowing how you scrolled it would tell us nothing we could act on, so we did not build the machinery to find out — and machinery that does not exist cannot leak, be subpoenaed or be sold.

// In the product

THE SAME RULE INSIDE CMP42.

The CMP42 product follows the same posture: no third-party analytics, no fingerprinting, no session replay. Your team's interactions with your CRM are not a data source for anyone else.

What CMP42 does record is for you: the audit trail of every write, the run history of every process, and token cost accounting per process and per run. That is observability of your agents — not surveillance of your users.

The managed tier collects three narrowly scoped, first-party data points — all documented, none analytics: structured error logs with request context (URL, HTTP status, timestamp) and no user content or model payloads, kept 30 days for debugging; usage metering aggregated per workspace at the endpoint class, storage-GB and process-run level, kept rolling 12 months for billing; uptime checks from a handful of external nodes hitting the health endpoint, with no real user traffic. No analytics panel. No session recording. No behavioural tracking of your users. Customers who want cookie-free web analytics for their own admin UI can opt in to Plausible Analytics pointed at their own instance — nothing runs unless the customer switches it on. The self-hosted image sends nothing outbound at all. This website uses the same tool for its own page counts, under the terms described above; that is a property of cmp42.com, not of your tenant.

// What we do receive

ONLY WHAT YOU SEND.

The only personal data we receive through this website is what you choose to send: an email to hello@protagx.com, or a Design Partner application. Details, lawful bases and your rights are in the privacy policy.

// Do not take our word for it

VERIFY IT IN 60 SECONDS.

  1. Open your browser's developer tools (F12, or right-click → Inspect).
  2. Open the Application (Chrome, Edge) or Storage (Firefox) tab and look at Cookies and Local Storage for this site. They are empty — including after the page counter has run.
  3. Open the Network tab and reload the page. Every request goes to this site's own domain — no analytics hosts, no font CDNs. You will see /js/script.js and a /api/event request: that is the counter, on our domain, not somebody else's.
  4. Look at the response headers of the page request and find Content-Security-Policy. connect-src 'self' is the line that makes a beacon to a third party impossible rather than merely forbidden.
// Questions on this

What people ask here

The same answers as in the CRM FAQ, next to the case they belong to.

TRU-04

Does CMP42 train AI models on our data?

No. CMP42 does not train on your data and does not ship a model of its own that could. You bring the model you trust.

Prompts and sources for this question

All 43 questions in the CRM FAQ