Security and data quality

Account and API access

Addrex uses its existing provider for account authentication. Authenticated API requests use credentials managed through the console. Keep API keys on your server, revoke keys you no longer need, and use the documented HTTPS endpoints.

The public first-address experience uses a server-side session. It does not require you to provide or expose an API key in your browser.

Data handling

Address inputs are processed to produce results. Account workflows may store uploads, job results, usage records and feedback. Read the privacy policy for the information collected and contact options for data requests.

Do not assume real-time queries have zero retention or that all stored records share one deletion schedule. Ask us about your requirements before sending sensitive data or relying on a specific retention period.

Evidence, coverage and certification

Postal ranges, delivery-point evidence, canonical physical locations and nearby event reports are distinct forms of evidence. Availability depends on the source and location. Missing data is shown as unavailable; it does not establish that a feature or hazard is absent.

Addrex does not claim USPS CASS certification. This page does not represent a SOC 2 certification, encryption-at-rest attestation, or audited service-level commitment.

Report a concern

For a security or account-access concern, use the contact page. Describe the affected route and expected behavior without including passwords, API keys, private addresses, or another person's data.