Core postal lookup does not require an account. This policy explains the limited information processed when you search, submit a form, request API access or choose optional analytics and advertising.
Information processed
Public searches may create a short-lived sanitized query log with a hashed network signal and general user-agent class. Correction, contact and API-access forms collect the information you enter. API use records a key identifier, date, counters and last-use time. We do not sell personal information.
Purposes
We use information to operate and secure the service, respond to requests, prevent abuse, understand aggregate performance and meet legal obligations. Full search text is not sent to analytics. Core lookup remains usable without marketing consent.
Vendors and sources
Postal data is sourced from GeoNames under CC BY 4.0. Optional Google analytics, consent and advertising products remain disabled until configured and are loaded only according to the site’s consent controls and applicable regional requirements. Maps are loaded from OpenStreetMap only after an explicit user action.
Retention and rights
Operational logs are rotated and size-limited. Form submissions and API records are retained only as long as needed for the stated purpose, disputes, security and legal obligations. Contact hello@zipcodeglobe.com to request access, correction or deletion where applicable.
Security
We use HTTPS, access controls, password hashing, CSRF protection, rate limits, restricted storage paths and audit logging. No online service can promise absolute security.
Cookies and local storage
Essential session cookies support security functions such as administrator authentication, CSRF protection and controlled form submissions. The public lookup itself does not require an account. Optional consent choices may be stored locally so the site can remember whether analytics or advertising scripts may load. Rejecting optional processing must not prevent access to core search, country directories, postal results or non-commercial tools.
Security and abuse prevention
Rate limiting may use a keyed hash of a network address together with a coarse user-agent category. The purpose is to reduce automated abuse without publishing or deliberately retaining a plain network identifier in application logs. Administrative sessions use secure cookie attributes when HTTPS is active, password hashing, lockout controls and audit records. No internet service can promise absolute security, so users should avoid submitting sensitive information that the requested task does not require.
International access and third parties
Visitors may access ZipCodeGlobe from many countries, while the operator is based in India and infrastructure or optional vendors may process information in other jurisdictions. When optional Google products, a certified consent platform, payment provider or map service is enabled, their own terms and privacy practices also apply. The administration panel keeps those integrations disabled until identifiers, disclosures and consent requirements are configured. Postal records themselves describe public geographic assignments and are not treated as private customer address books.
Choices, correction and deletion requests
You may ask about personal information submitted through a contact, correction or API-access form, request correction of inaccurate contact information, or request deletion where retention is not legally or operationally required. Provide enough information to locate the submission without sending additional sensitive data. Consent for optional analytics or advertising can be changed through the consent controls when those services are enabled. Privacy requests can be sent through the contact page or to hello@zipcodeglobe.com.
Policy changes
This policy may be updated when features, vendors, legal requirements or retention practices change. The page displays its publication or update date. Material changes should be reflected before a newly enabled integration begins processing visitor data, not retroactively after deployment.