Privacy

If you are here because you saw the tracker on a site

Nothing is stored on your device. No cookie is set, no identifier is kept, and there is nothing for you to opt out of that would still leave something behind.

The site you visited records the page, the referrer, your browser, operating system and device type, and roughly where you are — the country and the nearest city your internet provider’s address block is registered to. That is the city, not you: everyone on the same provider in the same area resolves to the same point, and the coordinates stored are the centre of that city rather than anywhere you have been.

Your IP address is not stored. It is used at the moment of the visit to work out the country and city above, and to make an identifier by hashing it together with your browser string and a secret that is replaced every night. Once that secret rotates, yesterday’s identifier cannot be linked to today’s — by anyone, including us. That is what allows a visitor count without a cookie and without any way to follow you between days, and it is a property of the design rather than a promise about our conduct.

There is no cross-site tracking, and nothing records the page a visitor sees. A site owner can switch on two options, both off by default: a click heatmap and a replay of the pointer on a sample of visits. They store positions as numbers — never an element, a label, text, or anything typed into a field — and are deleted after thirty days.

What we collect about you, the customer

When you sign in. We use Google or GitHub to sign you in. From them we receive your email address, display name and avatar image. We never receive or store your password for either service.

When you connect Google. Every scope we ask for, and what it is for, is listed under Google user data below. We store the tokens so scheduled reports can run. Disconnecting from the dashboard revokes them.

When you pay. Payment is handled entirely by Stripe. Card numbers never reach our servers and we cannot see them. We receive only a confirmation that a payment succeeded, and the amount.

Google user data

Connecting Google is optional and powers three features. We ask for the narrowest scope that each one can work with, and none of them can write to your Google account.

• Search Console (webmasters.readonly) — reads the queries, clicks and positions Google already reports for properties you have verified, so the Keywords section can show what you rank for. The writable Search Console scope is deliberately not requested: it could add properties and submit URLs, and nothing here needs to.
• Analytics (analytics.readonly) — reads your GA4 figures so they can be shown beside ours while you are checking a migration. It cannot change a property, a stream or a setting.
• Keyword Planner (adwords) — requested only where a Google Ads developer token is configured, and used only to look up search volume, bid ranges and related keyword ideas for keywords or pages you enter. We do not create, edit, pause or spend on campaigns. Google publishes no read-only variant of this scope, which is the only reason a broader one is requested.
• Sign-in identity (openid, userinfo.email, userinfo.profile) — your email address, name and avatar, used only when you choose to sign in with Google, to sign you in and to label your account. The connect flow does not ask for these. If you have signed in with Google before, they still appear on the connect screen, because Google adds scopes you have already granted this application rather than replacing them.

Limited Use. Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Data obtained through these scopes is used only to provide the features above. It is never sold, never transferred to a third party except as necessary to provide those features or where required by law, never used for advertising, and never used to train any generalised or artificial-intelligence model.

How Google data is protected

• In transit — every request to and from Google, and every request between you and this site, travels over TLS. There is no unencrypted path.
• At rest — tokens and the reports they fetch sit in our Supabase Postgres database, which encrypts its storage at rest.
• Reachable only by the server — the tables holding Google tokens are read exclusively by server-side code using a privileged key that never leaves the server. No token is ever sent to a browser, included in a page, or exposed through the public API, and a signed-in customer cannot read another customer’s connection.
• Not read by people — Google data is processed automatically. Nobody here reads your Search Console, Analytics or Keyword Planner data, except in the narrow case where you ask us to look at something to resolve a support problem, or where the law requires it.
• Revocation and deletion — disconnecting from the dashboard deletes the stored tokens and the data fetched with them. Deleting the site or your account does the same. You can also revoke access at any time from your Google account permissions, which stops the scheduled reports at once.

The data you collect is yours

Analytics gathered through your sites belong to you. We do not sell them, do not share them with advertisers or data brokers, and do not use them to build any audience or profile across sites. You can export everything through the API and delete a site and all of its data from the dashboard.

A dashboard is private until you publish it. If you switch one to public, its traffic figures become readable by anyone with the link — that is the point of the feature, and it is off by default.

Who else processes data

• Supabase — database, sign-in and file storage
• Railway — application hosting
• Stripe — payment processing
• Google and GitHub — sign-in, if you choose to use them
• Resend — the emails we send you
• OpenAI, Anthropic, Google, Perplexity and xAI — only if you enable AI visibility, and only the questions it asks. Your visitor data is never sent to any of them.
• Anthropic — the text of keyword ideas from a keyword research search, to estimate each one’s search intent. Nothing else from your Google account or your visitors is included.
• Moz — a single keyword and market, only when you press “Check difficulty” on it.
• Google PageSpeed Insights — the public addresses of pages the site audit checks with Lighthouse, which Google then loads like any visitor would.

Cookies

On this site we set one kind of cookie: the session cookie that keeps you signed in. There are no advertising or third-party tracking cookies here, and the tracker we distribute sets none at all.

Keeping and deleting data

Raw events are kept for 30 days on the free tier and 365 on a paid plan, then deleted. Daily rollups — counts with no per-visit detail — are kept indefinitely, which is what lets a chart span years without keeping a log of individual visits.

You can delete your account and everything in it from the dashboard, or ask us to at johnnyhashim@gmail.com. Where a payment record must be kept for tax purposes, we keep the minimum required and detach it from your account.

Contact

Questions, corrections and deletion requests go to johnnyhashim@gmail.com.