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 OpenSEO launches.
This draft outlines how we expect the hosted version of OpenSEO 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, such as saved keyword lists, tracked keywords and the results of actions you run.
- If you connect Google Search Console or Google Analytics: which Google account and property, its email address, and read-only access tokens, stored encrypted. Reports are fetched from Google when you open them and are not stored, with one exception: a site audit of a project with Search Console connected stores each audited page's clicks for the last two 28-day periods, to flag pages that get search traffic but redirect, fail or are noindex. They are deleted with the audit.
YepAPI
All SEO 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. OpenSEO does not process payments.
Self-hosting
If you self-host OpenSEO, 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.