Cookie and Tracking Notice

We use essential browser storage and cookies to keep users signed in, secure sessions, remember settings and operate the service. These are necessary for the features requested by the user. Where we use optional analytics or marketing technology, it should be controlled through the consent choice shown on the relevant site.

When a customer installs the Call Bullet script or WordPress plugin, it can store a first-party session identifier and record source, campaign, landing page and page activity so a later phone call can be connected to the visit. It swaps displayed numbers from the customer’s configured pool. It does not itself create a cross-customer advertising profile.

On Call Bullet's own website we use the Meta Pixel and Meta's Conversions API to measure which Facebook and Instagram ads bring visitors, demo bookings, sign-ups, checkouts, paid plans and number orders, and to help Meta show our ads to similar people. Meta Platforms Ireland Ltd receives the page visited, the ad click identifier, browser cookies (_fbp, _fbc), IP address and browser type, and — only if you accept — a hashed (SHA-256) email address and account ID when you sign up or pay.

In the UK, EU, EEA and Switzerland (or if we can't tell where you are) none of this runs until you press Accept. Rejecting is as easy as accepting. Change your mind any time with Cookie settings in the website footer; a refusal stops new browser and server events straight away. We keep a record of each choice (time, region and notice version). We also count ad arrivals by campaign and day without cookies or any personal identifier. For visitors who arrive from an ad, Call Bullet itself records which of our pages were viewed and which steps (sign-up, sign-in, checkout, payment, number order) followed, so we can see what our advertising achieves; this record stays with Call Bullet.

The website owner decides to deploy the script and is responsible for an appropriate privacy and cookie notice, consent where required, and correct configuration. The owner can withhold the Call Bullet consent signal so source details are not sent. Disabling storage or the script may prevent dynamic number swapping and attribution.

Browser controls can remove or block cookies and local storage. Customers should also provide any consent control required for their visitors. Essential authentication and security storage cannot be disabled while continuing to use signed-in features.

The Privacy Notice explains the personal information involved, purposes, sharing, retention and rights. Contact info@callbullet.com with the website address and approximate visit time if you need help identifying Call Bullet technology.