What we collect, and what we do not.
What this site collects when you book a demo, what the application holds for your organisation, and what happens to both. It is short because there is not much of it.
Last updated September 2026.
1. Who we are
Archie is a software product built and run by the team behind it ("we", "us"), working from Sydney, Australia. This policy explains how we handle personal information in connection with the Archie website and the Archie application.
We handle personal information in accordance with the Privacy Act 1988 (Cth) and the Australian Privacy Principles.
2. What we collect
Booking and enquiry information. When you book a demo on this website the form collects your name, your work email address, a phone number and your company, and it accepts an optional note about what you are building. It also records the time you picked and the timezone your browser is set to, because an appointment without both of those is not an appointment. Nothing else on the form is required, and there is no field for anything we have not listed here.
If you write to us by email instead, we hold what you chose to put in the message.
Project content. Documents and data your organisation uploads to the application, such as specifications, drawings, schedules and contracts, together with the deliverables generated from them.
Usage information. Log data generated by using the application, such as authentication events, actions taken on deliverables and technical diagnostics.
3. How we use it
We use booking and enquiry information to hold the appointment, to confirm it, to reach you if the meeting has to move, and to answer what you asked. The phone number exists for the third of those and is not used for anything else.
We use project content solely to provide the service to your organisation: extracting data, computing results and producing deliverables.
We use usage information to secure, maintain and improve the service.
We do not use your project content to train machine learning models, and we do not permit third parties to do so. We do not sell personal information.
4. Storage and security
Data is stored on managed cloud infrastructure. Access to the application is authenticated, and actions on deliverables are role-restricted and logged. Signed deliverables are hashed and locked against modification.
No system is perfectly secure. If we become aware of a data breach affecting your personal information that is likely to result in serious harm, we will notify you and the Office of the Australian Information Commissioner, as the Privacy Act requires.
5. Who else sees it
The booking form posts to this website's own endpoints on this website's own domain. Those endpoints rebuild the submission field by field and pass it on to the Archie API, which holds the calendar. No third party receives the form directly, no advertising or analytics service is sent any part of it, and no calendar credential is ever given to your browser.
Beyond that, we disclose personal information only to the service providers who host and support the operation of the service, under contractual confidentiality obligations, or where we are required by law to disclose it. Where infrastructure is located outside Australia, we take reasonable steps to ensure comparable protections apply.
6. Retention
We retain booking and enquiry information while it is useful for the enquiry and for a reasonable period afterwards. Project content is retained according to the agreement with your organisation. Signed deliverables form part of a project record and are retained for the period agreed with your organisation.
7. Your rights
You may ask for access to, or correction of, the personal information we hold about you by writing to hello@archiebuilds.com.au. If you have a concern about how we have handled your information, tell us first and we will respond within a reasonable time. You may also complain to the Office of the Australian Information Commissioner.
9. Contact and changes
Questions about this policy can be sent to hello@archiebuilds.com.au. We may update this policy from time to time, and the current version is always the one published on this page.