Keep your geocoding results
A cloud geocoder rents you its answers. The terms say how long you may keep them, and the price list says what keeping them costs. An offline geocoder answers from a file on your disk, so the result is yours.
What the cloud terms say
| Service | Keeping the coordinates | Price |
|---|---|---|
| Google Geocoding API, Service Specific Terms, last modified October 28, 2026 | §6.3.1: latitude and longitude may be cached “for up to 30 consecutive calendar days”, then deleted; §6.2: not with a non-Google map | per request |
| Mapbox Geocoding | temporary results may not be cached; permanent results (permanent=true) may be stored, for your own use, not for distribution | temporary: 100,000 a month free, then $0.75 per 1,000; permanent: $5.00 per 1,000 from the first request |
| Esri ArcGIS Location Platform | stored results need forStorage=true | not stored: 20,000 free, then $0.50 per 1,000; stored: $4 per 1,000, none free |
Read in full text on November 8, 2026. Terms and prices change; the links go to the pages themselves.
What changes with a file on your disk
GridPin answers from a sheet, one file per country built from open address data (Overture Maps, OpenAddresses and the national sources named on each country page; some countries add a separate POI layer). There is no request to keep or delete, no map you must show the points on, and no price per stored point: write the coordinates into your database and keep them as long as your own records last. The data licence of each sheet is in its attribution file and in gridpin stats.
Geocode once, keep the table
gridpin batch usa.bin customers.csv customers_geocoded.csv gridpin batch usa.bin customers.csv customers_geocoded.csv --with provenance
--with provenance adds the sheet's release, data date, licence and SHA-256 to every row, so a stored point says where it came from years later.