Policy and Security

What this page is for

Use this page as the trust-policy hub for the UAIX launch surface. It connects the dedicated public pages for privacy and data, accessibility, and analytics to the current licensing and security release posture so reviewers can audit the whole trust layer from one governance section.

Current policy map

• Privacy and Data for the public-reading, discovery, and data-exposure posture.
• Accessibility for readable-launch expectations, keyboard and mobile QA, and accessibility-significant release handling.
• Analytics for the current published limits on measurement, telemetry-significant changes, and disclosure posture.
• Governance, the Changelog, and News for the authority model, dated release trail, and public narrative around trust-significant changes.

Current licensing posture

• Active public launch theme: the current UAIX Authority theme declares GPL v2 or later in its public package header.
• Other packaged artifacts: evaluate each distributed package against its own shipped header, notice, or bundled source terms rather than assuming one broader site-wide code license where none has yet been published.
• Public standards pages: treat the canonical page paths as the public reading, citation, and review surface for UAI-1 and related records. Do not infer a broader trademark, certification, or endorsement right from public availability alone.

Security and release discipline

• The public site is a standards and publication surface, not a live security gateway or managed trust service.
• Launch checks should keep HTTPS, security headers, .well-known delivery, sitemap delivery, validator behavior, and machine-facing route inventory aligned before public support claims are widened.
• Use API Reference, Conformance Pack, the Validator, and Implementations when a release needs reviewable machine evidence instead of prose-only assurance.

Observable response hardening

Use the section below when a launch reviewer needs the concrete response-header layer that now backs the public trust posture on WordPress-rendered routes, plus the boundary between app-level hardening and host-level deployment work.

[uaix_security_header_posture context=”policy”]

How these policy pages fit together

• Use this page as the hub: start here when the question is “which published policy surface should I read next?”
• Use the dedicated pages for the actual posture: Privacy and Data, Accessibility, and Analytics each publish the current launch-stage boundary for that area.
• Use References and Contributors and /.well-known/uaix.json when a reviewer needs the current public discovery and handoff packet without relying on screenshots or private instructions.