First-party signal intelligence

See what finds you. Never track who.

Pulse brings sessions, search, backlinks, and AI referrals into one calm view. One 1.2 KB signal. No cookies, no consent banner, and nothing that identifies a person.

No cookiesNo persistent IDNo ad networkNo sampling
Signal consolesickfade.com · live
Visitors · 30d
1.5k
From AI
6%
Cookies
0
Stored IDs
0
AI referral signalChatGPTClaudePerplexity

Built for healthcare first

Nothing identifying. Nothing to breach, leak, or subpoena.

Our first Pulse clients were therapy and counseling practices. On those sites, “who visited this page” must never become a stored fact. So Pulse measures paths and sources—not people.

Protocol 01

No cookies. No IDs.

The anonymous visitor hash is salted and rotates daily. Tuesday cannot be linked to Wednesday, including by us.

Protocol 02

First-party only.

Counts move from your site to Pulse. No ad network or third party receives a byte about your visitors.

Protocol 03

Paths, not people.

Learn that ChatGPT sent visits to a service page this month—never who those people were.

Pulse collects nothing a visitor-identity lawsuit could be about. We say “no personal information collected,” never “HIPAA compliant”—compliance belongs to the whole practice. Our part is handing it nothing identifying to worry about. That is privacy by default in the Kalydron Standard.

Pulse versus GA4

Same category. Opposite philosophy.

SignalGoogle AnalyticsKalydron Pulse
Weight~130 KB of JavaScript1.2 KB — about 100× smaller
IdentityCookies plus a persistent client ID that links visits for monthsNo cookies, no ID — the daily hash cannot connect visits across days
Consent bannerRequired in most serious jurisdictionsNot needed — nothing identifying is collected
Your dataSampled on Google’s servers and deleted after 2–14 monthsUnsampled, first-party counts with permanent history
AI trafficBuried under generic ReferralChatGPT, Claude, and Perplexity counted by name
The dashboardGA4 — famously impenetrableThe signals an owner needs, readable in ten seconds

GA measures people because visitor profiles feed an ad machine. Pulse measures traffic: how many came, where from, and whether it is growing. Already run GA? Pulse can sit beside it and show the AI signal GA misses.

Signal path

Three moving parts. Boring on purpose.

  1. 01

    One line loads the signal

    Install @kalydron/pulse from npm, or load its pinned npm build from jsDelivr. The 1.2 KB signal is deferred and cannot block the site.

  2. 02

    A cookieless beacon counts

    Path, referrer, and a salted daily hash are the full payload. ChatGPT, Claude, and Perplexity traffic is counted by source.

  3. 03

    Search data joins nightly

    Search Console and Bing clicks, impressions, and backlinks join the permanent history without adding more code to the site.

Install from npm

One package. Then the signal is live.

JavaScript apps install directly from npm. WordPress, Squarespace, Wix, Webflow, and plain HTML can load the same pinned npm release through jsDelivr.

Open @kalydron/pulse on npm ↗
@kalydron/pulse · npm1.2 KB · zero dependencies
npm install @kalydron/pulse

No build step · pinned npm release via jsDelivr

<script defer src="https://cdn.jsdelivr.net/npm/@kalydron/pulse@1.1.0/dist/pulse.iife.js"
  data-site="YOURSITE"></script>
  1. 1 · We register the site and create its private dashboard.
  2. 2 · Install from npm or use the pinned npm CDN build.
  3. 3 · Traffic arrives in minutes; search joins after connection.

Measured in the open

Real numbers your customers can verify.

Opt-in sites receive a public verification page and live badge fed directly from measurements—not a number typed in by the owner.

Open the leaderboard

Open a channel

Find out what is finding you.

A person will scope the site, install Pulse, and connect the signals that matter.