As someone who used to work at an ad tech company, I can tell you that we're very much not an ad tech company. In fact, we set out to build the opposite. More here: https://radar.com/blog/our-commitment-to-privacy
Short, easy-to-spell name that suggests location. It's worked out pretty well for us, and we got the dot com!
I believe the point is that Op doesn't _want_ to chat. I believe the originally point is you should be up front and _clear_ with your pricing rather than trying to force a conversation.
Yep, I get it. Working on a self-serve pricing calculator. Reality is that enterprise convos do make sense at sufficient scale. If it does here, our inbox is open!
Often, if a company has "Contact Sales" on their pricing page it's because they only want customers who have a budget big enough to warrant contacting sales.
At an early stage, it's often easier and more lucrative to build for and support a few large customers than many small ones.
> Licensee shall not … store any address or point of interest data from Radar's geocoding, autocomplete, or place search APIs for more than thirty (30) days;
So if an e-commerce site user starts typing their address, it’s autocompleted via Radar, and the user confirms it, then the site must delete the user’s address after 30 days?
I used to work for a company that made an app for drafting evacuation signs, and we had a usecase for using a map as an underlay to show the surrounding buildings/terrain for the siteplan. I recall that quite a few map providers had a TOS that prevented that usecase (as the evac signs would be saved to pdf for distribution or printed), so I'm interested what the take is here.
