Home › Guides › Can we list a defaulting tenant on a tenancy database?
Can we list a defaulting tenant on a tenancy database?
Much less often than the industry assumes. Listing is available only after the tenancy has ended, only against a named former tenant, and only on narrow grounds. Falling behind in rent is never, by itself, enough. You must give the tenant advance written notice and a real chance to object, and consider what they say. Where family or domestic violence is anywhere in the picture, do not list and get advice.
General information, not legal advice. Tenancy-database rules are state and territory law and they differ. Your obligations depend on your circumstances and your jurisdiction.
The tenancy-law rules on this page bind you whether or not the Privacy Act does, and a tenancy-database operator is bound by the APPs regardless of its turnover.
Not sure it's you?
Does this apply to you?
Tap what's true for your agency. Nothing is saved.
Orientation only, not a compliance assessment. General information and tools, not legal advice.
What has to be true before you can list anyone?
Every Australian state and territory regulates this, under broadly aligned provisions that nonetheless differ in detail. The common floor:
The tenancy must have ended. You cannot list a current tenant. Listing while a dispute is still running is the most frequent unlawful listing.
A named former tenant only, who was a party to the agreement. You cannot list an occupant who was never on the lease.
A permitted ground. Typically a breach leaving a debt greater than the bond, or a tribunal or court termination order relating to the tenant's conduct. Being served a termination notice, or not looking after the property, is not on its own a ground.
Advance written notice to the tenant and a real chance to object, commonly at least 14 days, with the objection genuinely considered rather than filed.
The listing must be accurate, complete and clear, and it must relate only to that tenant's own conduct.
Arrears alone is never enough. That is the single most common misconception, and it is the one that produces listings a tribunal will order removed.
What if the tenant left because of family or domestic violence?
Do not list, and get advice. The absence of a statutory ban is not permission.
An express statutory prohibition exists in only two jurisdictions, and one of them is narrow:
Victoria prohibits listing where the breach resulted from family or personal violence the renter experienced. This is the broad version.
New South Wales protects a tenant only where the tenancy was terminated under the domestic violence provisions and that person gave the domestic violence termination notice. Someone who left because of violence without using that route is not covered by the prohibition.
Everywhere else it is a discretion, not a ban. In Queensland and South Australia the tribunal may order that a person not be listed, and family violence is an example of an "unjust" listing. In Western Australia family violence makes a listing "unjust", which is a ground for a court order rather than a prohibition. No family-violence database provision was found in Tasmania at all.
So the honest position is that in most of Australia nothing stops you listing. That is a reason for more care, not less. Someone who leaves a violent household commonly leaves a broken lease, rent owing and damage behind them, and a listing then blocks them from renting anywhere for years. A tribunal can order removal after the fact, and the reputational exposure of having made the listing does not go away when it does.
If family violence appears anywhere in the tenancy history, stop before lodging anything and get advice.
One duty that is not discretionary: in Victoria, where you hold information relating to family violence that is on a database, the residential rental provider must tell the operator within 7 days that it must be removed.
Sources: Residential Tenancies Act 2010 (NSW) ss 211 to 218, including s 213A (further restriction on listing, domestic violence) ✅ verified against the current version for 10 June 2026 · Residential Tenancies Act 1995 (SA) ss 89A(4)(d) and 99F ✅ verified against authorised version 15.1.2026 (`verify/2026-07-30-nsw-sa-tenancy-pins.md`) · and the residential tenancies legislation of your own state or territory, which sets its own listing conditions and notice periods.
⚠️ We cite section numbers only for the two jurisdictions we have read at source. Victoria, Queensland, Western Australia, Tasmania, the ACT and the Northern Territory all regulate database listings, and the body of this page describes the pattern they share, but we have not yet verified their section numbers against the current Acts, so we do not print them. A citation nobody has checked is worse than none.
How long can a listing stay, and what happens if it is wrong?
Listings do not last forever, but note whose duty that is: the three-year limit falls on the database operator, not on you. Do not assume a listing you made drops off because you left it alone, and do not tell a tenant you will remove it on that basis. Your own hook is the duty below, which is triggered by a listing being wrong or out of date.
If the tenant later says the listing is wrong, a much shorter clock applies than anything in the Privacy Act: in most states the listing agent must notify the database operator within about 7 days of becoming aware, and the operator must act within about 14 days. Work to the state clock, not to the APP 13 benchmark.
Sources: the relevant state or territory Residential Tenancies Act; Privacy Act 1988 (Cth), APP 13 (Schedule 1) · See also a disputed tenancy-database listing
What does the Privacy Act add on top?
The disclosure to the database operator is a use or disclosure of personal information, so APP 6 applies. And APP 10.2 requires such steps as are reasonable to ensure information you disclose is accurate, up to date, complete and relevant, having regard to the purpose of the disclosure. Reconcile the ledger before you lodge anything: a listing built on an unreconciled figure fails that test and is long-lived.
The database operator is bound by the APPs for its database activities regardless of its turnover, because operating a residential tenancy database is itself a trigger under s 6E(2). Note the limit of that: merely listing a tenant on, or searching, someone else’s database does not make your business covered. Whether the Privacy Act binds you is the separate turnover-and-triggers question in the box above.
And "residential tenancy database" is narrower than it sounds. The Regulations define it as a database that does both of two things: it stores personal information about an individual's occupation of residential premises as a tenant, and it can be accessed by someone other than the operator or a person acting for the operator. Both limbs have to be met. So an internal list kept inside your own agency, that nobody outside it can reach, is not a residential tenancy database on that definition, and keeping one does not make you an operator.
⚠️ That is a narrow point and it is not permission. If the Act binds you for some other reason, the APPs apply to whatever is on that list, and the accuracy and fairness duties bite in the ordinary way. Tenancy law may also have something to say about how you use it. The only thing limb (b) settles is that an internal list does not, by itself, turn you into a database operator.
Sources: Privacy Act 1988 (Cth), APP 6 and APP 10.2 (Schedule 1), and s 6E(2) with the Privacy Regulations 2025 (Cth) ss 5 and 7(1)-(2) (commenced 1 April 2026), which prescribe a small business operator that operates a residential tenancy database, confine that coverage to the prescribed database acts and practices, and define the database itself in the two-limb terms above ✅ (`CLAIMS-LEDGER.json`, VERIFIED)
✅ The Regulations were read at source on 2026-08-02, so the pinpoints above are pinned rather than inferred: the authorised PDF of `F2025L01377` (17pp, every page footed "Authorised Version F2025L01377 registered 14/11/2025"), extracted text at `research/source-text-privacy-regulations-2025-F2025L01377.txt`. ⚠️ It is drafted with sections, not regs, which is why the citation reads `s 7` and not `reg 7`. ⚠️ The instrument is the 2025 Regulations, not the superseded Privacy Regulation 2013 still named in `verify/2026-07-27-round3-batch34-statutory.md`. · OAIC APP Guidelines chapters 6 and 10 · OAIC APP guidelines
→ The free 2-minute audit covers the disclosure points most likely to cause real harm, including database listings.