Privacy policy
For adam.finzel.co.uk and my OpenSEO dashboard at seo.finzel.co.uk. Last updated 15 November 2026.
I'm Adam Finzel, and both of these are mine. I run them myself, as a private individual in the UK, and I'm the one responsible for the data they handle. There's no company behind them.
If you have a question, or want me to show you or delete something I hold about you, send me a message with the contact form.
Contents: this blog • the contact form • OpenSEO and your Google data • your rights
This blog, adam.finzel.co.uk
Analytics
The blog uses Google Analytics to count visits and see which posts people read. It sets cookies in your browser and sends Google your browser details, the pages you view, roughly where you are (from your IP address) and how you got here. I use it only to see how the blog is read. Google's own handling of it is in how Google uses information from sites that use its services. You can block it with your browser's settings or the Google Analytics opt-out add-on. Analytics data is kept for Google Analytics' standard retention period, then deleted.
Comments
If you leave a comment, the blog stores the name, email address and website you enter, your comment, your IP address and your browser's user agent. Your email address is never shown. Comments are checked for spam by Akismet, a service from Automattic, which receives the comment and those details to do it (Automattic's privacy policy). A comment stays as long as the post does, unless you ask me to remove it.
The contact form
If you use the contact form, your name, email address and message, with your IP address and the time, come to me as an email. They're sent through Amazon SES, an email service from Amazon Web Services (AWS's privacy notice), to my personal Gmail inbox. I use them only to reply to you. The email stays in my inbox until I delete it, and you can ask me to delete it at any time.
Hosting and logs
The blog runs on my own server, behind Cloudflare, which handles the connection and protects the site from attacks (Cloudflare's privacy policy). Like most websites, the server logs each request (your IP address, the page, the time and your browser's user agent). I use those logs only to keep the site working and secure, and they're deleted after a short time.
OpenSEO, and the Google data it reads
OpenSEO at seo.finzel.co.uk is my private SEO dashboard: the open-source OpenSEO app, running on my own server. I use it to look after my own websites' search traffic. It isn't offered to the public, and nobody else has an account. The only person who signs in with Google, and whose Google data it reads, is me.
What it reads, and the permissions it asks for
OpenSEO connects to Google only after I sign in with Google and agree on Google's consent screen. It asks for these permissions (OAuth scopes), and all of them are read-only:
| Permission | What OpenSEO reads with it |
|---|---|
https://www.googleapis.com/auth/webmasters.readonlySee your Search Console data | The list of sites in my Search Console account, their search performance (search queries, pages, clicks, impressions, click-through rate and average position), and URL inspection results. |
https://www.googleapis.com/auth/analytics.readonlySee your Google Analytics data | The list of my Google Analytics accounts and properties, and their reports (sessions, users, pages, traffic sources and engagement), mainly to see visits that came from search. |
openid, email, profile | My Google account's ID, email address and name, so OpenSEO knows which Google account a connection belongs to. |
It can't add, change or delete anything in Search Console, Analytics or my Google account.
How it uses the data
Only to show me how my own sites are doing in search, in OpenSEO's dashboard and reports, so I can decide what to fix or write next. It isn't used for advertising, isn't sold, and isn't used to build profiles of anyone.
I don't use Google data to develop, improve or train any AI or machine-learning model.
Who it's shared with
I don't sell, rent or share Google data, or pass it to advertisers, data brokers or anyone else. The only exceptions would be if the law required it, or to deal with a security problem.
OpenSEO also uses DataForSEO, a paid data service, for keyword research. That works from the keywords and domains I type in. My Google data isn't sent to it.
Where it's kept, and how it's protected
On my own server. The Google access and refresh tokens are encrypted before they're stored, every connection to OpenSEO and to Google uses HTTPS, and OpenSEO sits behind a login that only I can use.
How long it's kept
- Google sign-in tokens: until I disconnect Google in OpenSEO or revoke access in my Google account. A connection that no OpenSEO project uses is deleted, and revoked at Google, within about a day.
- Search Console and Analytics reports: OpenSEO keeps cached copies of recent reports so its pages load quickly, and refreshes them from Google as they go out of date. When I disconnect a site, its cached Search Console data is deleted.
- Everything: if I stop using OpenSEO, I delete its data from my server.
How to revoke access
- In OpenSEO: Project settings → Integrations → Disconnect. This deletes the stored tokens and revokes them at Google.
- In your Google account: go to myaccount.google.com/connections (Google Account → Security → Your connections to third-party apps & services), pick the app, and choose Delete all connections. OpenSEO then can't read anything more.
To have anything deleted that OpenSEO already holds, use the contact form.
Google API Services User Data Policy
OpenSEO's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Your rights
Under UK data protection law you can ask me for a copy of the personal data I hold about you, and ask me to correct or delete it. Ask through the contact form and I'll reply within a month. If you're not happy with my answer, you can complain to the Information Commissioner's Office.
Neither site is meant for children, and I don't knowingly collect data about them.
If this policy changes, I'll update it here and change the date at the top.