Overseer ← Home

privacy

What Overseer collects on this site, why, and how long it keeps it. We keep as little as we can.

Last updated 28 October 2026

Who we are

Overseer (“we”, “us”) is run by its founder in the United Kingdom and is responsible for the personal data described here. When Overseer moves into a company, we’ll name that company on this page.

Questions or requests: support@ovrhq.dev.

This page covers the ovrhq.dev website, the beta waitlist, and signing in to Overseer. The Overseer app runs on your own computer; we’ll describe how it handles data here before it’s publicly released.

What we collect

If you join the waitlist, we keep your email address, when you joined, whether you joined on the site or by signing in, and where you are in the queue (waiting, invited or joined).

If you sign in with Google or GitHub, that service tells us your account ID there, your email address and your name. From GitHub we take your primary verified email, and your username if you haven’t set a name. We store these with the date your account was created and your access level. We never see your Google or GitHub password. The access the service grants us is used once, to read those details, and is not stored. We don’t store your profile picture or anything else from your account. Signing in also adds you to the waitlist if you aren’t on it already.

When you stay signed in to the app, we keep a one-way fingerprint (hash) of your session token, which account it belongs to, and when it expires. We can’t turn the fingerprint back into your token.

While a sign-in is in progress, we briefly keep random one-time codes that link the browser step back to the app on your computer, plus your account ID once you finish.

To stop spam and abuse, we count how many requests come from each network. We don’t store your IP address. We store a salted one-way hash of it (for IPv6, of your network’s prefix) next to a counter.

If you email us, we keep the email so we can reply.

Cookies and tracking

This site sets no cookies and stores nothing in your browser. We don’t use analytics, advertising or tracking scripts, and the site loads nothing from other websites. Our host, Cloudflare, may set a strictly necessary security cookie if it ever needs to check that a visitor isn’t a bot.

Why we use it

We don’t sell your data, use it for advertising, or use it to train AI models.

Data from Google

When you sign in with Google, we ask only for your basic profile: your Google account ID, email address and name. We use them only to create your Overseer account and recognise you when you sign in again, and we don’t share them with anyone. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

You can remove Overseer’s access at any time from your Google account or your GitHub settings.

How long we keep it

Expired records are cleared automatically once a day. If Overseer shuts down, we’ll delete everything.

Who else handles it

These providers may process data outside the UK, including in the United States. When they do, they use safeguards recognised under UK law, such as the UK International Data Transfer Addendum or the UK Extension to the EU–US Data Privacy Framework.

We don’t share your data with anyone else unless the law requires it.

Your rights

Under UK data protection law you can ask us to show you the data we hold about you, correct it, delete it, send it to you in a portable format, or stop or limit how we use it. Where we rely on consent, you can withdraw it at any time. Email support@ovrhq.dev and we’ll reply within one month.

If you’re unhappy with how we’ve handled your data, you can complain to the Information Commissioner’s Office at ico.org.uk. We’d appreciate the chance to put it right first.

Children

Overseer isn’t meant for anyone under 13, and we don’t knowingly collect their data. If you think a child has given us their details, email us and we’ll delete them.

Changes

If we change this policy, we’ll update this page and the date at the top. If a change affects how we use data we already hold, we’ll email the people affected first.