Your developer account.
Clear data handling.

Information used by the service

Registration requires an email address, password and an Australian mobile number for verification. The service also records verification state, API key metadata, credit ledger entries and usage information needed to secure accounts and enforce limits.

Passwords and API keys

Passwords are stored as hashes. API key secrets are shown once when created and stored as hashes for authentication. You can revoke keys in your account. Keep the original secret private; the service cannot show it again.

SMS verification

The configured SMS verification provider receives the phone number and verification request needed to send and validate a code. Verification attempts, resend times and request origin information may be recorded to limit abuse. A verification message is not consent to promotional messages.

Usage and security records

Request records support credit accounting, rate limiting, troubleshooting and investigation of misuse. The API key itself should not be placed in a URL. Avoid submitting personal information in search strings. Server and network providers may process technical request information when delivering the service.

Cookies and documentation examples

The account area uses a session cookie for sign-in and security. The documentation playground keeps a key in the current page’s memory and uses it only for requests you explicitly submit. It does not save the key to browser local storage.

Source listing data

The public API is separate from account records and exposes only the documented public fields. Agent email addresses, phone numbers, descriptions and internal search bands are withheld. Review the field policy.

Recovering access

Use account recovery with your email and previously verified Australian mobile. Eligible recovery messages are queued for SMS delivery. A successful reset requires the delivered code and a new password, then revokes existing sessions and API keys.

Closing your account

You can close your account while signed in. Closure requires your current password and explicit confirmation. It revokes API access and removes or pseudonymises your email, raw phone, password hash and verification-provider references.

Records retained after closure

A keyed phone identity hash remains to prevent repeated free-credit registration. This is distinct from storing your raw phone number. Completed request-accounting records are scheduled for pruning after 180 days; verification challenges after 30 days; recovery records are pruned after expiry; short-lived abuse controls expire on their own schedules. Provider and network records follow their own service policies. Closure does not delete agency-sourced property observations from the upstream dataset.

Published 7 November 2026. This page describes the implemented service; provider configuration and operational retention settings may be updated as the product develops.