We’ve made three modifications to Section 7 of our API Terms of Service:
You agree to display the Factual ID in machine readable format on any pages where Factual Data is incorporated.
We’re keen that the Factual ID is perpetuated with the entity as functional attribution. If you have local entity pages that have Factual data, please embed the ID in a machine-readable format:
<meta name="factual" content="http://factual.com/edaea712-a3dc-4948-9f44-8814ce889e3e" />
You may not systematically query the Factual API in a manner to obtain and cache data for a given locality, region or country.
The API is intended for runtime use, so we don’t want those walking our data to take up bandwidth; if you need a download, just give us a shout.
Factual may suspend or throttle Services until we believe the number of API calls will not exceed capacity limitations. You will not take steps to circumvent any technical measures Factual may put in place to implement throttling or suspension.
Here we’re clarifying that we equitably balance calls to the API to ensure that simultaneous users have the resources they need. We’ll slow you down if your appetite exceeds the capacity of the free buffet. This does not include use of our supported (read: paid) service.
As usual with Terms of Service, we may change it at any time without advance notice. However, we’ll endeavor always to publicize any modifications on our blog and Dev Mailing List.