Privacy & tracking limits

Click protection

Client websites send ad click identifiers, page and referrer addresses, IP addresses, country, browser information and phone or WhatsApp tap events to Fake Clicks Protector. Website owners can review these records. IP addresses selected for automatic blocking may be sent to Google Ads for campaign exclusions.

The tracker also sends automation status and screen width for risk scoring. Arrivals require an ad identifier in the page URL; supported contact taps can use that identifier later in the same site’s browser session. Identifiers are not verified as genuine paid clicks. Recording depends on the installed script, JavaScript, browser storage and successful requests; this is not a complete record of visitors or Google Ads clicks.

Core arrival and contact-tap recording currently continues even when the keyword region check fails or a recognized advertising refusal is present. The tracker does not supply a consent banner or persist evidence of advertising acceptance. Website owners must assess and provide the necessary lawful basis, privacy disclosures and consent controls before installation. Where core tracking requires consent, the website must withhold the tracker until that consent is given and prevent further loading after withdrawal; the keyword switch alone does not do this.

Optional matched keywords

Ad links may include the matched advertising keyword. When permitted, it is stored with the visit and subsequent phone or WhatsApp taps to measure contact intent. It is not the visitor’s actual search query and does not confirm a completed call or conversation. Keyword attribution is not sent as a Google Ads conversion by this feature.

The current no-banner option disables keyword measurement in consent-required or unknown regions. Elsewhere it respects Global Privacy Control and the website’s recorded refusal. Keyword attribution is kept for the browser session and cleared from future events when measurement is refused.

The current keyword gate excludes the EU/EEA, United Kingdom, Switzerland and Canada, as well as unresolved regions. It recognizes Global Privacy Control and a value of “denied” in cookie_consent or fcp_ad_measurement on the client website. Missing choices are not stored acceptance. Both browser and server region checks must permit a keyword; other consent platforms need integration. This gate is not a complete legal assessment for every location.

Your choices

Use the client website’s advertising privacy settings to refuse or withdraw measurement, or enable Global Privacy Control in your browser. Contact the website owner for access or deletion requests. Website owners must disclose this processing in their own privacy notice and connect their advertising privacy choices to the tracker before using keyword measurement.

Those recognized choices affect future keyword measurement, not deletion of existing records or core event collection. Websites using a separate consent platform must connect withdrawal to their tracker-loading controls as appropriate; contact the website owner for help.

Blocking is not website denial

A risk score is not proof of fraud or a person’s identity. After a successful blocking response, the browser suppresses supported phone and WhatsApp link navigation; the website itself stays accessible. Earlier taps, manually dialled numbers and script bypasses are not prevented. Google Ads exclusions require authorized access and successful synchronization and cannot reverse prior charges. Direct ad calls, connected calls, chats and verified savings are not measured by website taps.