Privacy Litigation, Data Flow Analysis and Expert Testimony
Follow the Personal Data From Collection to Disclosure
A privacy or biometric privacy matter comes down to what a system collected, where the data went, who could reach it and how long it was kept, and the privacy notice rarely tells the whole story. Reading the database, the application code paths, the integration settings and the retained logs shows what the system actually did, and we measure that against what the notice and the consent screen promised. GDF examiners have testified in federal and state courts, and in Rogers v. BNSF Railway we reconstructed the biometric system records for the plaintiffs.
Why Privacy Litigators Retain GDF to Trace the Data
Global Digital Forensics was founded in 1992, and its examiners have been accepted by federal and state courts, deposed and cross examined in civil and criminal matters. Founder Joseph Caruso's technology career began in 1980 and spans software development, mainframe databases, real time transaction systems, mobile devices and cellular networks, which is the background that lets him read a biometric enrollment database or a consent flow as an engineer before he explains it as a witness. His engineering training at Stevens Institute of Technology and his CISSP sit behind that reading.
In Rogers v. BNSF Railway, the first Illinois Biometric Information Privacy Act class action to reach a jury, plaintiffs' counsel retained GDF as database, data analysis and computer forensics experts. We restored and analyzed the records of the identity verification system, normalized and deduplicated the data and reported what the system held and whom it reflected. Our expert practice spans federal district court, multidistrict litigation, arbitration and ITC Section 337 proceedings.
If your matter turns on records like these, read how the Rogers v. BNSF records were reconstructed before deciding who should examine yours.
The initial consultation is free, and a senior examiner sets the plan with you on the first call.
Compare What the Notice Says With What the System Does
A privacy notice, a consent screen and a vendor contract describe intended practice. The database schema, the application code paths, the integration configuration and the retained logs describe what actually happened, and privacy litigation lives in the gap between the two. Within the agreed scope we examine configurations, data inventories, access records, application behavior, retention settings and the notices themselves, and we record the exact conditions under which every observation was made.
Take a dispute over whether a web form sent a particular field to an analytics or advertising service. The question is not whether an integration existed but which fields it carried, to which destination, under which conditions and during which period. We identify each of those elements from the record, test the current behavior where that is useful, and use version records and deployment history to establish which build was live during the class period.
Attorneys with a disputed integration can describe the field, the destination and the class period and we will say which records would need to be preserved first.
Precision About What Each Record Proves
Permission to access data is not evidence that anyone accessed it. A disclosed recipient is not a confirmed transfer. A deduplicated count of enrollees is not a count of scans. Those distinctions decide class definitions and they decide cross examination, so every opinion we offer names the record behind it and exactly what that record proves.
Where historical logs have aged out, the surviving configuration history, version records and application behavior often still carry the answer. Current testing is labeled as current testing and tied to the version history, so any reconstruction of the past stands on records rather than on assumption.
Is retention already a problem in your case? Call (800) 868-8189 and we will discuss what the surviving configuration and version records may still support.
Technical Findings a Privacy Case Can Be Built On
GDF explains the system and the records in terms a court can weigh. Before we accept an engagement we discuss the technology at issue, the disputed questions, the experience the proposed expert needs and the procedural schedule, so the retaining firm knows at the outset what can be examined and defended before the report deadline.
The written work describes data flows, retention behavior and the differences between stated and observed operation, with each factual proposition tied to its source and every reconstructed configuration traced to the version records behind it. That structure lets the court evaluate the technical opinion on its own terms.
To see how observations and opinions are separated in a report, read the digital forensics process guide before the first call.
How a Privacy Expert Engagement Runs From Scoping to Testimony
Scope
We discuss the disputed questions, the systems and data stores involved, the proposed expert's relevant experience, potential conflicts and the report and hearing deadlines, then agree on the deliverables that can be completed and defended on that schedule.
Examine
We review the available databases, configurations, application behavior and logs under the protective order that governs the matter, document every method and test condition, and keep the chain from raw record to finding intact so another qualified examiner can follow it.
Explain
We prepare the report, the exhibits and the testimony that distinguish observations from opinions, then support counsel at deposition, hearing and trial.
Deadlines decide what can be done in each step, so bring the report and hearing dates to the first conversation and we will say what fits.
Evidence We Examine in a Privacy Matter
Data inventories, database schemas and system configuration show what a system was built to hold and where. Access, sharing and retention records show who reached the data, where it was sent and how long it survived. Application tests conducted under documented conditions show what the system does today, and the privacy notices, consent screens and vendor agreements supply the stated practice that the technical evidence is measured against.
Key Engagement Deliverables
Technical findings tied to their supporting records, timelines and exhibits built for the disputed questions, and a critical review of the opposing expert's technical opinions. Reports, declarations and deposition and trial testimony stay within the agreed scope, and each opinion is written so a judge, a juror and a rebuttal expert can all find the record it rests on.
If an opposing expert's report is already on the table, ask for a scoped rebuttal review before the deposition calendar fills.
Follow Biometric and Personal Data From Enrollment to Disclosure
Biometric privacy matters raise questions ordinary data cases do not. A fingerprint or face template is created at enrollment, stored in a database, matched on each use and sometimes shared with a vendor or an integrator, and each step leaves records in different systems with different retention. We examine the scanners, the applications that use them and the databases that hold templates, images and match events, which is the same work our biometrics and identity sciences practice performs outside litigation.
The Illinois Biometric Information Privacy Act supplies the statutory context in many of these matters. Our role is to explain how the system collected, stored, used and retained the biometric data and who was reflected in those records.
The same discipline applies to personal data outside the biometric context: website and application data collection, third party integrations, consent and preference records, retention and deletion behavior, and the access records that show who reached what. In each case the examination follows the data from collection to disclosure and documents the evidence at every step.
Biometric matters have their own evidence trail, and our biometrics expert witness practice explains how enrollment, matching and vendor records are examined.
From Collection to Testimony in Four Steps
- Collect
Identify the fields, the sources and the conditions under which data entered the system.
- Process
Examine the transformations, identifiers, templates and matching that acted on it.
- Store and share
Trace retention, access and every transfer the records support.
- Explain
Present the observed behavior in terms the court can weigh.
Rogers v. BNSF Railway: Rebuilding the Biometric Records
Truck driver Richard Rogers brought a class action alleging that BNSF Railway violated the Illinois Biometric Information Privacy Act when fingerprint information was registered and used through identity verification systems at Illinois rail facilities, and the matter became the first BIPA class action to reach a jury trial. Global Digital Forensics was retained for the plaintiffs as database, data analysis and computer forensics experts.
Our work restored the identity verification database, normalized and deduplicated its records and reported which biometric information the system held and whom it reflected. The jury found 45,600 violations and the district court entered judgment for $228 million; the court later vacated the damages award and ordered a new trial limited to damages while leaving liability in place, and the parties' settlement agreement provides for a $75 million fund. Read the Rogers v. BNSF case study and the linked court records.
Bring the devices, accounts and dates involved to a free first call. Start the conversation here.
Technical references
The statutory text most often at issue in biometric privacy matters is published by the Illinois General Assembly as BIPA section 15.
Meet the Expert Behind the Opinion
Joseph Caruso, founder, CEO and CTO of Global Digital Forensics, brings the database and systems background to privacy matters. His selected case experience includes Rogers v. BNSF Railway, and his class action work has covered reservation systems, mainframe databases, source code and transaction systems, the same kinds of records a privacy matter turns on. Meet the GDF team, then ask for a current CV. Availability and conflicts for the proposed expert are settled before any disclosure is drafted.
Want to know who would testify? Ask which expert would be proposed for your matter and we will confirm availability and conflicts before any disclosure is drafted.
Prepare for the scoping call
Gather the Records a Privacy Expert Will Ask For
A privacy examination starts with the data inventory, the notices and consent records, the integration settings and the retention schedule. Choose a guide, give each record it lists an owner and bring the open questions to the first call.
Teams that arrive with those records mapped spend the first call on the disputed data flows rather than on finding out where the evidence lives.
Every guide is free to read online. A download asks for a work email and company, which you can skip, and the file starts right away.
New York SHIELD Act Private Information Preparation
Map the private information, safeguards, service providers and incident records a privacy or breach review will examine.
File: ZIP: guide and editable CSV checklists.
Medical matter data sources
Identify the records held in EMRs, practice systems, portals and logs, then document the custodians, retention and access questions.
File: ZIP: source guide, checklists and sample questions.
Browse all preparation packages by subject.
Each overview lists the source dates and the contents of its pack.
Collection, Destination and Stated Settings
What personal information did the system collect?
We examine the application behavior, the database schema, the configuration and the retained records to identify what was collected, from whom and under what conditions. Where the dispute reaches back years, version records, backups and configuration history extend the examination into the class period.
Where did the data go?
Data flow testing, integration configuration and retained transfer records can establish destinations and recipients. Permission to share is not the same as evidence of a completed transfer, and the report keeps the two apart so the argument stays with what the records actually show.
Can you compare the stated settings with actual behavior?
Yes. We compare the stated configuration with observed behavior under documented conditions and report the differences. Each difference is tied to the configuration, the test conditions and the software version that produced it, which is the technical record a compliance argument is built on.
Talk with an examiner
Put the Privacy Evidence Question to an Examiner
Tell us the systems, the data and the deadline. We review relevant experience, potential conflicts and the scope before anything is engaged, and the first consultation is free.
Since 1992 · 24/7 dispatch · Court tested experts
Talk with an examiner
Retain a Privacy Expert Who Can Explain the Data
Expect to walk through the systems, integrations and vendors that touched the data and the period at issue. A senior examiner then names the configuration and version records to preserve and outlines the data flow examination, and the first consultation is free.
Our 24/7 hotline is (800) 868-8189.
GDF does not accept pro se litigation cases, and GDF may decline matrimonial or family law cases at our discretion.
Reviewed by Joseph Caruso, Founder, CEO and CTO, CISSP. Last reviewed .