Back to the blog

Reusable age credentials under U.S. state laws

A visitor can present a credential today based on an age check performed months ago. Before accepting it, a site needs to answer three questions. Does the method fit the law? Does this presentation belong to the visitor making the request? Is another age check due? Keep those decisions separate when you design a returning-visitor flow.

Know what the visitor is reusing

This guide compares five state laws for covered online adult-content services. It looks at the type of evidence each law describes, when it calls for verification, and what the parties may keep. Sources checked November 22, 2026.

Think of three steps in a wallet flow. An issuer establishes an age attribute and gives the visitor a credential. The wallet can create a new presentation for a particular site. The site decides whether to trust the issuer, whether the presentation is valid, and whether the evidence qualifies for that request. A cached account result is different. It records an earlier decision at the site. Opening a new login session with that account leaves the age check itself at its original date. [11]

That gives the operator three clocks to track. The first is when age was established. The second is how long the presentation can be used. The third is when the law requires verification again. A presentation generated a second ago can still carry evidence from an older check. [11]

Louisiana and Texas name digital identification

Louisiana Revised Statutes § 9:2800.29 expressly includes a digitized identification card among the methods covered sites can use. It points to § 51:3211, which defines a card available through a state-approved app from the state department or an authorized representative and describes the card’s data and current status. The same adult-content provision also describes commercial verification using government-issued identification or a commercially reasonable method based on transactional data. [1] [2]

Texas Civil Practice and Remedies Code § 129B.003 lists digital identification or a commercial system that verifies age using government-issued identification or a commercially reasonable method based on transactional data. The definition of digital identification refers to proof of the person’s identity. The Supreme Court’s June 2025 decision in Free Speech Coalition v. Paxton upheld the challenged Texas requirement under intermediate First Amendment scrutiny. The decision leaves the fit of an individual credential design to a separate analysis. [3] [4]

These provisions give operators named routes to evaluate. For an age-only presentation from a private wallet, ask the provider to identify the statutory route it relies on and show the evidence behind it. Find out whether the verifier uses the original evidence in a qualifying commercial system and what the verifier establishes about the visitor on each request. An age-only field tells you the claim being made. The provider must explain how it was established and what connects it to the person presenting it. [1] [2] [3]

Florida requires a choice of methods

Florida Statutes § 501.1737 requires covered sites and apps to offer both standard and anonymous age verification and let the visitor choose. Section 501.1738 defines the anonymous method around a commercially reasonable check conducted by a nongovernmental, independent third party that meets U.S. organization, principal place of business, and ownership or control requirements. It restricts how that verifier uses, shares, and retains personal identifying information used to verify age. [5] [6]

An age-only proof can be part of a design worth evaluating. Identify who issues the credential, who operates the wallet, and who actually conducts verification. Then check whether the verifying party qualifies for the anonymous route and whether the site also offers a standard route. The Florida provisions describe the method and the parties’ obligations. The acceptance of any particular reusable proof and its use on return visits still need to be assessed. [5] [6]

Ohio and Tennessee put repeat checks on different clocks

Ohio Revised Code § 1349.10 distinguishes attempts to access covered material from account or subscription creation. It calls for age verification for both and adds reverification every two years after creation for the account or subscription. The statute ties reasonable methods to commercial verification using photo identification or transactional data, including the specified database route. The two-year rule governs account reverification. The separate access duty still needs its own analysis before an operator relies on an account flag. [7]

Tennessee Code § 39-17-912 calls for reasonable verification when a user attempts to access a covered site and again when the user tries to return after the age-verified session. The session is the shorter of the session in which the user was verified and 60 minutes from verification. The September 2026 district court order describes the amended law, records that the Sixth Circuit vacated the earlier preliminary injunction in November 2025, and lets the amended challenge proceed by denying a motion to dismiss. [8] [9] [10]

Suppose a visitor verifies on a covered Tennessee site at 2 p.m. and returns at 3:15 using the same wallet. Under that session rule, the operator must perform a reasonable verification on return. A one-year credential expiry cannot extend the session. A new presentation can demonstrate that the visitor controls the wallet on this request. Whether this is enough for a new reasonable age verification depends on what the method actually does. Document that assessment and keep a qualifying verification path available if the proof cannot support it. [8] [10] [11]

Design retention around the job each record does

Louisiana bars the operator or third party performing the required check from retaining identifying information once access is granted. Texas also bars retention of identifying information by the parties performing the required verification. Ohio requires immediate deletion of information gathered for access-only age verification and sets separate, limited conditions for keeping account, subscription and billing information. Florida sets its own limits on the anonymous verifier’s use, sharing and retention of personal identifying information. [1] [3] [7] [6]

Tennessee requires at least seven years of anonymized verification data and bars retention of the active user’s personally identifying information after access is granted. Its definition of anonymized evidence includes how the verification system works and execution volumes relative to visits. Plan that evidence separately from the token payload and the visitor’s account. Test whether identifiers used in logs, analytics, support tools, or fraud records can be joined back to the user. [8] [10]

What operators should verify before launch

Build a record for each state and each covered user journey. Use it to decide what the wallet can do, where a separate check is needed, and what the team must test. Treat NIST’s wallet controls as technical guidance. Establish the basis for statutory acceptance from the state law and the way your system implements it. [11]

  • Method and issuer. Record the named method, the issuer and verifier, their roles, and the evidence used to establish the age threshold. In Louisiana and Texas, ask which digital identification or commercial verification route the system is using. [1] [2] [3]
  • Visitor choice and fallback. Verify Florida’s two routes and the anonymous verifier’s independence and organizational qualifications. Test what happens when an issuer is unfamiliar, a check fails, or the visitor has no supported wallet. [5] [6]
  • Holder and presentation. Check who controls the wallet, the signature and trusted issuer, the intended site, the validity period, and how a captured presentation is rejected when reused. Ask what happens when a credential, device or signing key is reported compromised and how the verifier learns its status. [11]
  • Recheck timing. Test Ohio’s account creation and reverification separately from access. Test a Tennessee return after the session has ended and verify the check still takes place when a credential remains valid. [7] [8] [10]
  • Evidence and deletion. Decide what each party sees and keeps, and test deletion in logs and third-party systems. Check that Tennessee’s historical evidence is genuinely anonymized and document the distinct retention rules for every state you serve. [8] [10] [1] [3] [7] [6]

Sources

  1. Louisiana Revised Statutes § 9:2800.29 Louisiana State Legislature
  2. Louisiana Revised Statutes § 51:3211 Louisiana State Legislature
  3. Texas Civil Practice and Remedies Code §§ 129B.002 and 129B.003 Texas Legislature
  4. Free Speech Coalition, Inc. v. Paxton, June 27, 2025 U.S. Supreme Court
  5. Florida Statutes § 501.1737 Florida Senate
  6. Florida Statutes § 501.1738 Florida Senate
  7. Ohio Revised Code § 1349.10 Ohio Legislative Service Commission
  8. Tennessee Code Bill, § 39-17-912 Tennessee General Assembly
  9. Tennessee Senate Bill 448, 2025 Public Chapter 405 Tennessee General Assembly
  10. Free Speech Coalition, Inc. v. Skrmetti, September 15, 2026 order, ECF 79 U.S. District Court for the Western District of Tennessee
  11. NIST SP 800-63C-4, Subscriber-Controlled Wallets National Institute of Standards and Technology
Contact Safe Passage