Privacy Policy

From builders. When you create an account and use Gus:

• Your name, business name, email address and Australian mobile number.
• The suburb, postcode and service areas you select, and your plan and billing status.
• Your brand kit: licence number and state, ABN, business phone, colours and the suburbs you service.
• Sign-in records — how you signed in (Google, an emailed code, or an operator password) and when.
• If you pay for a plan, your billing details are held by Stripe; we see your plan and payment status, not your card number.

From Xero, if you connect it. Signing up with Xero asks only to read your organisation, invoices, contacts and chart of accounts. Connecting Xero from the dashboard also asks for permission to create bills and invoices, which the Paperwork features use to add receipts as draft bills and prepare invoices for you to approve. From this we calculate job margins and profit. You can disconnect Xero at any time from the dashboard.

From homeowners. When a homeowner contacts a builder through Gus — by WhatsApp, a tracked phone number, or a Facebook or Instagram lead form — we receive their name (where given), phone number, email (on lead forms), suburb or postcode, the details of the job they describe, their messages, and any site-visit times they agree. Calls to a tracked number are logged with time, duration and outcome.

Receipts and photos a builder sends to Gus, such as supplier dockets and job photos.

We use this information only to run Gus for the builder it belongs to:

• To configure local features and campaigns for the service areas you select.
• To power the WhatsApp assistant — answering homeowners on the builder’s behalf, qualifying the job, and proposing site visits for the builder to approve.
• To read receipts, calculate job margins and produce the monthly and daily reports.
• To provide the operations dashboard, send sign-in codes, and bill for paid plans.
• To keep Gus secure, prevent misuse, and keep an audit record of the actions it takes on a builder’s behalf.

We never sell builder or homeowner data, and we do not use one builder’s customers or figures for another builder. Where a builder uses advertising features, Gus may send Meta an aggregated conversion signal (a margin value for a completed job) so their campaigns can be measured; this is described in the product before it is switched on.

Gus uses AI models to write replies to homeowners and to read receipt photos. Messages and images sent for that purpose are processed by our AI providers (see section 4). Replies are checked against a claims filter before they are sent, so Gus does not make promises about pricing, guarantees or timeframes that the builder has not recorded. A builder can take over any conversation at any time.

Gus does not give tax, BAS or legal advice. Its figures are bookkeeping calculations from your own records.

We share information with these providers only as needed to run Gus:

• Neon (PostgreSQL database) and Render (application hosting) — where Gus’s data is stored and processed.
• Vercel — hosts this website and the dashboard.
• Meta — the WhatsApp Cloud API for messages, and Facebook and Instagram for lead forms, advertising and posts a builder approves.
• Xero — accounting data, when a builder connects it.
• Anthropic and Google — AI models that draft replies and read receipts.
• Resend — emails your sign-in codes.
• Google — “Continue with Google” sign-in, if you use it.
• Stripe — payments for paid plans.
• Twilio — tracked phone numbers and call logs, where a builder uses them.
• TikTok — posts a builder approves, where they use it.
• Rocket.Chat — our support workspace, used when a conversation is handed to a person.

Overseas storage. Our database and application servers are in Singapore, and some of the providers above process data in other countries, including the United States. We choose providers that protect personal information to a standard comparable to the Australian Privacy Principles.

• Tenant isolation. Every builder’s data is separated at the database level with row-level security, so one builder’s session cannot read another’s records.
• Encryption. Data is encrypted in transit with TLS. Access tokens for connected services (such as Xero and Meta) and homeowner phone numbers are encrypted at rest (AES-256-GCM), and phone numbers are looked up by a keyed hash rather than stored in the clear.
• Sign-in. Sign-in codes are single-use, expire after 10 minutes and are stored only as a keyed hash; operator passwords are stored only as a bcrypt hash.

We keep information while your account is active. When you close your account, or ask us to delete your information, we delete or de-identify it, except for records we must keep by law — such as billing records for tax purposes — and the audit record of actions Gus took on your behalf, which is kept so those actions can be accounted for.

You can ask us for a copy of your information, ask us to correct it, or ask us to delete it. Builders can also ask for an export of their records at any time, on any plan, including the free Numbers tier.

Homeowners: your builder decides how your enquiry is handled, and is usually the best first contact. You can also contact us directly and we will work with the builder to respond.

Email hello@gus.build. We will respond within a reasonable time, usually within 30 days.

If you are not satisfied with how we handle a privacy complaint, you can contact the Office of the Australian Information Commissioner at oaic.gov.au.

We will update this page when what we collect or who we share it with changes, and change the date at the top. For significant changes we will tell builders by email or in the dashboard.