Legal
Privacy
Draft, not yet reviewed
This page is a placeholder written in plain language. It has not had legal review and is not the final text. It will be reviewed and replaced before OpenReach launches.
This draft outlines how we expect the hosted version of OpenReach to handle data. Details may change before launch.
What the hosted version stores
- The account details you give us when you sign up.
- Your YepAPI key, stored encrypted, so the app can make calls on your behalf.
- The work you create in the app: projects, saved creators and leads with your notes and statuses, lead searches, monitors and the mentions they find.
- That work includes information people and businesses published themselves: creators' public profiles and bios, and businesses' Google Maps listings. OpenReach stores only what you choose to save or monitor.
YepAPI
Creator, Google Maps and search data comes from YepAPI. When you run an action, the request is sent to YepAPI using your key. Your billing relationship is with YepAPI, and their handling of your account and payment data is covered by their own policies at yepapi.com. OpenReach does not process payments.
Community APIs
Some searches go to the free official APIs of Hacker News (Algolia), GitHub and Stack Exchange, and, on installs that configure it, Reddit. Only the search words are sent; no account data.
Self-hosting
If you self-host OpenReach, the database and everything in it run on infrastructure you control. We do not receive that data.
Still to be written
The final policy will cover retention, deletion, cookies, sub-processors, your rights and how to contact us. Those sections are not written yet.