Breach Watch
Latitude — Data breach disclosed September 2026
Information about members was involved in a data breach at Latitude, disclosed on 25 September 2026.
People affected: 225,000, stated by the source.
The sources for this record do not confirm what information was involved and when the incident happened.
- Update to a previously disclosed incident
- Officially confirmed
- Disclosure date: 25 September 2026
What matters
- Who was affected
- Members
- People affected
- 225,000, stated by the source
- Information involved
- Not stated
- Authorities notified
- OAIC and Australian Cyber Security Centre
Key dates
- Incident date
- Not confirmed
- Discovery date
- Not confirmed
- Disclosure date
- 25 September 2026
- Notification date
- Not confirmed
Each date is either established by a quoted source or explicitly not confirmed.
Affected people and data
Categories of affected data
Not stated
Notifications and response
Regulators notified
- OAIC
Government cyber security agencies notified
- Australian Cyber Security Centre
What the organisation says it did
- commenced an investigation
Not stated: Police notified · Remediation stated
Sources
Each source is labelled by what it is: the organisation's own statement, a regulator's publication, or a news report. Follow the link to read the original.
Regulatory update
OAIC’s action in relation to the 2023 Latitude Data Breach and information to update and assist individuals | OAIC
Further sources
For people who may be affected
If you may be affected
This record does not yet cite a notice from Latitude with instructions for affected people. If you have been told you are affected, follow the instructions in that notice, and reach the organisation through contact details on its own website.
Practical steps
- The sources for this record do not confirm what information was involved. If Latitude tells you that you are affected, its notice should say what was included and what it recommends.
- Treat unexpected calls, texts and emails that mention this incident with caution. Contact the organisation using details you find yourself, not details in the message.
- Keep a note of any notice you receive and anything you do in response. It helps if you need to make a complaint or claim later.
Official help
- Office of the Australian Information CommissionerRespond to a data breach notification Steps for contact, financial and identity information, from the privacy regulator.
- Office of the Australian Information CommissionerData breach support and resources Support services, including mental health support.
Cleverer is not connected with Latitude and cannot tell you whether your information was involved. Only the organisation can confirm that.
For Australian businesses
What would your business need to prove after an incident like this?
The sources for this record do not confirm how the incident happened, so these are the questions any data breach raises. This is not a finding about the organisation in this record. It is what another business would want on file if it had to explain itself after a breach.
An incident response plan, and a record of testing it
Showing who decides what, and how fast, before the pressure starts.
Notification decision records
Showing how you assessed whether a breach was notifiable, and when you decided.
Access reviews
Showing that you regularly confirm who can reach personal information, and remove what they no longer need.
A current supplier register
Showing which suppliers hold or can reach your customers' data.
Staff training records
Showing which staff completed privacy and security training, and when.
Board or management oversight records
Showing that cyber and privacy risk was reported to, and considered by, the people accountable for it.
Could your business prove what it had in place?
A policy shows what you intended. Evidence shows what happened. Check your current cyber compliance position and see which evidence is missing.
Cleverer helps businesses keep this work current and retain dated evidence of what was actually done. It does not prevent breaches, and nothing on this page is a finding about how this incident happened or what the organisation in this record did.