What the record means

Experience, policy & household context

Family ownership or leasing of a Tesla with FSD is sourced household metadata. It never counts as the lawmaker’s personal FSD experience. Local officials have a separate classification; a local roster has not yet been imported.

1. Ridden with FSD. Passenger during active FSD on HW4 or newer.
2. Supervised FSD. In the driver’s seat supervising active FSD on HW4 or newer.
3. Tesla Robotaxi ride. A ride in Tesla’s Robotaxi service; service and demonstration trips are distinguished.
4. Cybercab ride. A ride in a Cybercab, with demonstration or service context recorded.
5. FSD policy. Tesla-specific positions and general autonomous-vehicle policy, attributed separately.
6. Cybercab policy. Dated positions, statements, votes, and legislation relevant to Cybercab.
7. Family owns / leases a Tesla with FSD. Sourced household ownership or leasing of a Tesla with FSD; does not establish personal driving experience.

A qualifying HW4+ FSD trip requires FSD to have been active. Closed-course trips count and are labeled. Parked visits and manual-only driving do not qualify.

Evidence statuses

Verified

Reviewed evidence establishes the specific claim.

Self-reported

The lawmaker or office reports the experience; corroboration is incomplete.

Unverified claim

A claim exists, but the evidence is insufficient.

Reported no

An explicit, dated statement says no experience. This is not inferred from silence.

Unknown

No published finding establishes the answer. Unknown does not mean no.

AI collects candidate evidence. Approved human reviewers publish findings. Politician confirmation is not required where other evidence establishes the claim.

Hardware and trip context

Hardware can be directly verified or inferred using a documented vehicle-specific rule. Each inference must establish the relevant model, production period and market, and link its supporting source. Ambiguous identification remains unconfirmed.

Cybertruck, newer Model 3 / Model Y, and Cybercab contexts are research leads for hardware inference. The project does not treat a photo, registration year, or generic “Tesla ride” as proof that qualifying FSD was active.

Robotaxi service and Cybercab experiences are tracked separately; they do not automatically establish a passenger or supervising-driver HW4+ FSD claim.

Counts and history

The headline counts unique national lawmakers with verified HW4+ FSD passenger or supervising-driver experience. A person counts once, even with multiple trips or both types of experience. Former members retain their place in the cumulative record.

The main chart uses report publication dates, not trip dates. A newly discovered older trip increases the next published report. Previous reports remain fixed. Current-officeholder figures use today’s roster and can change with departures, vacancies and corrections.

Corrections are appended with a public explanation. A correction may lower a later total without altering earlier published points.

State map saturation is verified current experience divided by current roster membership. Congress and state legislators can be viewed separately.

Policy positions

We attribute dated quotations, votes and bill actions. Tesla-specific positions are distinguished from general autonomous-vehicle policy. Mixed and conditional positions are retained rather than reduced to a supportive/opposed score.

Roster sources

Congress: United States congressional roster. States: Open States / Plural people data.

Baseline retrieved 2026-09-30. 539 federal and 7326 state source records. Vacancies and membership require ongoing reconciliation; these are source roster counts, not statutory seat totals.

Congress includes nonvoting delegates. State coverage includes all 50 legislatures, including Nebraska’s unicameral legislature. Governors, DC’s council, and territorial legislatures are outside launch coverage.

Privacy and outreach

No account is needed to browse or submit evidence. Home addresses are processed for district matching and are not stored by the tracker. The U.S. Census Bureau receives the address for matching under its online privacy policy. We use its ACS2025 geography for the 119th Congress; we do not substitute future congressional boundaries. Unmatched or ambiguous addresses require manual lookup. Address matching currently covers Congress, not state or local officials.

First-party activity records contain event type and permitted identifiers such as a lawmaker ID, not raw addresses, search text, or submitted email content. Rate-limit identifiers are salted hashes. Private submission contacts and ride offers are visible only to reviewers.

Evidence uploads remain private until reviewed. Published supporting media can be viewed on a profile. Submitters should share only material they are entitled to publish.

External analytics are optional deployment integrations. Google Analytics, PostHog and Omani may have their own data practices; privacy configuration must be verified before enabling them.

Visitor outreach opens an editable message or official contact page. Clicking does not prove delivery. Project email is sent only after a reviewer approves the exact draft and explicitly sends it. SMTP acceptance is separate from confirmed delivery. Replies and delivery notices are recorded privately by reviewers. Follow-ups are reviewed drafts, spaced at least seven days apart, with an initial inquiry and up to two follow-ups within thirty days, then a pause. Stop requests are respected.

Ownership and corrections

Lawmaker FSD Tracker is operated by Andy Roberts, an interested individual seeking the facts. It is not affiliated with Tesla or any government organization.

Use a lawmaker’s correction form to dispute a finding. Include the source and what should change. Reviewers retain the original published record and append the resolution.