title: caching of Google Places API results
body: <p>I'm building a mobile app that lists posts, each post has a place attached to it.</p>
  
  <p>I want the list to be able to show distance from the user's location.
  without caching anything it would require to store the place reference for each post and while listing fetch the place's geometry from Google Places API, this sounds like a very bad idea.</p>
  
  <p>am I allowed to store the place's id, reference, name and geometry in my db and deliver it with my API?
  this is for performance purposes only</p>
  
  <p>another implementation might be to cache this data in a local sqlite db on the mobile device, but then the user will have to download the information for each uncached place so for a list of X different places the client will be doing X api calls, sounds slow and battery wasting.</p>
  
  <p>am I allowed to have a central cache in my db in a table that'll be refreshed every once in a while and evicted if not accessed for lets say 30 days ?</p>