HeySignal
A team.blue BRAND
Home»About
About HeySignal

We built the gate the industry kept skipping.

Server-side tracking was invented to get signal back after browsers clamped down. Somewhere along the way, it also became a very convenient place to lose the consent question. Move the pixels behind a server, hand the customer a container, and let "configure consent mode yourself" do the legal heavy lifting.

We watched that happen from the consent side of the fence. Thousands of websites collecting consent properly at the front door, then leaking data through a misconfigured tag in the back. The banner was perfect. The pipeline behind it was fiction.

HeySignal exists to close that door.

The rule
No proof, no processing.
What we believe

Five things we hold as non-negotiable

Consent is a gate, not metadata.

In most tracking stacks, consent is a plain-text field that tags may or may not read. In HeySignal it is cryptographic proof, signed into every event and verified before processing. No proof, no processing.

Fail closed, always.

When something is ambiguous, broken, stale, or missing, the event is refused. A tracking system that fails open is a compliance system that fails, full stop.

Minimize by default.

Personal data is stripped unless you explicitly choose to hash or send a field, per destination, per field. The default answer to "should we forward this?" is no.

Europe means Europe.

Our edge is Bunny.net. Our databases are OVHcloud in France and Germany. An "EU region" rented from a US hyperscaler answers a different question than the one regulators and DPOs are asking.

Say what the system does.

Our docs state HTTP codes, time windows, and algorithms. Our comparisons carry sources and dates. If we haven't earned a certification yet, the security page says so plainly.

What we refuse to build

The line we hold

This industry has a genre of features we want no part of. So, in writing:

  • We will not restore cookies a browser deleted when the user never granted the matching consent. Identifier lifetimes in HeySignal extend only while consent says they can.
  • We will not "mask" events to sneak past ad blockers for users who opted out. First-party delivery keeps honest measurement alive; the gate keeps it honest.
  • We will not ship a consent dashboard that only observes violations after the fact and calls that compliance.
  • We will not quietly forward denied traffic in "anonymous mode" and let you carry the legal theory.

If a feature only makes sense when nobody is looking, it does not make sense.

Where we come from

The consent side of the fence

HeySignal is a team.blue brand, alongside iubenda and CookieFirst. We spent years on the consent-collection side, integrating every tag manager and tracking tool our customers used. That vantage point is the product: we saw exactly where consent goes to die, and built the first tracking gateway where it can't.

The name

"Hey" is the knock on the door. "Signal" is what you get after it's answered. Tracking that introduces itself before it enters felt like something the internet was owed.

✱ One more thing

Every startup has a mission statement. We recorded ours.

HEYSIGNAL ✱ HI-FI ✱ STEREO ✱ A-SIDE
VOL
0:00
4:25
BEST PLAYED LOUD
Come see the gate work.
HEYSIGNAL ✱ A TEAM.BLUE BRAND
Related