Legal
Privacy Policy
Notice of amendment (13 September 2026). Clauses 8.4 and 10(b) were amended to reflect what a connected AI application may do where a customer has enabled the optional AI connector: with write access it may take off and scope the customer's projects, and may change or delete records a person created, and restructure an estimate, where a user confirms the change in the AI application's chat. Everything it does remains marked as AI-created and recorded in an audit log with prior values, and the customer's own review remains the check on it. The Software Terms of Use and Licence were amended on the same date (clause 9).
1. About this policy
1.1 Estimator Plus Pty Ltd (ABN 79 699 842 227) (we, us, our) provides the Estimator+ construction estimating and tendering platform (the Platform). This Privacy Policy explains how we handle personal information in connection with the Platform and our website, consistent with the Privacy Act 1988 (Cth) (Privacy Act) and the Australian Privacy Principles (APPs).
1.2 “Personal information” means information or an opinion about an identified individual, or an individual who is reasonably identifiable, as defined in the Privacy Act.
1.3 By using the Platform, you agree to the handling of personal information as described in this policy.
2. Whose information this policy covers
This policy covers personal information about: the account users of our customers (our customers' staff); individuals whose details our customers enter into the Platform (such as subcontractors and clients) or that appear in drawings and documents our customers upload; individuals who contact us or use our website; and individuals whose business contact details we collect from public sources to tell them about Estimator+.
3. Personal information we collect
We collect the following kinds of personal information:
(a) Account users (our customer's staff): email address, first and last name, job title, account timestamps, and a record of your acceptance of our terms and this policy (the version and the time) and of our AI connection notices (the version). We do not collect date of birth, home address, phone number, or photo for account users.
(b) Business details (of our customer): company name, address, phone, email, ABN, country and logo, and the name, ABN, address and logo of any second trading identity the customer adds. These may appear on tender documents generated through the Platform.
(c) Third-party contacts entered by our customer: for subcontractors: name, contact, email, phone, postcode and trades; for clients: name, contact, email and phone; and the quotes our customer records from subcontractors. This information is entered by our customer, not collected by us directly from those individuals.
(d) Customer content: plan drawings (stored as individual plan page images together with the text read from them; the original PDF is not retained), measurements, estimates, pricing, quotes, project notes, and the notes, questions and project records a connected AI application files. Drawings often show personal information about other people, such as property owners' names, site addresses, and the names of architects, engineers, designers and builders' staff. This information is uploaded by our customer, not collected by us directly from those individuals.
(e) Billing records: we use Stripe to process payments. Your card details, billing name and address, any ABN you enter at checkout, and full invoice, refund and dispute records are collected and held by Stripe on its systems; we do not store them. We give Stripe your company name, a billing email address (at first, the email address of the administrator who subscribes; an administrator can change it) and a reference to your account. From Stripe we hold only your Stripe customer and subscription identifiers, your subscription status, the number and type of seats on your plan, any discount applied, and subscription dates (such as trial, renewal and cancellation dates). The ABN we hold is the one entered in your business details (clause 3(b)). We do not collect or store full card numbers, PAN or CVV; these are handled entirely by Stripe.
(f) Operational information:
(i) AI connection records, where our customer connects an external AI application: which applications each user has connected and when, and the company's AI access setting;
(ii) an audit log of changes made by connected AI applications (which user and application made each change and what changed, including prior values);
(iii) a record of each exchange between a connected AI application and our AI connector (the connector record): the request the application sent and the response it was shown (images are replaced by a reference to the image), with the user, application and company, the time, and technical details the application's software sends, such as its name;
(iv) reports a connected AI application sends us when it cannot do something it was asked to do or finds a fault: what was asked, what it tried and its description of the problem;
(v) records of which plan pages a connected AI application viewed, and when each user last opened each project;
(vi) login session information (one active session per user), including the IP address and browser recorded with each sign-in; and
(vii) technical information our hosting providers log when you use the Platform or our website, such as IP address, browser type and the pages requested.
(g) Enquiries and demo requests: when you ask us to contact you or to book a demonstration through our website, we collect your name, email address, phone number, company name and role, how you heard about us, and the advertising campaign details in the link you followed to our website (clause 4.3), together with anything else you choose to tell us and our notes of our calls and other dealings with you.
(h) Business contacts from public sources: the names, business email addresses and business phone numbers of builders and their staff that we find in public sources, such as tender listings and company websites, together with the tender or listing concerned and our notes of our dealings with them.
4. How we collect personal information
4.1 We collect personal information:
(a) when account users register for and use the Platform;
(b) when our customers enter business details and third-party contact details into the Platform;
(c) when customers upload plan drawings and project content;
(d) through operational logs generated by use of the Platform (including the AI connection, audit and connector records described in clause 3(f));
(e) from Stripe, when you subscribe or a payment event occurs (clause 3(e));
(f) when you contact us or otherwise interact with us or our website; and
(g) from public sources, such as tender listings and company websites, for the business contacts described in clause 3(h).
4.2 Where our customer enters or uploads personal information about a third party, our customer is responsible for having the right to provide that information to us (see clause 12).
4.3 Cookies, advertising and measurement on our website:
(a) Our public website (not the Platform you sign in to) uses cookies and similar technologies from Google (Google Ads) and LinkedIn (the LinkedIn Insight Tag). We use them to measure which of our advertisements and web pages lead to enquiries and demonstration bookings, and to show our advertisements on Google, YouTube and LinkedIn to people who have visited our website. These tools may collect your IP address, device and browser details, the pages you visit and the page that referred you. Google and LinkedIn handle that information under their own privacy policies, may combine it with other information they hold about you, and may store and process it outside Australia, including in the United States (Google and LinkedIn) and Ireland (LinkedIn).
(b) When you arrive at our website from a link carrying campaign details (such as UTM tags or an advertising click identifier), or from another website, we keep those details, the page you arrived on and the website that referred you in your browser’s local storage until you book a demonstration. If you book, we keep them with your booking, together with your answer to “How did you hear about us?”, and clear them from your browser. We also send Google a hashed (encoded) copy of your email address and phone number, which Google uses to match your booking to an advertisement you clicked.
(c) You can block or delete cookies in your browser settings, turn off personalised Google advertising at myadcenter.google.com, and turn off LinkedIn advertising based on your activity in your LinkedIn settings under “Advertising data”. Blocking cookies will not stop you using our website or booking a demonstration.
5. Why we collect, hold, use and disclose personal information
5.1 We collect, hold, use and disclose personal information to:
(a) create and administer accounts;
(b) provide, support, secure and operate the Platform, including generating estimates, tenders and Submissions;
(c) provide the plan-reading feature and operate the AI connector, including keeping records of what connected AI applications were shown and changed so that we can investigate faults and resolve disputes (see clauses 7 and 8);
(d) process subscriptions and payments;
(e) communicate with users about the service, including service and administrative messages;
(f) respond to enquiries, and arrange, conduct and follow up demonstrations of the Platform, including by telephoning you on a number you give us, and contact builders whose business contact details we collect from public sources (clause 3(h)) about Estimator+;
(g) improve, develop and analyse our products and services, and develop new features;
(h) market our own products and services to our customers and to the business contacts described in clause 3(h), subject to the opt-out arrangements in clause 5.2;
(i) measure which of our advertisements and web pages lead to enquiries and demonstrations, and show our advertisements to people who have visited our website (clause 4.3); and
(j) comply with our legal obligations.
5.2 Direct marketing and opt-out: We may use the contact details of our customers and their account users, and the business contact details described in clause 3(h), to send marketing communications about our own products and services. Account users receive our product newsletter unless they unsubscribe. You may opt out of receiving marketing communications from us at any time by using the unsubscribe function in the message or by contacting us via the details in clause 19 and we will stop sending them. We do not use personal information for third-party direct marketing, and we do not sell personal information.
6. Disclosure and our service providers (sub-processors)
6.1 We disclose personal information to the following service providers who help us deliver the Platform:
| Provider | Role | Information involved | Location |
|---|---|---|---|
| Supabase | Core database, authentication, server functions, hosting | All application data | Database in Sydney, Australia; server functions may run in other regions (Supabase, Inc. is a US company) |
| Google (Gemini) | Plan reading: naming plan pages from their title blocks (clause 7) | Images of plan pages | United States, and other countries where Google processes data |
| Cloudflare R2 | Storage of plans, logos and the connector record | Plan page images and the text read from them, logos, the connector record (clause 3(f)) | Asia-Pacific region |
| Cloudflare Workers | Moving plans and logos to and from storage | Plan page images and the text read from them, logos, in transit | Cloudflare's global network (Cloudflare, Inc. is a US company) |
| Resend | Transactional email, and our product newsletter list | Recipient email address and email content; for the newsletter list, name, email address and company name | United States |
| Google (Google Workspace) | Our business email, including support@estimator.plus | Messages you send us and we send you, and the contact details in them | United States, and other countries where Google processes data |
| Stripe | Subscription billing and card payments | Card, billing address and ABN (collected directly by Stripe; we do not see card data); your company name, billing email address and a reference to your account (from us) | United States |
| Fly.io | Hosting for the AI connector (see clause 8) | Data passing between connected AI applications and the Platform, in transit; the connector holds no database credentials of its own | Sydney, Australia (Fly.io, Inc. is a US company) |
| Netlify | Hosting our website and the Platform's web pages | IP address, browser information and the pages requested | Netlify's global network (Netlify, Inc. is a US company) |
| Anthropic and OpenAI | AI applications our staff use under our own accounts when supporting customers and operating the Platform (clause 10) | Information our staff work with, which may include project content, plan pages, pricing and contact details | United States |
| Google (Google Ads) | Advertising measurement and remarketing on our public website (clause 4.3) | Website visit details; for demonstration bookings, a hashed email address and phone number | United States |
| Advertising measurement and remarketing on our public website (clause 4.3) | Website visit details | Ireland and United States |
6.2 We may also disclose personal information where required or authorised by law, to protect our rights, or in connection with a sale or restructure of our business (subject to appropriate confidentiality).
6.3 We do not sell personal information, and we do not disclose it for third-party direct marketing.
6.4 An external AI provider that our customer connects to the Platform is chosen and engaged by the customer, not by us, and is not one of our service providers, in accordance with clause 8. The AI applications our own staff use are described in clause 10.
7. Plan reading and our AI provider
7.1 When plans are uploaded, the Platform reads them so that each plan page is named, indexed and searchable within the Platform. Our own software reads the text already in the drawing. The Platform uses an AI provider to name plan pages: it sends the AI provider an image of each new plan page that arrives without a name, and the AI provider's model reads the page's drawing number, title and revision from its title block. Plan reading is the only feature of the Platform that sends data to an AI provider we engage; clause 10 describes the AI applications our staff use. The Platform no longer includes a built-in AI assistant, AI scope drafting or text tidy-up.
7.2 Current provider; provider may change: Our current AI provider for plan reading is Google (Gemini). We may also use it to read plan pages and extract their text. We may change or add AI providers for this feature from time to time, provided any replacement or additional provider is a reputable provider of comparable services engaged on terms consistent with this policy. We will update this policy to reflect any change of AI provider.
7.3 What is and isn't sent: We send the AI provider images of plan pages. A plan page can show personal information about other people (clause 3(d)), which the image carries. We do not send account users’ names, email addresses or login details, and there is no chat, question or user-typed content to send.
7.4 How the AI provider handles it: The AI provider acts as our processor and does not use prompts or responses to train its models. The provider may keep data for a limited period for abuse detection and legal compliance. This processing is governed by the AI provider's data processing terms for products where it acts as a data processor.
7.5 Plan reading is assistive. Sheet names and any text extracted from plans are generated automatically and may be inaccurate or incomplete. Our customers are responsible for checking them. This is also addressed in the Software Terms of Use and Licence.
7.6 Automated decision-making: The plan-reading feature names plan pages and reads their text; it does not make decisions that produce legal or similarly significant effects about individuals. External AI applications connected by our customers (clause 8) are operated by or for the customer, not by us. If our use of automated processing changes such that it is captured by automated decision-making transparency requirements, we will update this policy to disclose the required information.
8. AI applications connected by our customers
8.1 Our customers can connect their own external AI application (such as an AI assistant like Claude or ChatGPT) (called an AI Agent in our Software Terms of Use and Licence) to their data in the Platform through our AI connector. The connector is hosted in Australia and holds no database credentials of its own: it passes each request through as the signed-in user, and the Platform’s access controls apply to every read and write. The connector keeps the connector record described in clause 3(f) in our file storage (clause 6.1).
8.2 Customer’s AI, not ours: The AI provider is selected, authorised and engaged by our customer. When a customer connects an AI application, information that application reads (which may include project details, estimates and pricing, subcontractor and client names and contact details, plan pages and extracted plan text, and project notes) is transmitted to that AI provider at the customer’s direction. That provider’s handling of the information is governed by the customer’s own agreement with that provider, not by this policy, and the provider is not our sub-processor.
8.3 Consent and control: AI application access is off by default. It operates only if a customer administrator enables it at company level (read-only or read-and-write) and the individual user approves the specific application through a consent screen. Whether a connected application may write follows the company-level setting. The company-level setting can be changed, and an individual connection revoked, at any time from the AI connector page. These settings apply only to external AI applications connected by our customer: they do not switch off the plan-reading feature described in clause 7, which operates as part of the Platform whenever plans are uploaded, and they do not govern the AI applications our staff use under clause 10.
8.4 Safeguards and audit: A connected AI application with write access can add scope items, headings and folders, takeoff measurements and area outlines, quotes and their figures, subcontractor contacts, notes, questions for the customer’s client and its own working notes, set the scale of a plan sheet a person has not calibrated, and change, move or remove the items it created itself. It can also change, without asking first, the name, quantity, unit or rate of a scope item, the name of a heading, the wording of a note, the figures on a quote and a contact’s details, including ones a person created; a change that would move the price of the tender waits until the user answers a confirmation prompt. It can move or delete records a person created, and restructure an estimate, only after the user confirms that specific change in the AI application’s chat in response to a confirmation prompt the Platform returns; it is instructed to enter rates and remove contacts only on the user’s express instruction; and it cannot pick quotes, set margins, or modify the submitted copies of tenders, plan drawings, users or settings. The scope items, measurements and notes it creates are marked as AI-created, and every change it makes is recorded in an audit log with prior values (including any confirmation prompt and the answer given), which is designed to allow changes to be identified and reversed. Every exchange between a connected AI application and the connector is also kept in the connector record (clause 3(f)). These safeguards do not replace the customer’s review: anything an AI application creates or changes must be checked by the customer before it is relied on.
8.5 If you are a subcontractor or client: your details may be included in the information a customer’s connected AI application reads. The customer is responsible for having a basis to disclose your information to its chosen AI provider (see clause 12).
9. Cross-border disclosure (APP 8)
9.1 Some personal information is disclosed to, or stored by, recipients outside Australia:
(a) United States (and, for Google, other countries where it processes data): images of plan pages, and any personal information on them (our AI provider, for plan reading); information our staff work with using AI applications under our own accounts (Anthropic and OpenAI, clause 10); email addresses and email content, and our newsletter list (Resend); our business email (Google Workspace); billing information including ABN (Stripe, collected directly), and the company name, billing email address and account reference we give Stripe; website visit and advertising measurement details (Google and LinkedIn, clause 4.3).
(b) Asia-Pacific region: plans, the text read from them, logos and the connector record (Cloudflare R2). This storage is across the Asia-Pacific region and is not limited to Australia.
(c) Ireland: website visit and advertising measurement details (LinkedIn, clause 4.3).
(d) Global networks: plans and logos in transit to and from storage (Cloudflare Workers); the IP address, browser information and pages requested when you use our website and the Platform's web pages (Netlify); and information handled by our server functions, which may run outside Australia (Supabase).
9.2 Our primary application database is hosted in Australia (Supabase, Sydney), and our AI connector is hosted in Australia (Fly.io, Sydney). The connector record the AI connector keeps is stored in the Asia-Pacific region (clause 9.1(b)).
9.3 Before disclosing personal information overseas, we take reasonable steps to ensure the overseas recipient handles it consistently with the APPs.
9.4 Customer-directed disclosures to connected AI providers: Where our customer connects an external AI application (clause 8), information read by that application is disclosed to the customer’s chosen AI provider wherever that provider processes it (commonly the United States). That disclosure is made at the customer’s direction: the customer selects and authorises the provider, and is responsible for that disclosure.
10. Operator access
Our staff who are designated as platform administrators can access customer accounts and data across all customers through administrative tools (including project content, client names, pricing and plan pages) for the purposes of support, account management, work we do on a customer's projects at its request (including copying a project into or out of its account) and operating the Platform. Access is limited to these purposes.
For support, a platform administrator can switch on support access for a limited window (currently eight hours at a time). During that window they hold an administrator's access to every customer account, can make changes in it, and can connect an AI application to a customer's project through our AI connector, whatever the customer's own AI access setting (clause 8.3). Our staff use AI applications under our own accounts (currently Anthropic's Claude and OpenAI's Codex) in this work and in operating the Platform, so information they work with, which may include project content, plan pages, pricing and contact details, is processed by those providers in the United States. When our staff have one of a customer's projects open in the Platform, anyone else in that project sees them marked with the Estimator+ mark, and changes they make through an AI application are recorded in the AI change audit log (clause 3(f)) under their own account.
11. Payments and ABN
Card payments are processed by Stripe on its hosted pages. Your full card number and CVV go directly to Stripe: we never receive or store them. We give Stripe your company name, a billing email address and a reference to your account. We receive the billing records described in clause 3(e) to administer subscriptions, issue invoices and receipts, comply with our tax obligations and resolve payment issues. You can enter your ABN on Stripe's checkout page so it appears on your tax invoice; Stripe holds it for tax and invoicing purposes. We hold the ABN entered in your business details (clause 3(b)). Stripe also handles your information under its own terms and privacy policy.
12. Third-party information entered by customers
Where our customer enters or uploads personal information about a third party (such as a subcontractor or client, or a person named on a drawing), the customer is responsible for having the necessary right or basis to provide that information to us and for informing those individuals as required, including where our AI provider will process plan pages (clause 7) and where the customer’s connected AI application will read that information (clause 8). We handle that information on the customer’s instructions to operate the Platform, as described in the Software Terms of Use and Licence.
13. Security
(a) We take reasonable steps to protect personal information, including: isolating customer data at the database level so it cannot be accessed across customers; hosting our primary database in Australia; encrypting data in transit; limiting each user to one active login session (to deter credential sharing; signing in elsewhere makes earlier sessions read-only); not storing card data (Stripe handles it entirely); not using third-party tracking or analytics tools inside the Platform (our public website uses the advertising tags described in clause 4.3); and applying a content-security policy that restricts what the application connects to.
(b) For AI connections: the connector holds no privileged credentials, and keeps the connector record in a storage area of its own, separate from customers' plans; every read and write by a connected AI agent or application is enforced by database-level access controls as the signed-in user; access by a customer's own AI applications is off by default and requires both an administrator setting and per-user consent, each revocable at any time; and AI writes are marked and audited with prior values so they can be identified and reversed; a connected AI agent or application can modify or delete records it created, can move or delete records a person created only after the user confirms that change in its chat, and can edit some details of records a person created without asking first (clause 8.4).
(c) No method of transmission or storage is completely secure, and these measures are a description of our practices, not a guarantee.
14. Retention
14.1 We retain personal information only for as long as it is reasonably needed for the purposes described in this policy, or for any period we are required by law or a court or tribunal order to keep it.
14.2 While an account is open, information in the account is retained because the service requires it: customers use the Platform as their working record of projects, estimates and tenders. A customer can delete a project in the Platform at any time. Deleting a project deletes its records in our database at once, including its plans and Submissions; the Platform then asks our file storage to delete the project's files, and if that request does not complete, the files can remain in storage. The AI change audit log entries and the connector record for a deleted project are kept as clause 14.9 describes.
14.3 If your account is deactivated for non-payment, or your Subscription ends, the information in the account is retained while the account remains inactive: you can still sign in to access and export it. We do not delete inactive accounts automatically. If no one signs in to an account for 2 years, we may delete or de-identify the account and its information on reasonable prior notice, unless we are required to retain particular information or one of the retention categories below applies.
14.4 If we approve an account administrator's request to delete the account (clause 15.2), we delete the account's users and its records in our database 30 days after the request, including its projects, Submissions, contacts, notes and AI change audit log. Once deleted, these cannot be recovered, except from the backups described in clause 14.6 while those last. The account's files in our file storage (plan page images, the text read from them and logos) are not removed automatically by that deletion; we take reasonable steps to remove them once they are no longer needed (clause 14.5). The connector record is kept as clause 14.9 describes.
14.5 When personal information is no longer needed for any purpose under this policy (including after account closure), and no law or order requires us to keep it, we take reasonable steps to destroy it or ensure it is de-identified.
14.6 Information that has been deleted may persist in our encrypted operational backups for a limited period (up to 7 days) before those backups are overwritten. Backups are maintained for service continuity and are not a means of restoring individual account data on request.
14.7 Submissions are kept with the project they belong to: deleting a project deletes its Submissions, and deleting an account deletes them with it (clause 14.4). Export and keep your own copies of submitted tenders before deleting a project or asking us to delete your account.
14.8 We may keep our correspondence about a request to delete an account or information, as a record of what was asked and how we dealt with it.
14.9 The audit log of changes made by connected AI applications is never pruned while the account exists, including its entries for deleted projects, and is deleted with the account (clause 14.4). The connector record (clause 3(f)) has no set retention period: we keep it as evidence of what connected AI applications were shown and did, and it is not removed when a project or an account is deleted.
14.10 Stripe keeps billing records (clause 3(e)) on its systems under its own terms, including after account closure, for the periods required by tax and corporations law. The Stripe identifiers and subscription details we hold are deleted with the account (clause 14.4).
14.11 Enquiry, demonstration and business-contact records (clauses 3(g) and 3(h)) are kept while we may deal with you, and we take reasonable steps to destroy or de-identify them once they are no longer needed (clause 14.5).
15. Access, correction and deletion
15.1 You may request access to, or correction of, the personal information we hold about you by contacting us via the details in clause 19. We will respond within a reasonable period and may need to verify your identity.
15.2 A user or an account administrator may request deletion of an account or data by contacting us via the details in clause 19. Australian privacy law does not confer a general right to have information deleted, and we do not promise deletion on request: we review each request and decide it in accordance with this policy and our legal obligations, and we will tell you the outcome, including if we decline in whole or in part.
15.3 Information we keep under clause 14 for our own records (including the connector record and our correspondence about deletion requests), and billing records Stripe keeps, may not be deleted in response to a request, and where we approve a request we may de-identify rather than delete.
15.4 Where the information was entered into the Platform by a customer (for example, a subcontractor's details), we may refer the request to that customer, as the information is held on the customer's instructions.
15.5 Where an individual user is deleted, their work product remains in the customer's account and the authorship link is removed. The AI change audit log and the connector record keep the internal account identifier of the user who made each change or exchange.
15.6 There is no fee to make a request, though we may charge a reasonable cost for access in limited circumstances permitted by the APPs.
16. Anonymity
Where lawful and practicable, you may deal with us anonymously or using a pseudonym, for example when making a general enquiry. This is generally not practicable for account users, who need an identified account to use the Platform.
17. Complaints
17.1 If you believe we have breached the APPs, please contact us via the details in clause 19 with details. We will acknowledge your complaint and aim to respond within a reasonable period.
17.2 If you are not satisfied with our response, you may complain to the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au.
18. Changes to this policy
18.1 We may update this policy from time to time by posting the updated version at estimator.plus/privacy-policy. The “last updated” date at the top of this policy shows when it last changed.
18.2 Where a change materially changes how we handle your personal information, we will give you reasonable prior notice by email or in-Platform notice before it takes effect, and clause 1.4 of the Software Terms of Use and Licence (including your right to cancel before the change takes effect) applies. Nothing in this clause limits any separate notice we must give, or consent we must obtain, under the Privacy Act.
19. Contact us
Estimator Plus Pty Ltd (ABN 79 699 842 227)
Privacy contact: support@estimator.plus