|
Top-level
 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 3 comments
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
10/ Digital privacy is a continually evolving issue. New technology makes so much possible, but also exposes us to new risks. It's a topic that is never "done".
We welcome (and pay for) suggestions as to how we can improve security. Here's our bug bounty program, at the bottom you can find a list of bug reports we've paid for:
https://opencagedata.com/security-bounty
Here's a report we wrote about our experiences running a bug bounty program as a smaller company:
https://blog.opencagedata.com/post/running-a-security-bounty-program-as-a-bootstrapped-business-lessons-learned
#geoeducation
10/ Digital privacy is a continually evolving issue. New technology makes so much possible, but also exposes us to new risks. It's a topic that is never "done".
We welcome (and pay for) suggestions as to how we can improve security. Here's our bug bounty program, at the bottom you can find a list of bug reports we've paid for:
https://opencagedata.com/security-bounty