This product exists to tell you who is on your site, so it is worth being exact about what that means. Most of what ClickHelm records never reaches us at all.
Last updated 2026-09-19
ClickHelm is operated by Hany Mahfouz. You can reach us at support@clickhelm.com about anything on this page.
There are two separate relationships here. Your visitors' data is recorded by the plugin into your own database, where you are the controller and we never see it. Your account data — your email, your licence, your billing — is held by us.
When somebody visits your site, the plugin records the following into the database on your own hosting. None of it is sent to us.
Because this sits in your database, you are responsible for disclosing it in your own privacy policy. If you operate in a jurisdiction that requires consent for this kind of processing, that obligation is yours and not ours.
Very little, and none of it is about your visitors. Twice a day each installation asks our licence server whether the key is still valid. That request carries:
Connecting a Google Ads account is optional, and nothing else in ClickHelm depends on it. If you connect one, ClickHelm reads the following Google user data through the Google Ads API, once a day. It writes to the account only the two things described on the Google Ads data page, and only if you switch them on: its tracking template, and an account-level IP exclusion list of the visitors you blocked.
It is used for exactly one thing: checking the clicks recorded on your site against the clicks Google actually charged you for. A click identifier that does not appear in Google's report was not a click Google billed, so it is excluded from your figures rather than counted against anyone. Google user data is never used for advertising, never used to build a profile of you or of anybody else, never combined with another customer's data, and never used to train any model.
Google user data is not shared, transferred or disclosed to anyone, and it is not sold - not to third parties, not to data brokers, and not in aggregated or anonymised form. The comparison happens between your site and Google, and its results are written into your own WordPress database, where only you can see them. No other ClickHelm customer and no other company receives any part of it.
The token that authorises the daily read is kept on your own server, not on ours. During the few seconds of the connection itself it passes through our licence server sealed with AES-256-GCM under a key held only in that server's configuration, and the row holding it is deleted the moment your site collects it - we keep no copy. Every request between your site, our server and Google travels over TLS. The reporting data itself is passed straight through to your site and is not stored by us; the only thing our server records about it is a daily count of how many API calls your licence made, so the shared quota can be managed.
ClickHelm's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. You can disconnect from your ClickHelm settings, or revoke access at myaccount.google.com/permissions, at any time: the daily read stops immediately and everything else in the plugin carries on working. A fuller account, including what Google's permission screen says and why, is at clickhelm.com/google-ads-data.
Five, each doing one thing:
That is the complete list, and none of them buy anything from us: we do not sell personal data of any kind, to anyone, in any form. No fonts are loaded from anyone else's server, and nothing on that list runs inside the plugin or in your account area.
Everything above is about the product. This is about the marketing pages you are reading now, which are a separate thing and are treated separately.
No advertising code runs on this website. Nothing is loaded from Meta and no script of theirs reaches your browser. Instead this server tells Meta, after the page has already been sent to you, that a page was opened and which one, and whether the visit led to downloading the free edition, so we can tell which of our advertisements were worth paying for. What goes with it is your address, the description your browser sends of itself, the page, and two identifiers this site stores in your browser: one to recognise a returning visit, one to remember which advertisement brought you. When the visit is a download, one more thing goes with it: the country, region and city your address points to. This server asks proxycheck.io for them and passes them to Meta only as one-way hashes, never as place names. It also remembers, for thirty days, which link brought you here — the tags a link carries, such as utm_source=tiktok, or simply that you came from an advertisement — and sends that with a download, so we can count downloads by where they came from. These cookies belong to clickhelm.com as a whole, including the account area at app.clickhelm.com, so that a sign-up or a purchase can be credited to the advertisement or link that led to it.
What it cannot see: anything on your WordPress site, anything the plugin recorded, or any visitor of yours. None of that is on this website, and there is nothing resembling this inside the plugin. The promise that visitor data never leaves your own server is about the product, and none of this touches it.
Because the sending happens here rather than in your browser, a tracker blocker cannot stop it. We would rather say that than let you assume otherwise. All three are ordinary cookies you can clear or refuse, which breaks the link between one visit and the next; and Meta's own advertising preferences at facebook.com/adpreferences govern what they do with what they receive. Nothing on this website stops working either way.
Two things about your account are measured the same way, and they belong in a sentence of their own because they are about you rather than about a page: when you confirm your email address, and when a licence is first paid for, our licence server tells Meta that it happened.
What travels with those is a one-way hash of your email address, for a payment the amount and the currency, and — when you came through this website — the same two browser identifiers and the link source described above, which for a payment are passed through the checkout so they arrive with it. Not your name, not your phone number, not your licence key, not any site you have activated, and nothing whatever about a visitor to it. The hash cannot be turned back into your address; it is there so Meta can recognise an account they already have and tell us which advertisement was worth paying for. That list is not a promise we ask you to take on trust: it is a test in our own suite, and if any of those ever started travelling the build would fail.
When you send a message through the form on this website, we keep what you typed into it — your name, email address, the department, the subject and the message, and the site address and licence key if you gave them — so the request can be answered and followed up. It is emailed to the department you chose and stored on our licence server. We also keep a one-way hash of the address the message came from, so the form cannot be used to flood anybody; the address itself is not stored. Messages are deleted after two years.
If you ask this website to email you the free edition, our licence server keeps your email address, the language of the page, when you asked and how many times, which link brought you, and a one-way hash of the address the request came from, so the form cannot be used to flood anybody. It sends you the link and nothing else. If you tick the box for tips and news, it also records that you agreed and when, and every such email carries a one-click unsubscribe.
This website tells Meta that the request happened, with your email address only as a one-way hash, so we can tell which advertisement led to it. An address without agreement to news is deleted twelve months after the last request; one that agreed is kept until you unsubscribe, and deleted twelve months after that. You can ask us to delete it sooner at privacy@clickhelm.com.
Visitor data on your server is cleaned up on a schedule you control in Settings, with one deliberate exception: people you have blocked are kept indefinitely, including their fingerprint. Deleting it would quietly undo the block and let them back in unrecognised. Your account data is kept while you have an account, and account and licence records for seven years afterwards where tax law requires it.
The visit figures above — the thirty-day reading and the daily counts — are kept for 400 days, one set per site per day, so your usage can be shown as a curve rather than a single number and you can be told before you outgrow your plan rather than after. Nothing else about a visit is kept on our side, and readings older than 400 days are deleted automatically.
You can ask us for a copy of your account data, ask us to correct it, or ask us to delete it, through the contact form under Privacy and data requests or by writing to privacy@clickhelm.com. Deleting your account data ends your licence.
Requests from your visitors come to you, not to us, because their data is in your database and we cannot see it. The plugin can export and delete an individual visitor so you can answer them.