Privacy
Not yet written.
This page is deliberately empty of policy text. A privacy policy has to describe what this business actually does with personal information — not what a template says a business might do.
Do not publish invented policy text here. A policy that describes practices the business does not follow is worse than no policy: it is a representation the client can be held to. This page ships only after the questions below are answered by LetsBuild and the wording is reviewed by the client's solicitor against the Australian Privacy Principles.
What is collected
Confirmed for this site: name, email, phone, suburb, project type, stage, timeframe and message via the two enquiry forms, plus a documentation link on the architect form. Anything collected elsewhere — phone enquiries, site visits, a CRM — needs listing.
Where it goes
Form submissions are received and stored by the site host. Confirm whether enquiries are also copied into a CRM, a mailing list, or a shared inbox, and who has access.
How long it is kept
A stated retention period for enquiries that do not become projects, and for those that do.
Third parties
Any analytics, advertising pixels, email platform or booking tool must be named. This site currently loads no third-party scripts and sets no analytics cookies — if that changes, this page changes with it.
Access, correction and complaints
How someone asks what is held about them, has it corrected or deleted, and who to contact if they are unhappy with the answer.
Breach response
A named person responsible, and awareness of the OAIC Notifiable Data Breaches obligation. Flagged for the client conversation — not legal advice.
Placeholder page · no policy text published · pending client input and legal review