When someone fills out a form on a website, the server handling that request can usually see their IP address, a number that, in combination with other data, can be used to work out fairly precisely where someone is and to track them across visits. A lot of sites keep that number by default, often without anyone deciding to, simply because it is there and nobody turned it off.

Approximate location is the deliberate alternative. Instead of storing the precise IP address, the lead record keeps only a rough city and region, enough to know generally where an enquiry came from, without keeping the kind of identifying detail that turns a simple contact form into a privacy liability sitting in a database somewhere.

Why it matters to you

A business collecting leads through a website is, whether it thinks about it this way or not, also collecting a small amount of personal data about the people who submit those forms. The less precise and identifying that data is, the less there is to protect, and the less there is to explain if a customer or a regulator ever asks what gets kept. Storing only an approximate region rather than a precise IP address is a meaningfully lower privacy footprint for essentially no loss of usefulness, since most businesses only ever wanted to know roughly where enquiries were coming from in the first place.

How I set it up

Every lead that comes through a site I build gets written to a private database in the business’s own Cloudflare account before an email notification goes out, so the lead survives even if the email itself is missed or deleted. As part of that write, the location field that gets stored is a coarse city and region rather than the visitor’s actual IP address. The IP address is never written to the record at all.

This sits alongside the rest of how lead tracking works on these sites: the goal throughout is to capture what is genuinely useful for following up with a customer and running the business, without accumulating identifying detail that serves no real purpose once the lead has been actioned.

What it looks like in practice

Open the record for a lead and you will see a name, contact details, the message they sent, and a rough location like a city name. You will not see an IP address, because it was never kept. If a business is ever asked what data it holds on a website visitor who submitted an enquiry, the honest answer is short, and that is by design rather than an oversight.

Questions I get about this

Why record any location at all if it's only approximate?
A city and region is genuinely useful, for example knowing whether a lead is inside your service area, without keeping anything precise enough to identify or track an individual visitor.
Isn't an IP address needed to run the site properly?
It passes through Cloudflare's network as part of normal traffic handling, the same as any website, but it is not written into the lead record that gets stored afterward. What is kept is the rough location, not the identifying number.
Does this affect how well the business can follow up with a lead?
No. Following up with a lead depends on the name, phone number and message they submitted, none of which this affects. Approximate location is a small extra field, not the substance of the lead.

Want this set up properly for your business?

This is the kind of thing I build every week. Grab a time and we will talk through what fits.