I am developing a dating app and will be adding a venue search function soon. I hope Iggy can provide the data for this with reasonable terms. Specifically, I

I am developing a dating app and will be adding a venue search function soon. I hope Iggy can provide the data for this with reasonable terms. Specifically, I want to pre-process the data, store it in a database, and use the app's backend to do search. Google Maps API [1], TomTom API [2], HERE API [3], Mapbox Geocoding API [4], Azure Maps [5], Yelp [6] and other mature geocoding APIs have licenses with extreme restrictions. They forbid storing any of their data. Apps are limited to the search APIs provided directly by the vendor's API. And since caching is forbidden, they carry the risk of unintentionally running up a huge bill. The vendor can suddenly raise the price (as Google Maps API already did once) and applications cannot use caching to reduce costs since that is forbidden by the terms. They require brand attribution. They forbid combining their data with data from other sources, like the app's users. They forbid showing their data on other maps. These limitations make the APIs mostly useless for innovative new applications. A few new API companies have few data restrictions. Radar [7] allows caching data for 30 days. Geoapify [8] allows saving data. What is Iggy's policy on saving and caching data returned from the API? I skimmed Iggy's Terms of Service [9] and found nothing about this. How fresh is Iggy's data for Points-of-Interest hours of operation? I'm mostly interested in osm_coffee_shops, osm_restaurants, and osm_bars. [1] https://cloud.google.com/maps-platform/terms https://cloud.google.com/maps-platform/terms [2] https://developer.tomtom.com/terms-and-conditions https://developer.tomtom.com/terms-and-conditions [3] https://developer.here.com/terms-and-conditions#restrictions-on-here-materials https://developer.here.com/terms-and-conditions#restrictions... [4] https://docs.mapbox.com/api/search/geocoding/ https://docs.mapbox.com/api/search/geocoding/ [5] https://docs.microsoft.com/en-us/answers/questions/214472/azure-maps-cahcing-policy.html https://docs.microsoft.com/en-us/answers/questions/214472/az... [6] https://www.yelp.com/developers/api_terms https://www.yelp.com/developers/api_terms [7] https://radar.io/terms https://radar.io/terms [8] https://www.geoapify.com/term-and-conditions https://www.geoapify.com/term-and-conditions [9] https://www.askiggy.com/terms https://www.askiggy.com/terms