Privacy

Privacy boundaries for site visits, correspondence and public domain-layer observation.

.auDO is a public evidence and publishing service, not a user-profiling, account or lead-capture platform.

Privacy model

Four boundaries define the public service

The observatory keeps visitor interaction deliberately light and separates correspondence from the public-source evidence it collects.

No public accounts

The public site does not require registration, sign-in or a reader profile.

Contact information is optional

A contact email is requested only when a response or follow-up is wanted.

Observation uses public sources

.auDO observes documented public domain-layer signals rather than private organisational systems.

Correspondence stays separate

Enquiry handling does not become observatory evidence or analytical input.

Site visitors and correspondence

No public accounts; contact information is optional

Standard request and verification 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. Cloudflare Turnstile processes request and browser signals for form-abuse prevention.

Correspondence handling

The contact intake Worker validates and routes form submissions to existing .auDO email addresses. It does not intentionally persist submission content in D1, KV, R2 or a case database, and submission bodies are not written to Worker logs. For a published-use submission, the form requires only the publication URL and a short description of how .auDO observations were used; publication title, publicly credited author or publisher details, and contact email are optional. Once delivered, correspondence may be retained in the receiving email system for review, follow-up, project administration, security or record-keeping. Direct email follows the same receiving-mail boundary. External services linked from .auDO continue to apply their own privacy practices.

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.

.auDO is owned and editorially controlled by Bryan Chetcuti. The Vigo Group provides operational services and bears current project costs. Operational support does not permit private client or commercial information to enter .auDO evidence and analysis.

Contact

Questions, corrections and privacy concerns

Use the contact page to route a privacy concern, correction request or question about .auDO's methods and published observations.