AVAVERELI
CompanyProductsKnowledgeResearchDocumentationDevelopersSupportSearchCustomer portal

Policy centre

Public obligations need visible authority.

This centre will publish approved policies with an owner, version, effective date, review date, change history, and stable canonical address. Architecture exists; policy substance is not invented here.

Registered policy types8
Legal approvalNOT_CONNECTED
JurisdictionNOT_DECLARED
Policy historyEMPTY

Publication register

Expected policies, clearly gated.

0 policy documents have passed the publication contract. Candidate entries identify the required authority without presenting draft language as operative policy.

01

Privacy notice

PRIVACY

Substance owner
P000
Publication owner
P003
Status
AWAITING UPSTREAM POLICY
02

Cookie notice

COOKIES

Substance owner
P003
Publication owner
P003
Status
AWAITING UPSTREAM POLICY
03

Website terms

TERMS

Substance owner
P000
Publication owner
P003
Status
AWAITING LEGAL REVIEW
04

Acceptable use policy

ACCEPTABLE USE

Substance owner
P000
Publication owner
P003
Status
AWAITING UPSTREAM POLICY
05

AI transparency notice

AI TRANSPARENCY

Substance owner
P003
Publication owner
P003
Status
AWAITING EVIDENCE
06

Accessibility statement

ACCESSIBILITY

Substance owner
P003
Publication owner
P003
Status
AWAITING EVIDENCE
07

Licensing policy

LICENSING

Substance owner
P001
Publication owner
P003
Status
AWAITING UPSTREAM POLICY
08

Security disclosure policy

SECURITY DISCLOSURE

Substance owner
P100
Publication owner
P003
Status
AWAITING UPSTREAM POLICY
01

Author

The accountable programme creates the policy substance.

02

Review

Legal, technical, privacy, accessibility, or security reviewers assess the relevant claims.

03

Approve

Named authority approves a numbered version and effective date.

04

Publish

P003 validates metadata and exposes the canonical document.

05

Notify

Material changes become visible with a plain-language summary.

06

Retain

Superseded versions remain traceable without remaining operative.

Publication contract

Current, historical, and machine-readable.

Every operative document must identify approval, effective and review dates, the version it supersedes, and a plain-language change summary. Sitemap and future AI retrieval may include only approved current versions.

  1. 01Stable canonical URL
  2. 02Effective version marked
  3. 03Superseded copy retained
  4. 04Material change summarised
  5. 05Search and AI indexes refreshed

Related assurance

Policies describe controls. Evidence must prove them.

P003 cannot use policy text to claim legal compliance, security assurance, accessibility conformance, or responsible AI. Those claims require their own accountable evidence and approvals.

Privacy and analytics posture →Accessibility architecture →AI transparency architecture →Licensing architecture →Security architecture →