Last updated October 10, 2026
PruneSEO holds the URLs we crawl, the Search Console access you grant us, and your account details. It holds nothing about you that is not needed to do that, and it gives you working controls over all of it.
Three categories, and the third is much larger than people expect.
The three categories of data
| Category | What it contains | Why |
|---|---|---|
| Your account | Name, email address, a hashed password, your avatar, and your role and organization memberships. | So we can identify you, let you in, and decide what you may see. We never ask for a company name you have not chosen to give us. |
| Your site data | The properties you add, and for each one: every URL our crawler discovered, the pages it fetched, their status codes, response headers, page titles, extracted word counts and content signals, the patterns they were grouped into, and the verdicts reached. | This is the product. Without it there is no audit — and it is large: a site with hundreds of thousands of URLs produces a correspondingly large record. |
| Search Console access | An OAuth grant scoped to read-only access to the properties you connect, plus the coverage data returned for the URLs we check. | So we can verify a sample of each pattern against what Google actually did. We do not ask for permission to change anything in your Search Console, and the grant is not scoped to allow it. |
We also record operational events: sign-ins, devices, failed and successful authentications, changes made in the product, and scheduled jobs. This exists so you can see what happened to your own account and so misuse is investigable afterwards.
We also do not train models on your data, and we do not use your crawled URLs or your Search Console results for any purpose other than producing your own audit.
When you add a site, our crawler fetches its URLs from your web server. That is the only part of the product that touches your infrastructure, and it is what makes an audit possible.
A small number of providers stand between your data and us. Each one is named here so you can hold us to it.
Sub-processors
| Provider | Role | What they receive |
|---|---|---|
| Search Console | OAuth tokens scoped to the properties you connect, and the coverage responses returned for sampled URLs. | |
| Cloudflare R2, Amazon S3, Backblaze B2, or MinIO | File storage | Artifacts and uploaded files you create. Whichever is configured for the deployment. |
| Resend | Transactional email | Your email address and the content of messages the product sends you — password resets, invitations, security notices. |
| Your hosting and database provider | Infrastructure | Everything, as the deployment requires. |
| Your identity provider | SSO, if you use it | Your identity claims, to the extent your provider sends them. |
We do not sell or share data with anyone else. A processor added later will be listed here before it starts receiving your data.
The sensitive parts of this system were designed with their failure modes in mind, and the controls are implemented rather than promised:
We do not keep your data because it might be useful later. If you delete something, the intent is to delete it.
These are implemented as product features, not as a process you have to request and wait for.
Rights, and how each is exercised
| Right | How to use it |
|---|---|
| Access — get a copy of your data | Export it from your account. An administrator can export any user’s data. |
| Erasure — be forgotten | Request deletion. Your identifying details are anonymised and hard-deleted; the record of the account remains, without you in it. |
| Rectification — correct it | Edit your profile and organization details directly. |
| Portability — take it elsewhere | The export is machine-readable. |
| Object and restrict | Through the contact page, as described below. |
| Withdraw consent | Disconnect a Search Console property at any time, which revokes that access immediately. |
There is also a standing record of personal-data processing — what categories exist, why, and who has accessed them — maintained by the product and visible to administrators.
If a breach affects your data we will tell you and the relevant regulator without undue delay, and we will say what we know, what we have done, and what remains unknown. We will not write to you only once the picture is complete, because by then the news is out anyway and you deserved the warning first.
Privacy questions, access requests and complaints go through our contact page. You do not need to explain which right you are invoking or cite a regulation — say what you want and we will work out the rest.
If you are in the EEA or the UK and we do not resolve it, you may complain to your local data protection authority. We would rather you came to us first, but that choice is yours and it is not a precondition.
This policy is about PruneSEO. It does not cover the websites we crawl — those belong to whoever runs them, and their policies still apply to you as their visitor.