Housing Match
Specialist Disability Accommodation Provider Portal
Data Processing Agreement
The terms on which Housing Match processes personal and sensitive information on behalf of Australian provider organisations, including processing activities, AI processing, security controls, sub-processors, audit, retention and breach notification.
Version
v1.0
Next review
17 January 2027
Document owner
Housing Match
Effective date
17 July 2026
Change history
| Version | Date | Change |
|---|---|---|
| v1.0 | 17 July 2026 | Initial version prepared for the Customer Assurance Pack, verified against implemented processing activities, database schema, AI processing, security controls, audit logging and hosting configuration. |
Purpose
This Data Processing Agreement (DPA) sets out the terms on which Housing Match processes personal and sensitive information on behalf of Australian provider organisations that use the Housing Match Platform. It is written for procurement teams, privacy officers and legal advisers, and is suitable for Australian solicitor review.
This DPA aligns with the Australian Privacy Principles (APPs) and uses the terms "Controller" and "Processor" — familiar to enterprise procurement — to describe the roles of the Customer and Housing Match respectively. Both parties remain APP entities under the Privacy Act 1988 (Cth).
Scope
This DPA applies to:
- All personal and sensitive information the Customer uploads to, or creates within, the Platform, including participant profiles, resident profiles, documents, applications, messages and property data.
- All processing Housing Match performs on that information to provide the Platform, including AI processing, matching, audit logging and reporting.
- The sub-processors Housing Match engages to deliver the Platform.
This DPA forms part of the Terms of Use and is read together with the Privacy Policy, the Consent & Information Sharing Framework, and any subscription, Pilot or Founding Partner agreement between the Customer and Housing Match. In the event of inconsistency, the specific agreement prevails to the extent of the inconsistency; in relation to personal information, the Privacy Policy prevails over the Terms of Use.
Parties
The parties to this DPA are:
| Party | Description |
|---|---|
| Housing Match (Processor) | The operator of the Platform, which processes personal and sensitive information to provide the Platform to the Customer. |
| Customer (Controller) | The Australian provider organisation that has registered for the Platform and uploads or creates participant and property data for processing. |
Definitions
The following terms have the meanings set out below. Definitions shared across the Housing Match governance suite appear in the Master Glossary and are used consistently here.
| APP | Australian Privacy Principles, set out in Schedule 1 of the Privacy Act 1988 (Cth). |
| APP entity | An agency or organisation that holds personal information and is bound by the Privacy Act 1988 (Cth). Both Housing Match and the Customer are APP entities. |
| AI Services | The artificial intelligence features offered through Housing Match — compatibility assessment, match explanation, document extraction, executive and compliance reporting, and the in-app AI assistant. |
| Audit Log | The immutable, append-only server-side audit trail written exclusively by the recordAuditEvent backend function. Records who accessed what, when, and why. |
| Consent | The participant's voluntary, informed and specific agreement to the collection, use or disclosure of their information, recorded as an event in a permanent, append-only Consent Ledger. |
| Consent Ledger | The platform's immutable record of every consent grant, withdrawal, amendment and reconfirmation. |
| Controller | The party that decides the purpose and means of processing personal data. Under Australian law both parties are APP entities; this DPA uses 'Controller' to describe the party that determines why participant data is processed. The Customer is the Controller for participant data it uploads. |
| Customer | The Australian provider organisation that has registered for Housing Match and uploads participant or property data to the Platform for processing. |
| Data Breach | An act or event that compromises the security or integrity of personal data, or that is likely to result in serious harm to one or more individuals, as described in the Notifiable Data Breaches scheme. |
| Housing Match / We / us / our | Housing Match, the operator of the Platform available at housingmatch.com.au. |
| Participant | A person with disability who uses Housing Match to find suitable housing and supports, or whose profile is managed on their behalf by an authorised representative. |
| Personal Data / Personal Information | Information or an opinion about an identified or reasonably identifiable individual, as defined in the Privacy Act 1988 (Cth). |
| Platform | The Housing Match website and application available at housingmatch.com.au, including all features, dashboards, tools and content made available through it. |
| Processing | Any operation performed on personal data, including collection, use, storage, disclosure, matching, AI analysis, generation of reports, and deletion. |
| Processor | The party that processes personal data on behalf of a Controller. Housing Match is the Processor for participant data the Customer uploads to the Platform. |
| Provider | An organisation that uses Housing Match to manage properties, vacancies, residents, applications and related information — for example, an SDA provider, SIL provider, property agent or community housing provider. |
| Sensitive Information | A category of personal information defined in the Privacy Act that includes health information and information about a person's disability. Sensitive information is given heightened protection. |
| Security Incident | An event that may compromise the security of personal data, whether or not it meets the threshold for a Data Breach. |
| Sub-processor | A third party engaged by Housing Match to process personal data in providing the Platform, including hosting, AI and email providers. |
Roles and responsibilities
Housing Match and the Customer each hold responsibilities under the Privacy Act. Roles are allocated based on who decides why data is processed and who operates the processing:
| Data category | Controller | Processor | Notes |
|---|---|---|---|
| Participant and resident data the Customer uploads | Customer | Housing Match | The Customer decides to upload participant data and is responsible for authority and consent. Housing Match processes it to provide the Platform. |
| Property, vacancy, application and financial data the Customer creates | Customer | Housing Match | Provider operational data. Housing Match processes it on the Customer's instructions through Platform features. |
| Account and platform-operation data (login, usage, audit) | Housing Match | Housing Match | Housing Match is the APP entity for account and platform-operation data it generates. |
Both parties are APP entities
Categories of personal information
Housing Match processes the following categories of personal information, verified against the database schema:
| Category | Examples | Source entity / field |
|---|---|---|
| Account information | Name, email, phone, date of birth, gender, role, contact preferences. | User, ProviderProfile |
| Participant profile | Housing preferences, location, accessibility, household, support needs, interests, hobbies. | Participant |
| Resident profile | Resident details within a property, compatibility and support needs. | Resident |
| NDIS & funding information | NDIS plan details, funding type, support needs level, SDA eligibility and design categories. | Participant, Resident |
| Provider information | Properties, vacancies, residents, applications, financials, inspections, compliance. | Property, ProviderProfile, Application |
| Communications | Messages, applications, notes and enquiries sent within the Platform. | Message |
| Usage & audit data | Records of actions taken on the Platform (documents accessed, consent changes, AI processing). | AuditLog, PageView, AnalyticsEvent |
Categories of sensitive information
Housing Match processes the following categories of sensitive information, only where the Customer or a participant voluntarily provides it or an authorised representative provides it with authority:
- Disability type, diagnoses and support needs.
- Clinical reports — Occupational Therapy reports, Functional Capacity Assessments, Behaviour Support Plans, medical and hospital reports.
- Hospital discharge summaries and risk assessments.
- NDIS plan details and funding information.
Heightened handling
Processing activities
Housing Match performs the following processing activities on the Customer's data, each implemented and verified:
| Activity | Description |
|---|---|
| Registration & account management | Creating and managing user accounts, roles and organisation membership. |
| Profile management | Creating and managing participant, resident, provider and property records. |
| Document storage & access | Uploading clinical documents to private storage and issuing time-limited signed access links after authorisation. |
| Matching & applications | Matching participants to properties, processing applications and managing placement workflows. |
| Messaging | In-platform messaging between users about properties, applications and referrals. |
| Consent management | Recording every consent action in an immutable, append-only Consent Ledger. |
| Audit logging | Recording every sensitive action in an immutable, append-only Audit Log. |
| AI processing | Compatibility assessment, match explanation, document extraction and reporting (see Section 9). |
| Reporting | Generating executive, compliance and financial reports, including PDF exports. |
| Analytics | Internal first-party analytics and Google Analytics 4 website measurement. |
| Notifications | Transactional platform emails and optional Outlook calendar synchronisation. |
AI processing
Housing Match uses AI for the following purposes that involve the Customer's data. Most functions use de-identified data — no names, NDIS numbers, contact details or dates of birth leave Australia for these functions. Only document extraction, an optional opt-in feature, processes the original identifiable document, and only when the participant has given separate, explicit consent. Participants and their support coordinators can also enter profile information manually instead of using AI document extraction.
| AI use | Data processed | De-identified? |
|---|---|---|
| Compatibility assessment | Participant and property data to score how well a participant matches a property and its existing residents. | Yes — names, NDIS numbers, contact details and dates of birth are removed before processing; the call is blocked if a prohibited identifier remains. |
| Match explanation | De-identified participant and property data, plus already-computed compatibility scores. | Yes — the same de-identification layer is applied. |
| Document extraction | Raw clinical documents uploaded for AI-assisted profile extraction. | No — the raw, identifiable document is sent. Requires the participant's separate, explicit consent to overseas AI processing. |
| Executive & compliance reporting | Provider-level and aggregated operational data to generate narrative summaries and recommendations. | These reports are not used to transmit individual participant clinical records. |
| AI assistant | An in-app assistant that answers user questions about the Platform. | Does not process participant clinical information. |
AI is decision-support only
Consent
Consent is central to how Housing Match processes participant data. The Platform records consent as an event in a permanent, append-only Consent Ledger. The Customer is responsible for ensuring that appropriate consent or legal authority exists before uploading or sharing participant data.
- Each consent action — grant, update, reconfirm, withdraw, expire, provider access granted or revoked — creates a new permanent record.
- Consent is recorded with the actor, their role and organisation, the authority basis (self, guardian, nominee, administrator, parent of a minor, support coordinator as agent, other), the consent basis (written, verbal, guardian/substitute decision maker, digital acceptance), the legal document version, and the IP address.
- Consent can be withdrawn at any time. Withdrawal is recorded in the same ledger as the original grant, and the relevant sharing or processing stops.
- Overseas AI document extraction requires separate, explicit consent that can be withdrawn at any time.
Security controls
Housing Match protects personal data using a defence-in-depth approach. The following controls are implemented and verified:
- Secure login — every account requires email and password; every page is access-controlled.
- Role-based permissions — enforced on the server, with admin actions re-checked server-side.
- Organisation data separation — each provider can access only its own data, enforced through provider data scoping.
- Private document storage — clinical documents are never stored as permanent public links.
- Authorised document access — every document view is checked for identity, permission and consent before a time-limited signed link is issued.
- De-identification for AI compatibility processing — prohibited identifiers are removed before AI prompts are built; the call is blocked if any remain.
- Consent-gated overseas processing for AI document extraction.
- Immutable audit logging and an immutable consent ledger.
- Encryption in transit — all data between the user's browser and the Platform is encrypted using HTTPS/TLS.
- Immutable, version-locked agreement acceptance.
What we do not claim
Audit logging
Every sensitive action is recorded in an immutable, append-only Audit Log written exclusively by the recordAuditEvent backend function. No application code path updates or deletes audit rows.
- Recorded events include document access, AI processing, consent changes, profile updates, application status changes, messages, information sharing, legal agreement acceptance, permission changes, admin actions, data exports and security events.
- Each record captures the actor, their role and organisation, the action type, the target, the stated purpose, whether AI data was de-identified, the IP address, and the timestamp.
- Audit records contain no sensitive health information — only pseudonyms, timestamps, field-name references and the stated purpose.
- The Customer may request an audit extract relevant to its data through the contact details in Section 19.
Confidentiality
Housing Match treats all personal data processed under this DPA as confidential. Access is restricted to authorised personnel who require access to operate and secure the Platform, and to the sub-processors identified in Section 14. Housing Match does not sell personal data.
Sub-processors
Housing Match engages the following sub-processors to provide the Platform. Only verified, in-use providers are listed:
| Sub-processor | Purpose | What is processed | Location |
|---|---|---|---|
| Base44 (managed cloud platform) | Hosting, application, database, clinical document storage and backups. | All Platform data. | Managed cloud platform (core hosting). |
| AI providers — OpenAI, Google, Anthropic | Compatibility assessment, match explanation and document extraction. | De-identified data for compatibility and match; raw clinical documents for document extraction (consent-gated). | Overseas. |
| Google Analytics 4 | Website measurement. | Pseudonymous page views and events; IP addresses anonymised; no names or health information. | Overseas. |
| Resend | Transactional platform emails to registered users. | Email addresses and email content for transactional emails. | Overseas. |
| Google (Google sign-in) | Identity verification for users who choose Google sign-in. | Authentication data. | Overseas. |
| Microsoft Outlook (optional connector) | Calendar availability and event synchronisation for customers who connect Outlook. | Calendar events — only when the Customer enables the connector. | Overseas. |
Housing Match engages sub-processors under agreements that require them to protect personal data to a standard consistent with the APPs. Formal vendor risk assessment is on our security roadmap. Housing Match will notify the Customer of new or replacement sub-processors that materially affect the processing, giving the Customer the opportunity to raise concerns.
International processing
Some processing occurs outside Australia, consistent with APP 8 and our Privacy Policy. Not every AI function transmits identifiable information overseas — routine compatibility and match processing use de-identified data; only the optional, consent-gated document extraction feature transmits an identifiable document:
- AI compatibility assessment and match explanation — de-identified data sent to overseas AI providers.
- AI document extraction — raw clinical documents sent overseas, only with the participant's separate, explicit consent.
- Google Analytics 4 — pseudonymous usage data sent overseas, with IP addresses anonymised.
- Resend — transactional emails to registered users sent overseas.
- Google sign-in and the optional Outlook connector — authentication and calendar data sent overseas when used.
The Platform's primary application, database, clinical document storage and backups are hosted on the Base44 managed cloud platform. Where information is sent overseas, Housing Match takes reasonable steps to ensure the overseas recipient handles it in accordance with the APPs.
Data residency
Data residency is consistent with our Privacy Policy. The Platform's primary application, database, clinical document storage and backups are hosted on the Base44 managed cloud platform. Overseas processing is limited to the sub-processors and purposes identified in Sections 14 and 15. A dedicated Data Residency Statement provides further detail (planned).
Customer responsibilities
The Customer is responsible for:
- Ensuring it has a lawful basis and appropriate consent or legal authority before uploading or sharing any participant data, including sensitive information.
- Ensuring any representative acting on a participant's behalf has the legal authority to do so.
- The accuracy and completeness of the data it uploads, and updating it promptly when it changes.
- Managing consent for the participants whose data it uploads, including responding to withdrawal requests and removing data where consent is withdrawn.
- Compliance with the Privacy Act 1988 (Cth), the NDIS Act 2013 (Cth), the NDIS Code of Conduct and NDIS Practice Standards where they apply to the Customer.
- Ensuring only authorised staff are invited to the Customer's account and that each is assigned the correct role.
- Using the Platform only for its intended purposes and in accordance with the Terms of Use.
Housing Match responsibilities
Housing Match is responsible for:
- Processing the Customer's data only to provide and secure the Platform, and in accordance with the Customer's instructions through Platform features.
- Implementing and maintaining the security controls described in Section 11.
- Maintaining the Audit Log and Consent Ledger described in Sections 10 and 12.
- Engaging sub-processors under appropriate agreements and notifying the Customer of material changes.
- De-identifying data for AI compatibility and match processing, and consent-gating overseas document extraction.
- Notifying the Customer of a Data Breach affecting the Customer's data in accordance with Section 20.
- Supporting the Customer's access and correction obligations by providing audit extracts and enabling data export and deletion as described in Sections 21 and 22.
Security incident management
Housing Match maintains the Audit Log and access controls described in this DPA to detect and investigate security events. When a Security Incident is identified, Housing Match will assess, contain and investigate it, and determine whether it meets the threshold for a Data Breach under the Notifiable Data Breaches scheme.
Data breach notification
Housing Match complies with the Notifiable Data Breaches (NDB) scheme under Part IIIC of the Privacy Act 1988 (Cth). If Housing Match experiences a Data Breach that is likely to result in serious harm to one or more individuals, including the Customer's participants, Housing Match will:
- Assess the breach using the Audit Log to identify affected records and individuals.
- Contain the breach and take steps to limit its impact.
- Notify affected individuals as soon as practicable where required, with information about the breach, the steps taken, and what individuals can do.
- Notify the Office of the Australian Information Commissioner (OAIC) where required by the NDB scheme.
- Notify the Customer without undue delay where the breach affects the Customer's data, so the Customer can meet its own obligations.
Further detail is set out in our Data Breach Response Plan (planned). Formal incident response tabletop testing is on our security roadmap.
Data retention
Housing Match retains the Customer's data for as long as necessary to provide the Platform, maintain the Audit Log and Consent Ledger, resolve disputes, and comply with legal obligations. A formal data retention and destruction schedule is being developed (planned).
In the interim, the following applies:
- Active account data is retained while the Customer's account is active.
- Clinical documents are retained in private storage for the duration of the active account plus a reasonable period for audit and compliance purposes.
- Immutable Audit Log entries and Consent Ledger records are retained as a permanent legal record. They contain no sensitive health information — only pseudonyms, timestamps, field-name references and the stated purpose.
- Housing Match may retain minimal information (such as an email address) where required to comply with legal obligations or to prevent fraud.
Data deletion
When the Customer, or a participant on whose data the Customer has uploaded, requests deletion:
- Clinical documents in private storage are deleted and signed access links are revoked immediately.
- Profile information is removed or de-identified.
- Immutable Audit Log and Consent Ledger records are retained as a permanent legal record (no sensitive health information).
- Backups are managed by the Base44 hosting platform and are overwritten on the platform's backup cycle.
Termination
On termination of the Customer's account or this DPA, the Customer's right to access the Platform ceases. Housing Match will, on the Customer's request, export the Customer's data in a structured format, and then delete the Customer's data in accordance with Section 22, subject to the retention of the permanent Audit Log and Consent Ledger records and any data required to comply with legal obligations.
Contact details
For any matter arising under this DPA, including data requests, audit extracts, sub-processor concerns or breach notification, please contact:
This DPA is governed by the laws of New South Wales, Australia, consistent with the Terms of Use.
Governance register
This Data Processing Agreement forms part of the Housing Match Customer Assurance Package. The register below is the master index for the suite. It is maintained centrally and embedded in every governance document so that versions, verification status and review dates are tracked in one place.
Housing Match Customer Assurance Package — Governance Register
Master index for the Housing Match Customer Assurance Package. Maintained centrally and embedded in every governance document.
| Document | Version | Status | Last Verified | Cross-Checked With | Next Review |
|---|---|---|---|---|---|
| Privacy Policy | v1.0 | ✅ Implementation Verified | 17 July 2026 | Trust Centre, Security & Privacy Overview, source code | 17 January 2027 |
| Terms of Use | v1.0 | ✅ Implementation Verified | 17 July 2026 | Privacy Policy, Trust Centre, Security & Privacy Overview, source code | 17 January 2027 |
| Data Processing Agreement | v1.0 | ✅ Implementation Verified | 17 July 2026 | Privacy Policy, Terms of Use, Trust Centre, Security & Privacy Overview, source code | 17 January 2027 |
| AI Governance Policy | — | ⬜ Not yet drafted | — | — | — |
| Data Breach Response Plan | — | ⬜ Not yet drafted | — | — | — |
| APP Compliance Statement | — | ⬜ Not yet drafted | — | — | — |
| Data Retention & Destruction Policy | — | ⬜ Not yet drafted | — | — | — |
| Data Residency Statement | — | ⬜ Not yet drafted | — | — | — |
This register is the master index for the Customer Assurance Package. Each document is verified against implemented platform behaviour before its status is set to "Implementation Verified". Documents not yet drafted are shown as "Not yet drafted". © Housing Match 2026.
Housing Match — Data Processing Agreement v1.0
This Data Processing Agreement is a formal legal document prepared for solicitor review prior to publication. It describes only processing activities and controls that Housing Match has implemented and verified. It does not constitute legal advice. It will be reviewed by an Australian solicitor before publication. © Housing Match 2026.
