California AB 1705 advances adult-upload consent checks

Checked 30 July 2026. California Assembly Bill 1705 moved into the Senate Appropriations process after a 1 July amendment. The official status page lists an Appropriations hearing for 3 August 2026. That makes this a live policy watch, but the most important qualifier comes first: AB 1705 is an active bill, not a rule that platforms or creators must already follow.

The July text targets websites that permit or solicit user uploads of sexually explicit material. Its central idea is a pre-upload certification that every depicted person was an adult when the material was created, consented to being depicted, and consented to the upload. The proposal connects that statement to verified uploader contact information and a longer evidence-retention duty.

What the July amendment proposes

Before accepting an upload, an operator would have to obtain a statement made under penalty of perjury covering age and two distinct forms of consent: participation in the material and publication on the website. The uploader would also provide contact information, including an email address, and the operator would have to verify that email before permitting the upload.

The bill would require the operator to retain the statement and contact information in a readily available format for at least seven years. A site that fails to obtain the certification would be presumed to have violated the proposed duty of ordinary care. The text also creates routes for civil enforcement by a depicted person and by a public prosecutor.

• Pre-upload certification covers adulthood, consent to depiction, and consent to online publication.
• Uploader contact information includes at least a verified email address.
• The proposed retention period is seven years.
• Each full calendar day that violating material remains accessible can count as a separate violation.

Scope matters

The current definition covers a website that permits users to upload, or solicits from users, sexually explicit content for display. It excludes email or direct-messaging services on that function alone, and excludes cloud storage, file transfer, or collaboration services on that function alone. The July amendment also contains a specific exclusion for material sent through a private messaging or direct-communication feature of an online dating service, subject to the bill’s wording.

Those boundaries matter because a creator subscription platform, a general social platform, a dating service, and a private storage tool do not expose content in the same way. A responsible impact assessment should map the exact public-display and upload paths instead of treating every product with a message box as equivalent.

The unresolved operational questions

The bill specifies the statement and minimum contact record, but operators would still need to decide how they authenticate the uploader, connect consent to a particular asset and version, handle revocation or disputes, and protect retained records. Seven years of evidence can support accountability, but it also creates a sensitive data store that needs strict access controls, retention deletion, incident response, and a defensible purpose.

The Senate Judiciary analysis also records constitutional and Section 230 questions and notes opposition arguing that the definition may be broad. FoxyPulse is not predicting how those issues will be resolved. They are reasons to follow the enacted text, if any, rather than building a compliance program around a headline summary of the current proposal.

Who is affected if the bill becomes law

Platform operators would carry the direct workflow and recordkeeping burden. Uploading creators would be asked to make a formal certification and provide verified contact details. Depicted people would gain a specified civil route when material was created or uploaded without the relevant consent, or when they were a minor at creation.

Members and viewers are not the main operational subject of this bill. The practical consumer effect would be indirect: stronger provenance controls may reduce abusive material, while poorly designed collection could increase privacy and security risk for legitimate creators.

What to check before the next hearing

A platform can review its existing evidence architecture without representing the proposal as law. The useful exercise is to identify what is already collected, where it lives, who can access it, and whether a removal or consent dispute can be traced to an exact asset.

• Separate consent to participate from consent to publish and distribute.
• Link consent evidence to each depicted person and exact content asset.
• Document how an uploader email is verified and how account changes are handled.
• Minimize access to retained evidence and set audit, breach, and deletion controls.
• Recheck the official bill status and amended text after the listed hearing.

What this update does not establish

AB 1705 has not been enacted. The current text does not prove that a particular platform is compliant or noncompliant, and it does not replace legal advice about California law, federal law, or another jurisdiction. It is a dated signal that consent provenance and platform accountability remain active legislative priorities.

Source trail

• California Legislative Information — AB 1705 text amended 1 July 2026 (legislation)
• California Legislative Information — current AB 1705 status (legislative-status)
• California Senate Judiciary Committee analysis — 16 June 2026 (committee-analysis)

FoxyPulse is independent dated reporting. This material contains no raw affiliate destination, does not rank products by commission, and is not legal or medical advice.