Privacy Policy
In force since 5 September 2026
This copy is not complete. The operator's legal identity and contact address have not been configured on this deployment, so they are not shown rather than shown wrong. Everything below describes what the service actually does with your data.
This page describes what this service actually does with your data. It is written against the code, not copied from a template: every item below corresponds to a field that exists in the database or a request that is really made.
1. What we collect
| Data | Why | Kept |
|---|---|---|
| Your email address | It is your account. It is how you sign in and how we can reach you about the service. | While the account exists |
| A hash of your password | To check your password without storing it. The password itself is never written down anywhere, so we cannot tell you what it is — only reset it. | While the account exists |
| The URLs you audit and the reports produced | They are the product. You need to be able to open a report again and compare it with an earlier one. | While the account exists, or until you delete the audit |
| Domains you have verified as yours | Active checks (crawling, browser rendering, load and injection testing) only run against domains whose ownership you have proved. | While the account exists |
| Your plan, the audits used this month and any extras | To bill correctly and to show you where you stand. | While the account exists; billing records for as long as tax law requires |
| A Stripe customer identifier | To connect your account with your subscription. Card numbers never reach our servers — the payment happens on Stripe's own pages. | While the subscription exists |
| Your IP address, in memory, briefly | Rate limiting. Without it one script can exhaust the service for everyone. | Minutes, in a cache — not in the database |
| Taps on your phone number or your email address, if you install our tracking snippet on your own site | It is the conversion that matters to a trade business: you get calls, not form submissions. We store which of your own numbers was tapped, the page it happened on, and when — so you can tell whether it is the mobile or the landline people use. | While the account exists |
Which ad or search sent each enquiry, if you install the snippet: the
utm_source, utm_medium and
utm_campaign from your own ad links, the
domain name only of the site they came from, and the
path only of the first page they landed on |
So you can tell which campaign brings paying work and which does not. These are labels you put in your own ad links; the domain and the path describe the traffic, not the person. We deliberately do not keep the rest of either address — a search page's address contains what somebody typed, and a page's query string can contain another customer's name. | While the account exists |
If you install the tracking snippet on your site
The snippet is about 900 bytes of JavaScript that you paste into your own
site. It sets no cookies, reads none, and stores nothing in the
visitor's browser. When someone taps a tel: or mailto:
link it sends us three things: which type of link it was, the number or address
it pointed at — yours — and the path of the page. It also sends the
campaign labels from your own ad link, the domain name of the site they came
from, and the path of the first page they landed on, so that your dashboard can
say which ad brought the enquiry.
It sends nothing that identifies the visitor: no IP address, no browser fingerprint, no identifier, no session, and nothing at all about anything they did on any other site. We are not able to tell you who tapped, or whether the same person tapped twice, because we never receive anything that would let us work that out. And a tap is not a call: it means the phone opened its dialler.
The campaign labels are kept in sessionStorage for the length of
that one visit, so that a tap on your contact page still knows which ad brought
them to your home page. It is cleared when they close the tab, it is not a
cookie, and it is not readable by any other site. If their browser blocks site
storage, the tap is still counted and we simply do not know where it came
from — we say so in your dashboard rather than guessing.
If you sign in with Google
We ask Google for two things and nothing else: your email address and whether Google has verified it. We do not receive your Google password, your contacts, your files or your calendar, and we cannot act on your Google account.
2. What we do not do
- We do not sell or share your data. Not to advertisers, not to data brokers, not to anyone.
- There are no advertising or tracking cookies, and no third-party analytics script on this site. That is also why you are not being asked to accept cookies: there is nothing to accept. The tracking snippet
described in section 1 sets no cookies either; the campaign labels it keeps live
in
sessionStoragefor that one visit and are gone when the tab closes. Whether your own site needs to disclose it is a question for your site, not ours — we tell you exactly what it stores so you can say so. - We do not build a profile of you and there is no automated decision-making with legal effects.
- We do not read audited sites for any purpose other than producing your report.
3. Cookies
Two, both strictly necessary:
- A session cookie that keeps you signed in. Without it you would be signed out on every page.
- A short-lived sign-in cookie (about ten minutes) used only while you are signing in with Google, to prove that the reply coming back is the answer to the request you started. Without it, someone else could finish the sign-in on your behalf.
4. Who else processes your data
- Stripe — payments and subscriptions. They receive your email and your card details, which they handle directly; we never see the card.
- Google — only if you choose to sign in with Google, and only for that sign-in.
- Our hosting provider — runs the servers and the database and therefore holds the data at rest.
That is the complete list. Nobody else receives your data.
5. Your rights
You can ask us to show you the data we hold, correct it, delete it, give you a copy in a portable format, or object to a particular use. Write to the contact address above and we will act on it. If you are in the EU or the UK you can also complain to your data protection authority; in Australia, to the Office of the Australian Information Commissioner (OAIC).
Deleting your account deletes your audits and reports with it.
6. How it is protected
- Everything travels over HTTPS.
- Passwords are stored hashed, never in the clear.
- The process that opens a browser on audited pages runs without the service's credentials in its environment, so a flaw in the browser cannot reach them.
- The audit engine refuses to fetch anything that resolves to a private or internal address, so it cannot be pointed at our own infrastructure — or anyone's.
7. Changes
If this policy changes in a way that affects you, the date at the top changes and we tell you before it takes effect.