Privacy Policy

FirstBite TV (the “Service”) is operated by KrochmanSolutions (“we”, “us”). Questions about this policy can be sent to johnkrochman@krochmanholdingsinc.com.

We collect three categories of information, all of which are aggregate and non-identifying:

• Outbound click events.When a viewer presses a “Watch the rest on [Network]” CTA we record the timestamp and the show that was clicked. We do not record the viewer’s IP, device, account, or referrer in connection with that event.
• Aggregate page-view counts(via Vercel Web Analytics). For each page view we receive: the URL path, the referring URL (when the browser sends one), a country/region derived from the IP (the raw IP itself is discarded by Vercel before it ever lands in our dashboard), and a coarse device class (mobile / tablet / desktop, browser family, OS family). No cookies are set, no cross-site identifiers are used, and the dashboard surfaces aggregate numbers only — we cannot isolate or replay a single viewer’s session. Full detail in § 06.
• Standard server access logs. Our hosting provider (Vercel) records HTTP request metadata for reliability and abuse-prevention purposes. We do not cross-reference these logs with click data or analytics data.

• We do not require accounts or registration.
• We do not collect names, addresses, or phone numbers.
• We do not run advertising or behavioral retargeting on the Service.
• We do not embed the common consumer-tracking or behavioral-retargeting pixels — there is no Google Analytics, no Meta Pixel, no TikTok Pixel, and no LinkedIn Insight tag. The two third-party tools we do use are Impact.com (affiliate attribution, § 05) and Vercel Web Analytics (cookieless page-view counts, § 06). Both are narrowly scoped and fully disclosed.
• We do not sell or trade your personal information. We do share the minimum identifiers required for Impact.com affiliate-conversion attribution with the partner whose CTA you clicked — see § 05 for specifics. Vercel Web Analytics data is processed by Vercel under their own privacy terms and is not shared with any other party.

Episode 1 of each title is delivered via an iframe embed served by the partner that owns the rights (e.g. Peacock, Internet Archive, an official YouTube channel). Those partners may set their own cookies and run their own analytics inside the player. Their privacy practices are governed by their own policies, not ours.

FirstBite TV is a free service. Our sole revenue line is the referral fee partner networks pay us when a viewer we send them transacts on their platform. The mechanism that lets those networks credit a viewer to us is the Impact.com Universal Tracking Tag — a single third-party JavaScript snippet we load on the home page of firstbitetv.com (program ID P-A7328881).

What the tag captures.The tag transforms outbound CTA links into tracked variants and records a page-load impression beacon. The data captured includes the link you clicked, a timestamp, basic technical metadata (browser, OS, language, referrer) and an Impact-issued anonymous click identifier. We do not attach a name, email, account, or phone number — we don’t collect those in the first place.

Where the data goes.Per Impact.com’s own disclosure: “Data captured via tracking scripts may be shared with advertisers.” In our case “advertisers” means the specific partner network whose CTA you clicked. Sharing is limited to the attribution data that network needs to confirm your referral originated with FirstBite TV (so they can pay us the agreed referral fee). Impact.com also processes the data on our behalf under their own privacy policy: impact.com/privacy-policy.

How to opt out. The tag respects browser-level privacy signals. To suppress it entirely, use any of the following — all of them work and none of them break the rest of the Service:

• A content-blocker extension (uBlock Origin, AdGuard, Privacy Badger). The Impact.com script is on the standard EasyList / EasyPrivacy filter lists, so all of these block it by default.
• Built-in browser protections — Brave Shields, Firefox Strict Tracking Protection, Safari Intelligent Tracking Prevention (ITP).
• Enable Global Privacy Control (GPC) — most modern browsers expose this as a setting, and the EFF’s Privacy Badger sends it automatically.

If you would like a specific attribution event removed from the Impact.com ledger, email johnkrochman@krochmanholdingsinc.com with enough detail (rough timestamp + which partner) to identify the row, and we will request the redaction from Impact on your behalf.

We use Vercel Web Analytics to count page views on FirstBite TV. We use it because it is the most privacy-preserving analytics tool we are aware of for our scale: it is cookieless, it sets no cross-site identifiers, it does not fingerprint, and the dashboard surfaces aggregate counts only — we cannot isolate, replay, or join a single viewer’s session.

What the tag captures. For each page view the Vercel Analytics script reports the URL path, the document.referrervalue (when the browser sends one), and basic device classification (mobile / tablet / desktop, browser family, OS family). Country and region are derived on Vercel’s edge from the request IP — Vercel then discards the raw IP before storing the event, so the IP never reaches our dashboard.

What it does NOT capture.No name, email, account, phone number — we don’t collect those anywhere on the Service. No persistent visitor ID. No cookies, no localStorage writes, nosessionStorage writes. No keystrokes, mouse movement, scroll depth, or session replay. No cross-domain identifiers. No data is shared with advertisers or any third party other than Vercel itself.

Where the data lives. Vercel processes the analytics events on our behalf and stores the aggregates in their U.S. infrastructure. Their data handling is governed by vercel.com/legal/privacy-policy.

How to opt out. Like the Impact.com tag, the Vercel Analytics script is on the standard EasyPrivacy / EasyList filter lists. Any of the following will block it cleanly without breaking anything else on the Service:

• A content-blocker extension (uBlock Origin, AdGuard, Privacy Badger).
• Built-in browser tracking protections — Brave Shields, Firefox Strict Tracking Protection, Safari ITP.
• The Do Not Track or Global Privacy Control browser signal (Vercel Analytics honors both — the request is not recorded when either is sent).

FirstBite TV’s own first-party storage is minimal: one localStorage key (firstbitetv-theme) for remembering whether you chose light or dark mode, and one sessionStorage key (firstbitetv-intro-played) so the brand intro animation only plays once per session. Neither is shared with any server.

Vercel Web Analytics is cookieless. It does not set cookies and does not write to localStorage or sessionStorage. The page-view events go directly to Vercel’s ingest endpoint and that’s it.

The Impact.com tag described in § 05 may set short-lived attribution cookies (typically named __irClickID, __iras, or similar) for the duration of the partner’s referral window. These cookies do not identify you personally — they identify your click so the partner can credit it back to FirstBite TV. They are cleared by the same browser privacy tools listed above.

The Service is intended for a general audience. We do not knowingly collect information from children under 13. If you believe a child has used the Service in a way that involves their information, please contact us and we will investigate.

Because we hold no account-linked data about you, there is nothing for us to look up, export, or delete on a per-person basis on our end. If you would like the aggregate click event from a specific session purged from our database, or an Impact.com attribution event redacted on our behalf, contact us with enough timestamp detail to identify the row and we will action the request. Vercel Web Analytics events are aggregated and non-identifying, so there is no per-person record to delete there — but blocking the script on subsequent visits (see § 06) prevents any future events from being recorded at all.

We may update this policy as the Service evolves. The “Last updated” date at the top of this page reflects the most recent revision. Substantive changes will be summarized in a release note linked from the footer.