Back to The Gateway

Analytics privacy

Measure launch health without building a tracking surface.

The Gateway launch measurement should stay minimal, aggregate, documented, and aligned with the privacy story.

Useful signals

Aggregate page views, CTA categories, broken links, documentation exits, and coarse browser/device layout data.

Avoid

Session replay, input capture, third-party ad pixels, cross-site identity graphs, fingerprinting, and unnecessary IP retention.

Measurement boundary

Website analytics should not become product telemetry.

Redacted Gateway dashboard showing route, DNS, tunnel, device, and backup status cards
Do not collect Operator status.

Launch analytics should measure page interest, not product state, topology, or gateway health.

Redacted Gateway devices inventory screen
Do not infer Device identity.

Coarse layout data is enough; analytics should not fingerprint visitors or infer managed devices.

Redacted Gateway DNS control screen
Do not retain Resolver context.

Website measurement should avoid DNS behavior, raw IPs, and other operator context.

Launch rule

Decide what signal matters before adding analytics.

Analytics should be added only after the project defines useful launch signals and locks the data it refuses to collect.

Open launch status