|
Top-level
 6/ If you become a paying customer we do legally have to store a record of the transaction, but you can, with the single click of a button, delete your payment info once you stop being a customer. https://blog.opencagedata.com/post/delete-your-card-details All card billing is done via our payment processor Stripe, we never hold a record of your card details. 6 comments
8/ Next, if you use the optional "no_record" parameter in your API call, we will keep ... absolutely no record of what your query was. None. Nada. Zilch. 9/ Finally, we do our best to educate users of the API about privacy implications of location data. For example here is a guide to NOT showing precisely geocoded locations https://opencagedata.com/guides/how-to-preserve-privacy-by-showing-only-an-imprecise-location 11/ Thanks for reading and sharing Please get in touch if you have any questions (or suggestions) about our approach to privacy or security (or anything else). We have more threads about #geoeducation, the #geoweirdness of specific countries, border disputes, geocoding, etc linked on our blog: https://blog.opencagedata.com/geothreads Stay safe and private! π΅οΈ Final bonus toot - what to do if you want the benefits of tracking where youβve been without the privacy risk? π΅οΈπΊοΈ Please check out our friends at @owntracks https://owntracks.org an open source, privacy-focused journey tracking and sharing software |
Gregory's Server
7/ So now let's get into the geocoding API itself.
First up, please send us only location information, never details of who is at that location. Besides privacy concerns it just makes geocoding much harder.
Please see: https://opencagedata.com/guides/how-to-format-your-geocoding-query
#geoeducation