Files
zeekayandHanzo Dev d3a95910a9 analytics: one client, not six vendors — and stop POSTing user email offsite
social carried SIX third-party analytics vendors in one layout — Plausible,
PostHog, Dub, Facebook Pixel, Google Tag Manager and datafa.st — plus a backend
that POSTed the user's EMAIL to datafa.st/api/v1/goals on every register and
activate.

All of it was upstream (Postiz) fork residue and all of it was DEAD: every
vendor is gated on an env var (POSTHOG/PLAUSIBLE/FACEBOOK_PIXEL/GTM_ID/
DATAFAST/DUB) that is configured in no universe manifest and set on no pod, so
each guard was permanently false. Two of them even hardcoded a foreign domain,
social.com, which is not ours.

Removed, so the layout is now just the Sentry error boundary around the content.
Telemetry belongs to the ONE @hanzo/event client posting api.hanzo.ai/v1/event,
which Cloud fans server-side into the web (analytics), product (insights) and
error (sentry) lenses. One package, one tag, one door.

Also drops the now-inert datafast_visitor_id / datafast_session_id plumbing it
fed: 3 DTOs, a controller body param, and the cookie reads in register,
after-activate and first-billing. It was never persisted (no Prisma column) —
it existed only to feed the offsite call.

Zero behaviour change: nothing was configured, so nothing was firing.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-25 16:14:49 -07:00
..