Digital-ID map
beta

Take action

How to weigh in on age-verification and digital-ID laws

Age-checks and digital-ID mandates are written in the statehouse -- and, increasingly, at the federal level and in the EU. The leverage is in the timing: a bill is easiest to change while it is still in committee. Here is how to be heard before it becomes law.

The short version

Most of these rules move as state bills. Find the bill number and the committee it sits in, read what it actually requires, and get your position to your own legislators and the committee before the hearing. A short, specific message from a constituent still carries real weight at the committee stage.

A step-by-step start

  1. Find the bill and its status

    Get the bill number, chamber, committee, and sponsor, and where it is: introduced, in committee, scheduled for a hearing, or passed one chamber. Open States tracks bills and your legislators by address.

  2. Read it for what it actually requires

    Does it mandate uploading a government ID? Age-estimation from a selfie? Verification at the device or app-store level? Who holds the data, and for how long? Is there a private right of action or platform liability? Those details are the whole debate.

  3. Contact your own legislators first, then the committee

    Your representative and senator are your two votes -- contact both. Then the committee of jurisdiction, whose members decide whether the bill advances. Say you are a constituent, name the bill, and state your position in the first line.

  4. Submit written testimony or sign up to testify

    Most committees accept written comment and take public testimony at the hearing. Written testimony enters the record even if you cannot attend in person -- ask the committee clerk how to file it and the deadline.

  5. Make the privacy case concretely

    Uploading a government ID to read everyday sites creates a breach target and a record of what you read; age-estimation is error-prone and often fails for adults. Ask exactly what is collected, who holds it, how long it is kept, and how it is deleted and audited.

  6. Track it through both chambers and the governor

    A bill can be amended between chambers, so watch for a second committee and new language. If it passes, a veto request to the governor is a final step.

Who to contact

Templates you can copy and send

Starting points you can adapt. Fill in the bracketed parts -- including your state's public-records law where it applies -- then send.

Message to your legislators -- oppose or amend an age-verification bill 
Subject: Constituent opposed to [bill number] -- age verification / digital ID

Dear [Representative / Senator name],

I am your constituent in [town/ZIP], and I am writing about [bill number]. I oppose it as written / I am asking for amendments, because it would require [uploading a government ID / age-estimation / device-level verification] to use everyday websites.

My concerns are practical:
1. Privacy and breach risk: it creates a database of IDs and a record of what people read online -- a target attackers will go after.
2. It does not work cleanly: age-estimation misfires for adults, and ID mandates push people toward less safe workarounds.
3. Data handling: the bill is not clear on exactly what is collected, who holds it, how long it is kept, or how it is deleted.

I share the goal of protecting kids. I am asking you to [oppose the bill / amend it so that no government-ID upload is required, data is not retained, and there is a clear deletion and audit rule]. Please let me know your position.

Thank you,
[Name and address, so my office knows I am a constituent]
Written testimony -- for the committee record 
To the [Committee name],
Re: [bill number], written testimony -- OPPOSE / OPPOSE UNLESS AMENDED

My name is [Name]. I am a resident of [town]. I ask the committee to [not advance / amend] [bill number].

[One or two sentences on who you are and why this affects you.]

The bill would [describe the mechanism in one sentence]. I urge the committee to consider three things:

1. It creates a privacy and security risk: verifying age by ID or biometrics builds a database that becomes a target, and links people to what they read.
2. It is unreliable: age-estimation and ID checks produce false results and are easily circumvented, while burdening lawful adult access.
3. It lacks data safeguards: [note any missing retention, deletion, or audit language].

If the committee proceeds, I ask that it be amended to prohibit government-ID retention, require prompt deletion, and add an independent audit. Thank you for entering this into the record.

[Name]

A few things to watch for

"Think of the children" versus the mechanism. Everyone supports child safety; the real question is whether ID-upload or age-estimation actually works and what it costs everyone else. Keep the conversation on the mechanism, not the goal.

Device- and app-store-level mandates. Some bills push verification down to the phone or the app store, which quietly affects every app at once. That is a much broader change than it first appears.

Data retention and breach exposure. Ask precisely what is collected, who holds it, how long, and the deletion and audit rules. Vague language here is where the risk hides.

Fast substitutes and amendments. Bills get gutted and replaced late in the process; the version that passes may not be the one you read. Track amendments and the second chamber.

Private-right-of-action and liability clauses. These change who can sue platforms and tend to drive over-blocking of lawful content. They are easy to miss and heavily contested.

Where to go for more

This guide is informational and general. Bills and legislative procedures vary by state, so confirm the current status and process on the official bill page.

Not sure where to start?

Get a plan for your town

Tell the tool your issue and where you live and it pulls together who to contact, when they meet, and a message you can copy and send.

Open the get-involved tool →