Menu

Watch now

A FICTIONAL SATIRE | NOT A REAL GATHERING · MADE WITH AI

The fine print. In full view.

Privacy

Your data is not a plot twist. The unredacted guide to cookies, videos, support payments and the LSJ inbox manifest.

A FICTIONAL SATIRE | NOT A REAL GATHERING · MADE WITH AI

Effective / updated October 14, 2026

Welcome to the privacy file for littlestjeffs.com, an independent project operated by founder and creator Daniel Lukich. The interviews are fictional. Your privacy choices are real. For personal data we control through this website and correspondence, contact ImNotJeff@littlestjeffs.com. MR. DIAMOND has been excused from answering this one.

The unredacted summary

  • You clear the optional cookies for landing. Advertising cookies require consent. Hosting and security services may process technical information necessary to deliver and protect the site.
  • The audience counter is optional. Google Tag Manager, Google Analytics, Google Ads and Meta Pixel load according to your separate analytics and advertising choices. Rejecting optional cookies keeps the site fully usable. No velvet rope. No suspiciously exclusive guest list.
  • No visitor account. No secret membership card. Email updates are optional and do not create a login.
  • JOIN LSJ requires two yeses. Request updates, then press the confirmation button in our email. Only then do you join the confirmed list. Being mentioned in a file does not count as subscribing.
  • External links are marked exits. YouTube and social links take you to services with their own privacy policies. Their paperwork travels separately.

Hosting: the control tower

Cloudflare serves the site’s static files and helps keep abusive bots off the runway. When you load a page, it processes basic technical information such as your IP address, browser type, requested page and request time to deliver and secure the site. Necessary security mechanisms may use cookies or similar storage.

We use hosting logs to keep the site running and secure. We do not combine them with payment or marketing profiles. The control tower needs to see incoming traffic; it does not need to cast you in the next episode. Cloudflare explains its own handling in its privacy policy (opens in a new tab).

Videos: press play, open the file

Artwork and locally hosted media make requests to the site’s media hosting when they load. The opening film and other YouTube players load only after you choose to load a video. The dramatic entrance requires your click.

We use YouTube’s privacy-enhanced youtube-nocookie.com player. Playback can still send technical and viewing information to YouTube. Privacy-enhanced does not mean invisible. YouTube and external social services apply their own privacy policies.

Cookies: your clearance, your call

The cookie desk offers Accept all, Reject optional and separate choices for analytics and advertising. Necessary hosting and security storage is separate. An old yes to analytics is not a new yes to advertising. Even our fictional press office understands that sentence.

Use Cookie preferences in the footer to change or withdraw consent. We remember your choice locally for up to 180 days. Withdrawal disables measurement, removes accessible first-party analytics and advertising cookies, and reloads the page. Do Not Track and Global Privacy Control signals prevent optional measurement from loading.

Analytics: counting the audience, with permission

If you allow analytics, Google receives technical and usage information such as page paths, device and browser information, and visit events. It may store analytics cookies. Google Tag Manager (GTM-WFH63SXG) manages loading according to your choices.

Google signals and Google advertising personalization are disabled. We omit URL queries and fragments from the page-view data we send. We never send wallet addresses, payment amounts, email addresses or newsletter registrations to Analytics. Google describes its retention and processing in its privacy policy (opens in a new tab).

Advertising measurement: the publicity department

Only if you separately allow advertising measurement, Google Ads (AW-18509441409) and Meta Pixel (1099472759378409) receive browser and device information, page visits and advertising attribution information. They may use cookies such as _gcl_*, _fbp and _fbc. Personalized Google advertising is disabled.

Meta receives PageView, ViewContent on episode and trailer pages, and Contact when you click an external support checkout or copy a manual receiving address. A support click confirms a click, not a payment or investment. Our accountants have requested that we keep that distinction.

We do not configure automatic advanced matching or send wallet addresses, payment amounts, email addresses or contact-form contents as event parameters. Third-party SDKs may still process the current page URL and their own identifiers.

After verified email confirmation, Meta receives a Lead event only with advertising consent. It contains neither your email nor your confirmation token. Confirmation and unsubscribe links themselves load no tracking. Signing up is not permission to follow you down every corridor.

The server copy: one event, not two sequels

With advertising consent, our Cloudflare Worker also sends PageView, ViewContent and Contact events to the same Meta dataset through Conversions API. These include the event time, page path without queries or fragments, your IP address, browser user-agent and valid Meta attribution cookies if present.

A shared event identifier lets Meta deduplicate browser and server copies. We do not send subscriber emails, wallet addresses or payment amounts through this connection. Lead remains a browser event after verified email confirmation.

Server measurement also requires advertising consent and respects Do Not Track and Global Privacy Control. Temporary hashed event and abuse-prevention counters expire automatically. The access token stays encrypted in Cloudflare and is never delivered to browsers. Meta explains its processing in its privacy policy (opens in a new tab).

Support: follow the money, not the visitor

Supporting the show in crypto — USDC on Base, DOGE, SOL, XRP, BTC or ETH on Ethereum — takes place through an external checkout or a direct transfer on a public blockchain. This website does not connect your wallet, request private keys or make blockchain requests on your behalf. MR. DIAMOND remains admirably uninvolved in wallet security.

We may receive payment status and public transaction details for reconciliation and applicable recordkeeping. Blockchain transactions are public and permanent by design: anyone can look them up. We do not link visitor analytics to wallet addresses.

Fixed USD support links open MoonPay Commerce on moonpay.hel.io. Wallet connection, payment details, conversion and transaction processing happen on that provider’s page. This site adds no wallet SDK and receives no private keys or card details. Manual USD suggestions are display-only; those cards send no transfer amount.

MoonPay may process payer information under its own privacy policy (opens in a new tab). Read the payment file before authorizing the payment. Dramatic music is optional.

JOIN LSJ: the inbox manifest

Request a seat on the mailing list and we collect your email address, the time and version of your consent, and whether you confirmed it. Cloudflare Email Service sends confirmation emails from news@updates.littlestjeffs.com. Our private Cloudflare D1 database stores the list.

We use the list for LSJ episodes, trailers and project news. Newsletter consent is separate from cookies: rejecting optional tracking does not prevent you from joining or leaving. We do not sell the list or share subscriber emails with Google or Meta. The manifest is for updates, not an auction scene.

Confirm your seat. Leave whenever you like.

Confirmation links expire after 24 hours. Daily cleanup removes pending requests after 24 hours. Confirmed subscriptions are removed after two years unless renewed. Every future update will include an unsubscribe link; confirming removal deletes the newsletter email record. You can also request deletion by contacting us. No exit interview with the fictional press office.

To limit abuse, we temporarily keep hashed email and IP identifiers and request counters, cleaned daily after expiration. Access tokens are stored as hashes, and query strings are redacted from our Worker logs. A short, necessary HttpOnly cookie carries a one-use anonymous confirmation receipt to the success page and is then deleted.

Writing to us does not put you on the guest list

When you contact us, we receive your email address and whatever you choose to write. We use it to reply or handle the issue; correspondence does not enroll you in the newsletter. We retain it only as reasonably necessary to resolve the matter, protect the service and meet applicable legal obligations.

Your rights: no VIP pass required

Depending on where you live — for example under the GDPR, UK GDPR or California law — you can ask what personal data we hold about you and request correction or deletion. Relevant records may include your correspondence and support transaction records we receive.

Other applicable rights may include restriction, portability, objection and withdrawal of consent without affecting earlier lawful processing. You may complain to your local data-protection authority. We do not sell personal data. Optional advertising measurement shares browser and event information with Google and Meta only after advertising consent, which you may reject or withdraw.

Send enough context to identify the records. We may request proportionate verification, but never wallet secret credentials. We respond within applicable statutory deadlines and explain lawful limitations, including required financial records and public blockchain data we cannot erase. Requests are available without discriminatory treatment. “No comment” is a show motif, not our process for privacy requests.

Why we process information

Where applicable law requires a legal basis, optional analytics and advertising measurement rely on consent. Site delivery, abuse prevention and answering correspondence rely on legitimate interests or another applicable basis. Required financial recordkeeping relies on applicable legal obligations. We do not make automated decisions producing legal or similarly significant effects about visitors.

Where the file travels, and how long it stays

Providers may process data outside your country under applicable safeguards and their own policies. Hosting and analytics retention depends on provider settings and operational needs. Expiration of your browser preference does not erase provider records. We may disclose relevant information where required by law or necessary to protect the service and address a claim.

Security and younger viewers

HTTPS, access controls and deployment checks reduce unauthorized access. Absolute security cannot be guaranteed. Report security issues through Contact. We prefer bugs in the script to bugs in the security controls.

This site is not directed to children under 13. A parent or guardian can contact us to review and delete information supplied by a child where applicable.

Revised case files

If our practices change — including a new feature that needs your data — we will update this page first and change the date at the top. The revised file will be here in plain view. No dramatic shredder sequence required.

Contact: an actual answer

Privacy questions or requests? Write to ImNotJeff@littlestjeffs.com, or visit Contact. Tell us which file needs attention. Leave the passwords and private keys out of the envelope.

Back to top ↑