Privacy policy for the static evidence desk

A method readers can challenge

Trust requires visible limits. This page states what the desk does, which evidence it accepts and where a conclusion stops. We do not invent first-hand tests, credentials, customers or regulator findings to make a page sound more authoritative.

Primary sources establish law and enforcement. Provider material explains game mechanics. Third-party pages can reveal common questions or conflicting claims, but they remain discovery sources until a closer record confirms the detail.

Every material challenge is welcome when it includes the exact page, disputed sentence and a retrievable source. Corrections are dated, and uncertainty stays visible when the available records genuinely disagree.

Bottom line: The static build has no analytics, advertising pixels, accounts or server-side form collection. Local preferences use only browser storage; a production owner must publish any later analytics or form processors before enabling them.

1. Data minimisation
2. Source inspection and network requests
3. Keep the production data map current
4. Scope and last-reviewed date

Complete the list using sources you reached independently. If a material answer is missing, the absence is part of the conclusion; it is not a reason to guess.

Do not rationalise these away.

• Adding trackers without updating consent and disclosure
• Invented credentials or unsupported certainty
• Sharing passwords, one-time codes or unredacted identity records

If a warning appears after money or documents have moved, preserve the URL, messages, transaction references and terms before closing the session. Secure the connected email account and contact the payment provider promptly when fraud is suspected.

Trace the conclusion.

Sources are listed by the role they play. Government and regulator records establish Australian legal context; other material is explicitly labelled when it is used only for discovery or product detail.