back to EV1 Labs
Privacy.
The public site is static and intentionally low-data. It uses
cookie-free first-party metrics to understand page views, source
attribution and buyer actions without ad pixels, remarketing or
hidden lead capture.
static site
first-party metrics
local Daily Signal traces
site data
Cookie-free metrics
EV1 Labs records aggregate page, source and CTA signals through its
own Worker endpoint. It does not set analytics cookies, create
remarketing audiences or run Google, Meta or LinkedIn pixels. The
metrics script may use sessionStorage for a random per-tab session
id and first-touch UTM/referrer while you navigate the site. These
aggregate records may be stored in a Cloudflare D1 database for
first-party reporting.
daily signal
Local-only scores
The Daily Signal game may save a nickname and score in the visitor's
own browser storage. It is not a public leaderboard or server-side
account system.
brief email
You choose what to send
When you send a product brief by email, EV1 Labs receives the
context you choose to include. Do not send secrets, passwords or
production credentials in the first message.
what is measured
Small event payload
The first-party metrics event can include page path, referrer
hostname, approved UTM tags, first-touch attribution, language
route, coarse device class, section id, scroll depth, engagement
time, viewport size, link click type and the CTA event id. It should not
include email bodies, private messages, passwords, IP addresses as stored report fields,
persistent cross-session profiles or full
query strings. The report is used to understand source, page and
action patterns, not to build retargeting audiences.
client work
Privacy is part of scope
Product builds should define what data is collected, where it lives,
who can access it and what must be avoided before launch.
next signal
Send only what is useful.
A first brief needs product context, not private credentials. Keep
sensitive access details out of the first email.
Open brief