What is an IP address, and why does every website get one?

An IP address is the number your device uses on the internet. When someone opens your website, their browser sends the address to your server, so the server knows where to send the page back. No website can work without receiving it.

The same happens for every other server the page talks to. An analytics script, a chat widget, an embedded video or a font loaded from another company's server: each one receives the visitor's IP address too.

Most home and mobile connections get a "dynamic" address, which changes from time to time. On its own it doesn't say who you are. Only your internet provider knows which customer had which address at which moment.

What did the Court decide in Breyer?

Patrick Breyer sued the German federal government. Its websites stored visitors' IP addresses, with the date and time of each visit, to defend against cyberattacks and to make it possible to bring criminal proceedings. He wanted them to stop.

The question for the Court of Justice was whether a dynamic IP address is personal data for a website owner who can't identify the visitor by itself. Its answer, on 19 October 2016: yes, if the website owner has the legal means to identify the visitor with the help of extra information held by the internet provider.

In Germany there were such means. After a cyberattack, the website owner could go to the authorities, who could get the subscriber's details from the provider. That was enough. The website didn't need to hold the name itself, and it didn't need to plan to look it up. It mattered that a lawful route existed.

The Court said a second thing that gets less attention. A website owner may have a legitimate interest in storing some visitor data to keep its site working and to protect it against attacks. German law at the time didn't allow that balance to be made, and the Court said EU law requires it. So Breyer isn't "you may never keep an IP address". It's "an IP address is personal data, so you need a good reason and the usual safeguards".

Does GDPR say the same?

Breyer was decided under the old Data Protection Directive. GDPR, in force since May 2018, is more direct about it:

  • Article 4 defines personal data as information about an identifiable person, and names "an online identifier" as one way a person can be identified.
  • Recital 30 gives IP addresses as an example of such an identifier, next to cookie identifiers. It says these traces, combined with other information, can be used to build profiles of people and identify them.
  • Recital 26 sets the test: take into account all the means "reasonably likely to be used" to identify someone, by you or by anyone else.

Put together: for a business running a website, the safe starting point is that your visitors' IP addresses are personal data.

What if you shorten or hash the address?

A common idea is to cut off the last part of the address, or to replace it with a code (a "hash"). Both help. Neither makes the address anonymous for the business that does it.

  • The SRB ruling (2025). On 4 September 2025, in EDPS v SRB, the Court of Justice said that pseudonymised data (data where the names have been replaced with codes) isn't personal data for everyone in every case. For a recipient who has no way to link the codes back to people, it may not be. But for the organisation that holds the key, it still is. And whether data is personal is judged from that organisation's side, at the moment it collects the data.
  • The European Data Protection Board (2025). Its draft guidance on pseudonymisation says pseudonymised data that can be linked back to a person with extra information is personal data, even when the data and the extra information are held by different people. It also warns that a plain hash can be reversed by hashing every possible input and comparing. There are only about four billion older-style (IPv4) addresses, so that's easy to do.
  • The Italian regulator (2022). When it ordered a website to stop using Google Analytics, the Garante said an IP address is personal data and that even a shortened one doesn't become anonymous, given Google's ability to combine it with other data it holds.

So shortening and hashing are good safeguards. They're not a way out of GDPR for the business that does them.

Where do your visitors' IP addresses go?

This is where the rules bite for most small businesses. You probably don't store IP addresses yourself. The tools on your site receive them for you.

  • Google Analytics, 2022. Several European regulators acted against websites using Google Analytics, because visitor data, IP addresses included, went to the US without enough protection. Italy's regulator gave one website 90 days to fix it. The French regulator, the CNIL, says changing how a tool handles the IP address isn't enough on its own, because the visitor's device still talks directly to the tool's servers. One answer it accepts is a proxy: a server in between, so the IP address never reaches the tool.
  • Bindl v Commission, 2025. On 8 January 2025 the EU's General Court ordered the European Commission to pay a visitor €400. The visitor had used a "Sign in with Facebook" link on one of the Commission's own websites, and that sent his IP address, among other data, to Meta in the US without proper safeguards. The €400 was for the uncertainty he was left in about what happened to his data. One visitor, one login button, a real award.
  • The US rules since 2023. On 10 July 2023 the European Commission adopted the EU-US Data Privacy Framework. Since then, data can go to US companies certified under it without extra paperwork. In Latombe (3 September 2025) the General Court dismissed a challenge to that framework. A further appeal can change this, as it did twice before, so check where each tool sends data and whether it's certified.

There's also a separate rule. The ePrivacy Directive asks for consent before a script stores or reads anything on the visitor's device. The European Data Protection Board says this can cover tracking techniques that work with the IP address alone. We cover that in Is website visitor identification GDPR compliant?.

What should a website owner do?

  1. List what's on your pages. Every script, font, video embed, chat widget and form tool receives your visitors' IP addresses. Your browser's developer tools show which servers each page talks to.
  2. Ask each vendor four questions. Do you store the IP address? For how long? Do you shorten or hash it, and who holds the key? Which countries does it go to?
  3. Prefer tools that let it go. A rough location (country, city) can be worked out at the moment of the visit, and the address dropped. You rarely need the address itself.
  4. Keep only what you have a reason for. Breyer accepts that security is a valid reason to keep some data for a while. Write the reason down, set a short retention period, and stick to it.
  5. Say it in your privacy policy. Name the tools, what they receive, why, and where the data goes.
  6. Load what needs consent only after consent. Your cookie banner should hold back any tool that stores or reads anything on the device.

For more on choosing tools, see GDPR-friendly visitor tracking.

How does Signal handle IP addresses?

We make Signal, a tool that reads what visitors do on your site and offers the ready ones a call, a call back or WhatsApp. Like any website tool, it receives your visitors' IP addresses. Here is what it does with them, as written in its code on 14 November 2026.

  • Location and network, at the moment of the visit. When a visit starts, Signal looks up the rough place (country, region, city) and who owns the network, using a database on its own servers. The address isn't sent to anyone else for this.
  • What it stores from that lookup. The place, only when analytics is allowed. An organisation's name, only when the network belongs to an organisation such as a company or university; home and mobile providers never show one, because a provider's name says something about the person. A data centre's network is kept for spotting bots. The address itself isn't stored.
  • Not in the database or logs. Signal's request logs keep the method, the path and the host, not the IP address.
  • A spam check. When someone sends a form, Signal keeps a one-way code made from the IP address, the website and the day, mixed with a secret key, so the same address can't be matched across websites or days. It's deleted after two days. Under the rulings above, we treat that code as personal data while it exists: it's protection, not anonymity.
  • In memory, briefly. Rate limits that stop abuse hold the address in the server's memory for up to an hour, never on disk.
  • Where. Signal runs in Frankfurt.

So "we don't store your IP address" is true for Signal's database and logs. It isn't the same as "we never process it". No website tool can say that.

What we're not sure about

  • When a business visitor is a person. Signal can show an organisation's name for a visit from that organisation's own network. For a one-person business, that name can point to one person, so it can be personal data too.
  • How the latest rulings will be applied. The SRB judgment is recent, the Board's pseudonymisation guidance was still a consultation version when we checked, and the US framework could face a further appeal. Expect this to keep moving.
  • Your country's view. National regulators read these rules a little differently. Check yours.

Frequently asked questions

Is a static IP address personal data?

More clearly than a dynamic one. A static address stays with one connection, so it's easier to link to a person or a small office. Breyer dealt with the harder case, the dynamic address, and still said yes.

Is an IP address personal data if I never look up who it belongs to?

Usually yes. In Breyer, it was enough that a lawful way to identify the visitor existed. You don't need to use it.

Not for the address simply arriving: your server can't send the page without it. What you do next needs a legal basis, such as a legitimate interest in security. Consent can come in through the ePrivacy rules, if a script stores or reads anything on the device.

Does a company's IP address count?

Data about a company isn't personal data. But a company's address can point to a person, for example a sole trader, or someone working from home. Treat them with care.