Did a video tape service provider knowingly disclose personally identifiable information concerning a consumer?
Provider role, video event, account or consumer state, identifier, recipient, request payload, and timing of the disclosure.
CIPA / ECPA / VPPA / WESCA / FSCA
got pixels?
VPPA pixel evidence
Connect the video event to the alleged disclosure.
For defense counsel reviewing a Video Privacy Protection Act claim, preserve the video journey, consumer context, identifier, request payload, recipient, and consent record. State which links the browser evidence does not establish.
Try it yourself. Open the app.
byPapaya Privacy Co.General product and technical information. Not legal advice.
Matter-specific evidence question
Did a video event and person-linked identifier reach a third party?
VideoTitle + playback event
VisitorAccount state
IdentifierDevice or account value
RecipientThird-party endpoint
ConsentInterface + choice
The short answer
VPPA evidence to preserve
For a VPPA tracking pixel lawsuit, preserve the specific video or audiovisual material, viewing event, visitor's account or consumer context, identifier, recipient, exact request payload, timestamp, consent interface, and reproduction steps. Show whether the video event and identifier appeared in the same transmission, and document any missing link.
The statute addresses knowing disclosure by a video tape service provider of personally identifiable information concerning a consumer, subject to listed exceptions. A complete factual review therefore asks separate provider, consumer, video-information, identification, disclosure, knowledge, and consent questions.
A browser run can show what the site and tracker did during the tested journey. It does not determine whether an identifier legally identifies a person, whether the visitor is a statutory consumer, whether the website is a covered provider, or whether consent or another exception applies.
Evidence ledger
VPPA evidence checklist
The report should show both the links that connect the video to the visitor and the missing facts that prevent a complete inference.
Video material
Video title, URL, page context, player state, and the specific playback or viewing event tested.
Consumer relationship
Logged-in or logged-out state, subscription or purchase context, account indicators, and facts the browser could not establish.
Identifier
Account, advertising, device, cookie, session, or other value sent with the event and evidence of person linkage.
Disclosure
Third-party endpoint, request method, initiator, timestamp, payload fields, redirect chain, and surrounding requests.
Consent
Consent copy, distinctness, choice, timing, duration, withdrawal controls, and behavior before and after the action.
Repeatability
Screenshots, agent steps, network logs, account state, and a saved workflow for controlled reruns.
Controlled browser workflow
Compare video journeys
Controlled comparisons help separate the video event from account, identifier, consent, and tracker behavior.
Define the video event
Name the page, video or audiovisual material, playback action, tracker, account state, and consent path the run will test.
Capture the viewing state
Preserve the title or URL, player state, login or subscription context, cookies, identifiers, banner, and initial network activity.
Play and inspect
Trigger the specified event and record the request timing, initiator, recipient, payload, identifier, and video fields available for review.
Compare controlled variants
Repeat logged-in and logged-out states, consent choices, identifiers, and video events where relevant. State what changed and what remained unknown.
Limits and defenses
VPPA test limitations
The technical record should document present, absent, and inconclusive facts without turning them into an automatic statutory result.
01
A video title or URL in a request does not by itself establish a covered provider, statutory consumer, knowing disclosure, or personally identifiable information.
02
A device, advertising, or cookie value does not automatically identify a specific person. Preserve the value and the evidence of any person linkage separately.
03
A logged-in state does not by itself establish the statutory consumer relationship. Record the account, subscription, purchase, or service facts available to the browser.
04
Consent analysis depends on the statutory conditions and the actual interface. A click alone does not establish that every requirement was satisfied.
05
A present-day run cannot prove historical site behavior or every browser, account, location, and consent configuration.
Questions counsel ask
VPPA evidence FAQ
Direct answers about the evidence record. Legal conclusions still depend on the statute, jurisdiction, parties, exceptions, defenses, and current authority.
What evidence matters in a VPPA tracking pixel case?
The browser record should connect a specific video or audiovisual material to a playback or viewing event, the visitor's consumer or account state, any person-linked identifier, the recipient, the exact request payload, and the consent record. Missing elements should be documented as clearly as present ones.
Does a Meta Pixel video event establish VPPA liability?
No. A Meta Pixel request carrying a video event, URL, or device identifier does not by itself establish VPPA liability. Counsel must evaluate the provider, consumer relationship, video information, personally identifiable information, disclosure, knowledge, consent, exceptions, and current judicial interpretation. Preserve both the transmission and the facts the browser could not establish.
Can the test compare logged-in and logged-out video journeys?
Yes. Separate runs can preserve account state, subscriber or customer context, cookies, device or advertising identifiers, playback events, and requests sent during the same video journey. The comparison helps identify which facts changed.
How does consent matter under the VPPA?
Section 2710 permits certain disclosures with informed, written consent that is distinct and separate from other obligations and includes withdrawal choices. A browser test can preserve the interface and request behavior, while counsel evaluates whether the statutory conditions were satisfied.
Continue the evidence review
Related pixel litigation guides
Pillar guidePixel litigation evidence guideCompare the evidence questions behind VPPA, CIPA, ECPA, WESCA, FSCA, and health-data theories.TrackerMeta Pixel lawsuit evidencePreserve the Meta request, payload, identifiers, consent state, and user journey without assuming the theory.CaliforniaCIPA pixel litigation evidenceSeparate Sections 631, 632, and 638.51 and map each theory to testable browser facts.
See the software in action
Watch Got Pixels test a browser journey relevant to your work.
Got Pixels
Build and rerun journey tests.
Set the user path once, inspect what fires along the way, and reuse the workflow when the site changes. Start in the app.
- Set a site, jurisdiction, consent choice, and journey
- Reuse the journey across consent states and site changes
- Inspect requests, payloads, and screenshots
- Share the report for legal review
Product findings support legal analysis. The software does not determine liability or compliance.
Product demo
See a VPPA workflow in the software.
Book a demo and bring a video journey, consent state, or tracking question relevant to your work. We'll show how Got Pixels runs the browser test and presents the video event, identifiers, third-party requests, and limitations.
- A product walkthrough using the tracker or legal theory you choose
- How to set the consent state and browser journey in Composer
- Where the resulting requests, authority, defenses, and limitations appear