Privacy summary · pre-launch
Privacy
Collect the minimum information needed, keep subscriber data away from public content, and never turn community trust into behavioural profiles.
What public use may generate
Cookieless aggregate analytics may measure page views, approximate aggregate visitors, popular pages, broad device category, referrers and aggregate outbound or advertising interactions. No session replay, fingerprint, cross-site identifier or email-open pixel is used.
Forms and newsletters
The newsletter begins with email, optional suburb and interests, consent and suppression status. Production double opt-in uses a hashed, single-use token. Contact and submission data is visible only to authorised operators and is not written to ordinary logs.
Retention
Published news remains public for one calendar year from its first Lota Local publication. Corrections do not restart that period. Event records remain public for up to 14 days after the occurrence ends. Retractions, stale sources and unsafe or withdrawn evidence are hidden immediately.
Ordinary raw source artefacts are private and retained for 30 days by default, or less where risk requires it. Source hashes, retrieval metadata, canonical links and claim references may remain after expiry. Operational log, form and subscriber retention must be configured and reviewed before launch.
Your choices
Production provides one-click unsubscribe and supports access, correction and deletion requests subject to lawful editorial and audit retention. A current Australian privacy review remains a launch gate.
Development preview
Public forms in this local build validate input and then discard it. They do not persist or send personal information.