We build compact AI messaging tools.
JustAnIota official shield mark JustAnIota UAI tooling ɩ.com Compact AI messaging tools Language-neutral AI messaging: registries, schemas, validation.
Draft IOTA-1 tools
  • Current surface JustAnIota tooling draft
  • Plain-English definition Compact, structured AI messaging tools
  • Current attribution Michael Joseph Kappel, MCP
  • Short-domain status ɩ.com redirects to JustAnIota.com

Governance / Trust

Privacy and Data

Privacy posture for source text, compact payloads, validator reports, logs, and export evidence.

  • Record JAI-GOVR-0029
  • Path /governance/privacy-and-data/
  • Use Canonical public record

Document status

Public standards page Published on JustAnIota.com as part of the current public standards record
Code
JAI-GOVR-0029
Surface
Governance / Trust
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://justaniota.com/.well-known/uaix.json
https://justaniota.com/sitemap.xml
https://justaniota.com/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.

Plain English

Short payloads can still carry sensitive meaning.

Technical summary

Tools should avoid hidden logging of source text, compact payloads, registry choices, or validator reports unless a public policy explicitly says otherwise.

Deep spec

Future hosted tools need a data-retention policy before accepting real user payloads.

Data boundaries

  • Browser prototypes run locally in the page.
  • Do not submit secrets or private payloads into prototype tools.
  • Do not treat screenshots as durable validation evidence.