YOM

For privacy-sensitive teams

Privacy-first by design, ready for your counsel to review.

YOM avoids the patterns behind recent enforcement: third-party pixels, identifiers that survive an opt-out, full URLs with personal data in them. Whether it meets your obligations is for your legal team to decide. This page gives them the facts.

Start free, no credit cardTalk to us

The exposure your counsel is weighing

upper bound of Kaiser Permanente’s settlement over trackers on logged-in pages[1]
$47.5M
CIPA wiretap claims remain available after SB 690, signed 30 September 2026[2]
§631
consent for non-essential trackers, analytics included, under Quebec’s Law 25[3]
Opt-in

How it works

The identity is dropped before it’s stored.

GPC, DNT, denied or undecided consent all lead to the same place: no visitor id, nothing in browser storage, nothing forwarded. You can go further and drop those events entirely.

Ingest · live view

conversions in view 3

Illustration of an event stream. Events from visitors who granted consent keep a visitor id. Events carrying a Global Privacy Control signal, a denied consent, or no consent decision are collected cookieless: the visitor id is removed, but conversions are still counted. Query strings are stripped and email-like fields are scrubbed.

Illustration · simulated events, not customer data

What you get today

Shipped

  • No third-party pixels

    YOM loads none. Optional forwarding to your own GA4 or Meta Pixel runs only with marketing consent, and you can leave it off.

  • Cookieless by default

    No persistent id and no storage writes until analytics consent is granted; enforced server-side too.

  • GPC & DNT at the edge

    Treated as denied: cookieless by default, or dropped if you set the policy to drop.

  • PII scrubbing

    Email-, phone-, name-, address- and card-like params are removed from browser events.

  • Path-only URLs

    Query strings and fragments never leave the browser; click ids are recorded only as present or absent in reports.

  • Access controls

    Google sign-in, multi-factor authentication, and audit logs on pay-as-you-go.

  • Opt-out evidence report

    Per event: consent state, GPC, DNT, kept cookieless, PII scrubbed, forwarding suppressed. Evidence for your own review, not a compliance certificate.

What we don’t offer today

YOM does not currently hold third-party security attestations, does not sign business associate agreements, and makes no commitment about the geographic location of stored data. Don’t send YOM data that your obligations require to be covered by those, such as health information from authenticated patient pages. See security for the full picture.

Nothing on this site is legal advice. Privacy law varies by jurisdiction and changes often; have qualified counsel review your use of any analytics tool, including YOM.

Other solutions

Sources

Third-party figures as published by the cited source. Last verified . Prices and policies change; check the source before relying on a number.

  1. [1]BankInfoSecurity, “Kaiser Permanente to pay up to $47.5M in web tracker lawsuit.” www.bankinfosecurity.com/kaiser-permanente-to-pay-up-to-475m-in-web-tracker-lawsuit-a-30180
  2. [2]Crowell & Moring, “California governor signs SB 690.” www.crowell.com/en/insights/client-alerts/california-governor-signs-sb-690-limiting-private-right-of-action-under-cipas-pen-register-and-trap-and-trace-provisions
  3. [3]McCarthy Tétrault, “Quebec's Law 25 and cookies: not so cookie-cutter.” mccarthy.ca/en/insights/blogs/techlex/quebecs-law-25-and-cookies-not-so-cookie-cutter

Start measuring

Measure what you can prove.

The first 100,000 events every month are free. No credit card, no sales call.

Start free, no credit cardSee pricing