User Intents

In progress

Proposed AT Protocol mechanism for users to declare data-reuse preferences such as generative-AI training.

Website
demo.user-intents.org
Latest tracked evidence
Mar 08, 2025Proposal discussion opened
Last checked
Jun 24, 2026
Profile updated
Mar 19, 2026
Primary approach
Preference signal
Practical force
Voluntary signalIt only affects actors that detect and honor the signal; it does not itself prevent reuse.
Pipeline
Collect / Train / Retrieve
Status rationale
Publicly documented, but still emerging or not fully deployed.

Enforcement

Voluntary preference signal. Communicates a requested condition or restriction to automated systems.

It only affects actors that detect and honor the signal; it does not itself prevent reuse.

Catalog status describes public availability, not legal validity, adoption, or proven effectiveness.

What it is

User Intents is an AT Protocol proposal for letting people declare how their public social data may be reused, including for generative-AI training. A public demo already maps these declarations to draft AIPref-style HTTP signaling for web access.

The work is notable because it moves preference signaling from site operators toward end users, but it is still early and not yet a standardized, network-wide default.

User Intents publishes or proposes a machine-readable preference signal for multimodal material across the collection, training, and retrieval stages. The signal communicates requested conditions; compliance depends on discovery, interpretation, and voluntary support by downstream systems. Public materials describe an in-progress proposal or implementation; the newest dated source in this profile is “Proposal discussion opened” (March 8, 2025). These details describe the published mechanism and evidence, not a finding about legal validity, adoption, or effectiveness.

Limitations

This is still a proposal plus demo implementation, and its enforcement model is voluntary in the same sense as other preference-signal approaches.

Evidence trail

Adoption signals

No public adoption figure found.

Examples

Declaration record exampleSource

The atproto proposal discussion includes a concrete account-level declaration record with AI generation disallowed.

{
  "$type": "org.user-intents.declaration",
  "updatedAt": "2025-02-20T21:37:20.362Z",
  "org.user-intents.syntheticContentGeneration": {
    "allow": false,
    "updatedAt": "2025-02-20T21:37:20.362Z"
  }
}
HTTP header mapped from the declarationDemoSource

The public demo says these declarations can be translated into a Content-Usage header on web profile pages.

Content-Usage: train-ai=n