Introducing .auDO
A short, shareable brief explaining what .auDO is, why it exists, and how it makes public .au domain-layer trust signals more visible, consistent and explainable.
Privacy
How .auDO handles information associated with site visits and public domain-layer observation.
.auDO is designed as a public evidence and publishing service, not a user profiling, account or lead-capture platform.
Site visitors
No public accounts or on-site personal-information forms
What .auDO asks for
The public site does not require an account and does not ask visitors to submit personal information through an on-site form.
Standard request data
Infrastructure, content-delivery, logging, security or analytics services may process technical request data such as IP address, user agent, timestamp, referrer and requested URL.
External links and email
External services linked from .auDO apply their own privacy practices. Email enquiries disclose the information included by the sender and are handled through the receiving mail service.
Observation data
Public domain-layer data collected for system-level observation
.auDO collects publicly visible DNS, registration, mail and infrastructure signals about selected .au domains from documented public sources.
Public-source boundary
Observatory findings are based on public signals and documented external data, not private client, employer, partner or internal organisational information.
Publication and retention
Snapshots, change records, reports, manifests and supporting artefacts may be retained so public state and publication claims remain traceable over time.
Privacy concerns and corrections
A concern about inaccurate publication or unnecessary personal information will be assessed against the public-evidence purpose, source record, historical integrity and practical correction options.
Contact
Get in touch
Privacy questions, correction requests and feedback about .auDO public observations can be sent to Bryan Chetcuti.