Summary

  • The ACCC’s proposed rule would link service-level and plan-level records through a plan ID, enabling comparisons of actual charges, usage and geography without independently proving causation or network quality.
  • A stable pseudonymous customer key could support analysis across reporting periods, but privacy safeguards and linkage risks remain unresolved. The consultation closed on 7 October 2026; the rule has not been adopted.

The Australian Competition and Consumer Commission’s proposed 2026 Retail Telecommunications Record-Keeping Rule would change the level at which retail telecommunications evidence can be examined. Instead of relying only on plan descriptions or aggregate reporting, the ACCC could link information about a particular service with information about the plan associated with it. The draft separates service records from plan records and uses a plan ID to connect them.

Proposed coverage includes retail broadband, fixed voice and mobile services, together with active broadband and mobile plans, for specified providers around a 50,000-service threshold and selected smaller-market exceptions. The proposal remains unadopted following the consultation’s close on 7 October 2026; its fields and coverage should therefore be understood as proposed requirements, not settled obligations.

The service record would capture SA1 geography, brand, service start date, access carrier and technology, previous provider where known, actual billed charges, discounts, add-ons and usage. The associated plan record would describe characteristics including speed, usage charges, contract terms and availability or legacy-plan information. Joining these records would allow the ACCC to examine plan terms alongside the charges and usage associated with services, rather than treating a plan’s advertised characteristics as a complete account of the customer’s commercial experience.

Geography and access information could provide additional context for comparisons across services. The resulting evidence could help identify patterns that aggregate totals conceal, but it would not, by itself, establish why a charge or usage pattern occurred, demonstrate service quality, or prove that an observed pattern applies across the entire market.

The proposal also introduces a stable scrambled customer identifier intended to persist across reporting periods. The ACCC says this key should not identify a customer, should not be derivable to the customer’s actual identity, and should not be disclosed beyond providers and the ACCC. The consultation points to secret-key hashing as a possible approach. A consistent key could allow records from different periods to be associated with the same pseudonymous customer, making longitudinal analysis possible without including direct identity information in the analytical records.

That persistence is analytically significant: it allows changes to be examined over time rather than treating every reporting period as an unrelated snapshot. It also makes the management of the identifier and the linked records consequential, because the analytical value depends on maintaining continuity while respecting the stated restrictions.

The ACCC says it did not conduct a full privacy impact assessment because the proposed records lack personally identifiable information. That explanation describes the regulator’s stated reasoning; it does not settle every question about the risks of linking records across time. The distinction between excluding direct identifiers and preventing identification through other means remains important when assessing a stable key, access controls and disclosure boundaries.

The proposed limits on who may receive the key and whether it can be derived to an actual identity are central safeguards to examine, not evidence that every implementation risk has already been resolved. The records could provide the ACCC with a more connected account of plans, services, locations, usage and actual charges, but the strength and legitimacy of that evidence would depend on the final rule’s design and the practical protection of the linked data.

Sources