Staging — blog preview only.
Skip to content

No analytics on the marketing site

Scheduled

1 min read By NT²

A privacy product should not ask you to accept tracking just to read its privacy promise.

The first contact matters

Before someone stores a seed phrase or bank detail, they visit the website. They read the positioning, pricing, privacy page, and maybe a few stories like this one.

That visit is already a trust moment.

If the page loads a stack of trackers, pixels, and third-party scripts, the product has taught the user something before the copy begins: we say privacy, but first we measure you like everyone else.

NT² chooses a stricter line for the marketing site. No third-party analytics.

Less measurement, more consistency

This does not mean marketing teams stop caring whether pages work. It means the measurement appetite has to fit the product promise.

NT² Vault is local-first and zero-knowledge. The app is designed so servers cannot read vault contents. The public site should not undermine that posture by making casual surveillance feel normal at the front door.

The benefit is partly technical, but mostly moral clarity. A visitor can read about privacy without becoming a profile assembled by external scripts.

Trust is made of small choices

No analytics is not the whole security story. Encryption, key handling, backups, and sharing design matter much more once a vault exists.

But trust is cumulative. A company that avoids unnecessary tracking on a marketing page is practicing the same restraint it asks the product to practice with vault data: collect less, know less, depend less on invisible third parties.

That is the kind of consistency NT² is trying to build.

Read the broader privacy posture at nt2.me/privacy, or follow new stories through the RSS feed.

Last updated 2026-08-28

Related stories