UAI-1 is the current public message standard for structured AI-to-AI communication.
UAIX shield mark Public interoperability charter UAIX.org Universal Artificial Intelligence Exchange Public standards publication
Current UAI-1
  • Current version UAI-1
  • Plain-English definition Open message format for auditable AI-to-AI exchange
  • Current attribution Michael Joseph Kappel, MCP
  • Start here Get Started, Project Handoff, UAI-1, validator, roadmap, and changelog

Governance

Privacy and Data

Current public posture for discovery, public data exposure, and privacy-significant release work across the UAIX launch surface.

  • Record UAIX-GOVR-0070
  • Path /en-us/governance/privacy-and-data/
  • Use Canonical public record

Document status

Public standards page Published on UAIX as part of the current public standards record
Code
UAIX-GOVR-0070
Surface
Governance
Access
Public and linkable

How to use this page

Use this page for the current public posture on public data exposure, discovery behavior, and privacy-significant release work.

Review with

Policy and SecurityAnalyticsReferences and ContributorsChangelog

Privacy Posture

Read public data exposure as part of the launch trust surface

This page is the current public boundary for readable public records, discovery behavior, downloadable evidence, and privacy-significant release handling.

Public reading

Review should not depend on hidden intake

The current posture favors readable standards pages and discovery routes without implying unpublished account walls or private submission flows.

Discovery and downloads

Public routes are part of the data posture

Discovery manifests, sitemaps, validator exports, and conformance packets should stay aligned with what the site publicly says about data exposure.

Future work

Do not infer institutional privacy programs

Consent centers, DPA workflows, and broader privacy-office infrastructure remain future work unless they are formally published.

Review with

Policy and SecurityCross-cutting trust hub and security discipline.AnalyticsMeasurement posture that can overlap with privacy changes.References and ContributorsCurrent public handoff and discovery packet.ChangelogDated release record for privacy-significant changes.NewsPublic-readable release summary when posture changes.
Discovery routesPublic routes that should stay readable
https://uiax.org/.well-known/uaix.json
https://uiax.org/sitemap.xml
http://uiax.org/wp-json/uaix/v1/catalog

Use these public discovery surfaces when reviewing data exposure or handoff behavior.

Privacy and data posture

What is published now, how to verify it, and what is not implied

Use this matrix when a reviewer needs the current public boundary for readable records, discovery behavior, and privacy-significant release work.

Operating areaPublished nowVerify hereNot yet public
Public reading surfaceStandards pages, governance pages, and discovery routes should remain readable without implied account walls or private intake flows.Account portals, private submission programs, or formal intake-policy stacks are not yet public.
Discovery and public data exposureDiscovery manifests, sitemaps, and canonical pages are part of the public data posture and should stay aligned with what the site claims.Do not rely on screenshots, unpublished mirrors, or hidden collection behavior as the public record.
Release-significant data changesIf public data exposure, downloadable evidence, or telemetry-relevant behavior changes, the release trail should say so before the new state is treated as current truth.Broader privacy-office or consent-center infrastructure is not yet published.

The current claim is narrow and observable: public pages and discovery surfaces should remain reviewable without unpublished account or intake dependencies.

Privacy review packet

How privacy-significant changes should travel

Use this sequence when a release changes public data exposure, intake posture, discovery behavior, or downloadable evidence.

  1. Step 1

    Check the public reading path

  2. Step 2

    Check discovery and downloadable routes

  3. Step 3

    State the data-significant change

  4. Step 4

    Attach release evidence

  5. Step 5

    Publish the dated trail

Keep the written posture, observable routes, and dated release trail aligned before another reviewer is asked to trust the new state.

What this page covers

Use this page for the current public posture on privacy and data handling across the UAIX launch surface. It explains how the standards pages, discovery files, validation tools, and release trail should behave when public data exposure or collection expectations change.

Current published privacy and data posture

  • Public standards pages, discovery files, and primary review routes should remain readable without implied account walls or unpublished intake flows.
  • If a release changes public data exposure, form collection, downloadable evidence handling, or any telemetry-relevant behavior, record that change on Governance, the Changelog, and News instead of leaving it implicit.
  • Use References and Contributors, /.well-known/uaix.json, and /sitemap.xml when a reviewer needs the current public discovery surface without relying on screenshots or private instructions.

What reviewers should verify now

  1. Check whether the public reading surface remains usable without unpublished account, form, or intake dependencies.
  2. Check whether any downloadable validator evidence, fixtures, or conformance packets change what public data is exposed or retained.
  3. Check whether public route, discovery, or crawl behavior changed in a way that should be called out in the release trail.
  4. Check whether the written privacy posture still matches observable behavior and linked machine-facing routes.

What is not claimed

  • UAIX does not currently publish a broader consent center, user-account privacy portal, DPA workflow, or institutional privacy office.
  • Do not infer private submissions, hidden data sharing, advertising, or unpublished audience profiling from the public launch surface.
  • Do not imply broader repository or contact-center data-processing programs unless they are formally published on canonical UAIX pages.

How privacy-significant changes should travel

  • Update the affected canonical page and the observable site behavior together.
  • Record the change through Changelog and News when outside readers need dated context.
  • Use Policy and Security when the change also affects licensing or security-sensitive release posture.
  • Use API Reference, Conformance Pack, and the Validator when the same change also touches machine-facing evidence or downloadable artifacts.

Next step

Continue to Policy and Security for the cross-cutting trust hub, or read Analytics when the question is specifically about measurement or telemetry-significant release changes.