Methodology

Data Sources & Cross-Referencing

Public telecommunications allocation records, community submissions, and internal consistency checks.

Last Updated:
← Methodology Overview

Data Source Overview

Reverseau draws from two data sources, each serving a different purpose. Neither source independently constitutes a complete picture - they are combined to provide contextual telecommunications intelligence.

Source 1: Community-Submitted Reports

The primary and most substantial data source is community-submitted reports. These represent first-hand accounts from individuals who have received phone calls or SMS messages.

Key characteristics of community report data:

  • Submitted anonymously - no registration or personal identification required
  • Structured fields include phone number, caller type classification, contact channel, and written description
  • Reports are moderated through automated and human review processes
  • Data volume has accumulated since 2014, covering hundreds of thousands of community submissions across Australian phone numbers

Community reports reflect self-selected participation and do not represent a statistically random sample of all call recipients.

The pipeline for processing community reports is documented in Community Reporting & Processing Model.

Source 2: Public Telecommunications Allocation Records

Phone number allocation and service type information is sourced from publicly available records maintained by the Australian Communications and Media Authority (ACMA). This data provides:

  • Carrier allocation - which telecommunications carrier has been assigned a number range
  • Service type - whether a number range is classified as landline, mobile, VoIP, or special service
  • Geographic region - the area code and associated state or territory for landline numbers
  • Allocation status - whether a number range is allocated, quarantined, or available

This public data supplements community reports with structural telecommunications context. Allocation records reflect number range assignments, not subscriber-level usage. They do not confirm caller identity or current ownership - see Number Classification System for the allocation vs. ownership distinction.

Cross-Referencing Approach

Reverseau combines these two data sources to produce the information displayed on phone number pages. Cross-referencing matters because it lets the platform distinguish between structurally valid reports and potential noise - a report against a number that doesn't match any known allocation range, for example, can be flagged before it reaches the dataset.

The cross-referencing process includes:

Example: How cross-referencing works in practice When a community report is submitted for a number like 02 9XXX XXXX, the system cross-references ACMA allocation records to confirm the number falls within a valid Sydney landline range and identify the assigned carrier. That carrier and service type data then appears on the phone number page alongside the community report - giving visitors both the community's experience and the structural context in one view.

Cross-referencing enhances structural accuracy but does not verify the substance of reported experiences.

What Reverseau Does Not Source The following data types are not sourced or available through this platform:
  • Caller identity, personal information, or subscriber account data
  • Business registration or ABN records
  • Direct carrier feeds or real-time porting data
  • Law enforcement or regulatory investigation data
  • Call records, metadata, or interception data
Reverseau does not perform identity resolution, subscriber tracing, or investigative profiling of phone number users. For more on data handling safeguards, see Transparency & Data Integrity.

Metadata Refresh Frequency

Community reports are processed and published in near-real-time, subject to the moderation pipeline. Public allocation data is refreshed approximately quarterly, aligned with ACMA's publication schedule - though the exact timing depends on when ACMA releases updated records. This refresh cycle means that recently ported or reallocated numbers may temporarily display outdated carrier information. Reverseau does not receive real-time carrier routing updates.

Community Reporting & Processing Model

Submission and processing pipeline - from anonymous report to published data point.

Read documentation →

Number Classification System

Numbering structure, ACMA allocations, and why allocation does not equal ownership.

Read documentation →

Transparency & Data Integrity

Moderation workflow, correction requests, and the safeguards that keep the dataset honest.

Read documentation →