What we shipped this month: geocoding, IP, time zone and more
A roundup of recent work across the API: new compatibility hosts, faster time zone and elevation lookups, dashboard features, and clearer quota visibility.
A data processing agreement now available on request
Some organizations cannot simply agree to a general privacy policy and move on. Internal compliance requirements, industry regulation, or a customer's own vendor requirements sometimes call for a specific, signed agreement covering exactly how a vendor handles personal data. A data processing agreement covering My Geocode is now available on request for exactly that situation.
The agreement sits alongside our general privacy policy rather than replacing it, addressing the same underlying data handling in the more formal, specific terms that a compliance process often requires. It covers how account data, usage data, and IP address information, which is central to how quota is calculated per network, are processed as part of running the API.
Requesting one is straightforward: contact our team through /contact/ and ask for a data processing agreement for your account. This is handled directly by a person on our team rather than through an automated form, since the details of a given organization's requirements sometimes call for a conversation rather than a generic document.
This is particularly relevant for organizations processing personal data on behalf of their own customers, where a chain of data processing agreements down through every vendor involved is often a genuine legal requirement rather than a nice-to-have. If My Geocode's IP geolocation, geocoding, or other endpoints touch personal data as part of a larger system you operate, having this agreement in place closes that link in the chain properly.
We built this to be available to any account that needs it, rather than reserved for a particular size of customer or a particular pricing tier. Whether an account is running on the free tier, prepaid credit, or an Unlimited package, the same agreement is available on the same terms, since the underlying data handling it describes does not change based on how much an account happens to be paying.
None of this changes anything about how the API itself works, what data flows through a normal request, or what is documented in our general privacy policy. It is an additional, more formal document for organizations that specifically need one, sitting alongside the terms of service and privacy policy that already apply to every account by default. If your organization's compliance process requires this kind of agreement before deployment, reach out through /contact/ and we can get it arranged.