Spectrum Sales Pipeline by Spectrum Coach

Data Processing Agreement

Last updated: 7 November 2026

The short version.

  • Your company (the builder) controls the personal information about its clients and leads in the app. We process it only to run the app for you.
  • We keep it secure, and we use only the subprocessors listed here.
  • We tell you promptly about any data breach.
  • When you leave, we give you your data and delete it if you ask.

1. Parties and how this applies

1.1 This Data Processing Agreement ("DPA") is between:

1.2 This DPA forms part of our Terms of Service. It applies automatically when you accept those terms and for as long as we process Customer Personal Information. If this DPA and the Terms conflict about Customer Personal Information, this DPA prevails.

1.3 We offer the app to businesses throughout Australia. Wherever the Customer is located, this DPA operates alongside these Commonwealth laws:

1.4 Australian privacy law doesn't formally use the terms "controller" and "processor". This DPA uses them, in their commonly understood sense, to describe who decides how information is handled (the controller) and who handles it on their behalf (the processor). Both parties remain responsible for their own obligations under the Privacy Act 1988 (Cth) where it applies to them.

2. Definitions

3. Roles and instructions

3.1 You're the controller of Customer Personal Information. You decide what's collected, why, and how it's used. We're the processor.

3.2 We process Customer Personal Information only:

3.3 If we believe an instruction breaks the law, we'll tell you and may decline to follow it.

3.4 We won't sell Customer Personal Information. We won't use it for our own marketing or to profile individuals, and we won't combine it with other customers' data.

4. Our obligations

5. Your obligations

You're responsible for:

6. Security

6.1 We take reasonable technical and organisational steps to protect Customer Personal Information from misuse, interference, loss and unauthorised access, change or disclosure (APP 11). Schedule 2 describes the current measures.

6.2 We may update these measures over time, but we won't reduce the overall level of protection.

7. Subprocessors

7.1 You authorise us to use the subprocessors listed in Schedule 3.

7.2 We'll give account owners at least 30 days' notice, by email or in the app, before we add or replace a subprocessor that processes Customer Personal Information. If you have reasonable grounds to object, you can tell us within that time. If we can't address your objection, you can cancel, and we'll refund any fees prepaid for the period after cancellation.

7.3 We'll only use subprocessors that are bound by data-protection and security terms at least as protective as this DPA. We remain responsible for their performance.

8. Overseas disclosure (APP 8)

8.1 The app's database and stored files are hosted in Sydney, Australia (AWS ap-southeast-2, through Supabase).

8.2 Some subprocessors are based in, or may process or access information from, the United States and other countries, as shown in Schedule 3. Before we disclose Customer Personal Information overseas, we take reasonable steps to make sure the recipient won't breach the APPs. We do this by choosing established providers that have published security and data-protection terms.

8.3 You agree that you'll tell your clients and leads, for example in your own privacy policy, that their information may be disclosed overseas as described here.

9. Data breach notification

9.1 If we become aware of a Data Breach, we'll notify you without undue delay, and in any case within 72 hours. We'll tell you, as far as we know at the time:

9.2 We'll take reasonable steps straight away to contain the breach and reduce any harm. We'll also give you the information and help you reasonably need to assess, within the 30 days the Privacy Act allows, whether it's an Eligible Data Breach.

9.3 If it is an Eligible Data Breach, the parties will agree who prepares the statement to the OAIC and who notifies the affected people, as Part IIIC allows. If we can't agree in time, each party may notify as the Act requires. We won't notify your clients directly without consulting you first, unless the law requires it.

9.4 Our notice of a Data Breach isn't an admission of fault or liability.

10. Requests and assistance

10.1 If someone asks us for access to, or correction of, their information in your workspace, we'll pass the request to you promptly and won't respond to it ourselves unless you ask us to. Most requests can be handled in the app, because you can view, edit, export and delete client records.

10.2 We'll give you reasonable help with privacy impact assessments, regulator enquiries and complaints that relate to our processing.

11. Return and deletion on termination

11.1 You can export Customer Data from the app at any time, including when your workspace is read-only after a failed payment or cancellation.

11.2 We never delete Customer Data automatically when a subscription ends. It stays in your read-only workspace so you can come back, or export it.

11.3 When you ask us in writing to delete it (an owner can email fred@spectrumcoach.com.au):

11.4 We may keep information that the law requires us to keep, such as billing and tax records. It stays protected under this DPA for as long as we hold it.

12. Information and audits

When you reasonably request it, and no more than once a year (or after a Data Breach), we'll give you information you need to check that we're complying with this DPA. This can include a written description of our security measures and our subprocessors' published security reports or certifications. Any further audit must be agreed in advance, at your cost, and must protect the confidentiality of other customers' data.

13. General

Schedule 1: Processing details

Subject matterProviding the Spectrum Sales Pipeline app: hosting, storing and displaying the Customer's sales pipeline data
DurationFor the subscription, and afterwards until the Customer asks for deletion (see section 11)
Nature and purpose
  • Storing, organising, retrieving, displaying and exporting records
  • Receiving website and advertising enquiries into the pipeline
  • Reports and forecasts
  • Access control by role
  • Backups, security and support
People concerned
  • The Customer's clients, prospective clients and leads (home buyers, including people who submit website or advertising enquiries)
  • The Customer's staff and other users
Types of information
  • Names, email addresses and phone numbers
  • Enquiry details: what the person is interested in, where they want to build (suburb or postcode), their journey stage, whether they have land, and comments
  • Build type, buyer type, budget and timing
  • Dwelling, lot and street address details
  • Pipeline stage, meeting dates and outcomes
  • Lead source and campaign or lead IDs
  • Free-text notes, tasks and uploaded documents
  • For users: their name, email, role and activity history within the app
Sensitive informationNot required by the app. The Customer should avoid storing it.

Schedule 2: Security measures

Schedule 3: Subprocessors

SubprocessorPurposeLocation
Supabase, Inc.Database, authentication, file storage, server functions, and account emails (sign-up confirmation and password reset, created by Supabase's authentication service and delivered by Resend)Data hosted in Sydney, Australia (AWS ap-southeast-2). The company is in the USA, and its support or operations staff may access the data from overseas.
Amazon Web Services (as Supabase's infrastructure provider)The data centre underneath the database and storageSydney, Australia
ResendEmail delivery: team invites, password-reset and sign-up emails. Resend receives recipients' email addresses and the email content (for an invite, the inviter's name and company name). It doesn't receive client or lead records.USA
Stripe (Stripe Payments Australia Pty Ltd and affiliates)Subscription billing. Stripe receives the Customer's billing contact details, not client or lead records.Australia, USA and other countries
Netlify, Inc.Hosting and delivery of the app's web pages. Netlify processes request data such as IP addresses, not stored client records.USA, through a global network of servers
Google LLC (Google Fonts)Font delivery. Google receives users' IP addresses and browser details.USA and other countries
Google LLC (Google Maps Platform, Places API)Address suggestions on a client's build address, when the Customer has this switched on. Google receives the street text being typed so it can return Australian matches. It does not receive the rest of the client record, and the device's location is not sent. Until the feature is switched on, Google does not receive Customer Personal Information for this purpose.USA and other countries where Google operates
jsDelivrDelivery of the open-source code libraries the app uses. jsDelivr receives users' IP addresses.Global
Functional Software, Inc. (Sentry)Error diagnostics. Sentry receives technical error reports from the app (error details, page address without query strings, browser type and users' IP addresses). Reports are configured to strip names and email addresses, and they aren't linked to user accounts.USA

Services that the Customer connects to the app itself, such as its own website, Google or Meta lead forms or Zapier, are the Customer's own providers. They aren't our subprocessors.