Digital Privacy Rights: A Framework of Accountability

Migration note

This issue is a faithful port of the 2024 platform's "Digital Privacy Rights" plank, not a fresh policy pass. It hasn't yet been independently re-verified against the current state of US federal privacy legislation, state law counts, or GDPR/CCPA enforcement practice as of 2026. See the Research tier for what remains to be done.

The original argument

The source document frames privacy as a competitiveness question as much as a rights question: "innovation and security will go hand in hand," and businesses get "flexibility to grow while adhering to the highest privacy standards" under one national framework rather than needing to navigate fifty different state regimes. Its account of the current landscape names specific stalled federal bills (the Consumer Online Privacy Rights Act, the Online Privacy Act) and specific existing models to draw from (GDPR, CCPA) rather than arguing in the abstract. The accountability mechanism it proposes is institutional, not just legal: a "dedicated digital privacy agency" with enforcement authority, explicitly modeled on the idea that clarity of enforcement is what makes a privacy standard work in practice.

What Congress tried and what remains unresolved

The original 2024 plank named stalled bills without separating the public record from causal interpretation. ADPPA's official history establishes bipartisan House sponsorship, a 53-2 committee vote on July 20, 2022, and no floor passage. Contemporary reporting identified Senate concerns about enforcement strength and preemption of stronger state law among the barriers.

Senator Maria Cantwell and Representative Cathy McMorris Rodgers unveiled APRA as a bipartisan, bicameral discussion draft on April 7, 2024. It included a private right of action and a national standard. A later House draft removed civil-rights and algorithmic-accountability provisions, and the House Energy and Commerce Committee canceled its scheduled June 27 markup. Reporting described private enforcement, preemption, civil rights, and business liability as unresolved sources of opposition. The public record supports a failed coalition with several fault lines; it cannot assign one dispositive cause with confidence.

The 2026 SECURE Data Act is a House Republican proposal enforced by the FTC and state attorneys general. Democratic committee leadership criticizes it as an industry-friendly federal ceiling. That live dispute makes the platform's choices concrete: private enforcement, a strong federal floor, compatible stronger state protection, and targeted preemption only where conflicting implementation breaks a shared right or interface.

The preemption map

The north-star review resolves the conflict between privacy rights and federalism through function. National interoperability requires one vocabulary for covered data and actors, one machine-readable rights-request interface, one opt-out and consent-signal protocol, and common processor-contract and reporting fields. Those items receive targeted federal preemption when a conflicting state rule would make the shared interface fail.

The federal statute remains a floor for substantive protection. States may protect additional sensitive data, create stronger duties for children or biometrics, use general consumer- protection, civil-rights, contract, and tort law, and enforce the federal standard through state attorneys general. A stronger state rule must use the common national interface where the same right is being exercised. Congress must publish the preemption map field by field and assign a fast judicial process for boundary disputes.