A personal website may look modest, but even a simple blog can collect personal information. A contact form needs an email address, comments store identifying details, and analytics tools record visits. A clear privacy policy explains what happens to that information before visitors make a decision based on incomplete assumptions.
Trust matters particularly when a site is associated with one person rather than a large organisation. Readers may book a photography session, subscribe to project updates or ask for consulting advice. They deserve to know who receives their enquiries, whether their details are sold, and how long their records remain available.
Australian privacy law provides a useful baseline, but legal wording alone does not answer every practical question. Small publishers may fall outside some federal requirements, while readers still expect honest disclosures. Plain language, specific practices and a reliable contact route turn a legal requirement into a genuine assurance.
| Policy area | Vague wording | Clear wording |
|---|---|---|
| Collection | “We may collect information.” | “When you use the contact form, we collect your name, email address and message so we can reply.” |
| Purpose | “We use data to improve your experience.” | “We use your details to answer your enquiry. We do not use it for unrelated marketing.” |
| Third parties | “We may share data with trusted partners.” | “Your address goes to our hosting and email providers. We do not sell it.” |
| Storage | “We keep information as long as necessary.” | “We delete unsuccessful enquiries after 12 months and review active mailing records annually.” |
| Choices | “Contact us with any questions.” | “Email us to request access or correction. We acknowledge requests within five working days.” |
Personal information includes more than a name and email address. Forms may also receive a phone number, suburb, IP address, browser details and the words a visitor types. Server logs, comment notifications, embedded media and analytics scripts can create additional records, often without an obvious form submission.
Consider a Melbourne reader sending a portrait enquiry from a phone and a Sydney subscriber opening an update while waiting for a train. Their information may travel through your hosting provider, a form plugin, an email platform and an analytics service. Naming those participants is more useful than promising simply that everything remains “secure”.
Collection should match a defined purpose. A booking form needs enough information to arrange and invoice the job, but it may not need a date of birth or a home address. Sensitive details deserve particular restraint: avoid requesting health, financial or identifying information about other people unless it is genuinely necessary to deliver the service.
The Privacy Act 1988 and its Australian Privacy Principles govern many organisations, including small businesses above the $3 million turnover threshold and many government agencies. Covered organisations must maintain a clear, accessible privacy policy and explain their handling practices. They must also support access and correction requests and provide a complaint pathway.
Many Australian bloggers, freelancers and sole traders fall below that turnover threshold, so the Act does not automatically apply to them. Coverage can still arise through contracts, certain health-related activities or other legal arrangements. Transparent handling remains sensible outside the Act, particularly where a personal site also operates as a commercial service in Australia.
If you trade or promote services, misleading privacy claims can also create problems under the Australian Consumer Law. Statements such as “your information is never shared” must be accurate if hosting, payment and mailing providers receive it. For commercial email, the Spam Act 2003 also matters: messages generally require consent, must identify the sender and need a functional unsubscribe mechanism.
For organisations covered by the Privacy Act, people who have tried to resolve a concern with the organisation may lodge a complaint with the Office of the Australian Information Commissioner, or OAIC. Publishing an independent email address for privacy enquiries gives visitors a direct route before they need the regulator.
A useful policy fits on one page for a personal site. It identifies the operator, provides a contact address, explains what information is collected, states the purposes, lists relevant service providers, describes storage and security, and outlines access, correction and complaint options. Exact retention periods are more helpful than vague promises that data is kept only as needed.
Use direct sentences and ordinary vocabulary. “We collect your email address to send the newsletter you requested” communicates more than “Personal information may be processed for the provision of our services”. Avoid absolute wording unless you can guarantee it, and do not rely on links to complex third-party documents to explain your own practices.
Local context can sharpen the description. An Adelaide reader comparing freelance photographers should be able to see whether an enquiry is used for booking, portfolio analytics or advertising. If a WordPress plugin adds tracking, update the disclosure. If you use a payment processor, name it and explain that card details enter the processor’s system rather than being stored on the site itself.
Cookies are small files stored by a browser. Some keep a login or shopping cart working; others count visits, remember preferences or follow a reader around the advertising network. A personal site should distinguish genuinely necessary functions from optional measurement tools and identify who operates them.
Australia does not currently impose a blanket requirement for every website to obtain consent before placing cookies. That does not make unlimited tracking harmless. If analytics, advertising pixels or cross-site tracking reveal personal information, explain the activity and provide a practical way to decline optional tools where you control them.
Embedded content creates another layer. A YouTube video, Instagram post or social media button may cause the visitor’s browser to contact that platform. Email pixels can report whether a subscriber opened a message. A commuter checking email on free public Wi-Fi at a Brisbane station may receive no meaningful warning about those exchanges from your site alone.
Reasonable security can include HTTPS encryption, strong administrator authentication, current software, restricted hosting access and encrypted backups. It also requires sensible operational habits: remove unused administrator accounts, avoid sharing one password across several services, and ensure third-party plugins come from reputable sources. No website can promise absolute protection, so the policy should describe safeguards rather than guarantee that a breach is impossible.
Breach wording should not create a false legal impression. Australia has no general rule requiring every website operator to report a personal-data breach to the OAIC, although particular organisations and records, including some in the health sector, have specific notification duties. A clear incident process helps you contain access, investigate what happened and contact affected people promptly and honestly.
Retention works best when expressed as a practice rather than an aspiration. Set limits for unsuccessful enquiries, server logs, old contact forms and mailing records. Financial records may need to be kept for the period required under Australian tax law, while unnecessary correspondence can be removed from working email lists. A schedule reviewed periodically is more credible than a single claim that records are deleted immediately.
Before publishing, check that the document describes the site visitors actually use. Confirm the form fields, newsletter service, analytics provider, payment method and any community features. Each listed purpose should connect to a real activity, and every provider mentioned should receive only the information needed for that task.
Treat the “last updated” date as a maintenance signal. Review the policy when a plugin changes, a mailing platform is replaced, overseas storage is introduced or the purposes for collecting information expand. A periodic check will catch old provider names, broken contact addresses and practices that have quietly changed since the previous version.
Keep an archived copy of each version so you can show what visitors saw when they submitted an enquiry. This is particularly useful for a freelance business operating in Australia’s crowded market of sole traders and small studios, where a clear personal commitment can distinguish a professional service. Specificity is the substance of trust: readers should know exactly what you collect, why you collect it, who receives it and what control they retain.