Privacy Policy
Last updated: 2026-11-03
This policy describes what IP Locator does with data: what our server sees, what it keeps, what stays in your browser, what changes if you choose to sign in, and what we do not do at all.
1. Who we are and what this policy covers
IP Locator is run by an independent developer under the name LinnetLab, not by a company, based in Ireland. That developer is the data controller for this website and answers at the contact address below; this policy explains what happens to data when you use the site.
It covers this website only. The IP Locator mobile apps are separate products and carry their own privacy policies.
An account is optional. Everything on this website works without one, and unless you create one we never ask for your name, your email address or any other contact detail. What an account holds, and what signing in changes, is described in the two sections on accounts below.
2. What the service does
IP Locator shows you the public IP address your connection is seen with, and what is known about it: country, region, city and network provider. Whether the address belongs to an anonymizing network — a VPN, a proxy, Tor or a relay — and the separate VPN, proxy and Tor classifications all come from a dataset we do not hold today, so the service reports them as unknown rather than as “no”.
You can also type in a different address and look that one up instead of your own.
Location data for an IP address is approximate. It describes the network an address belongs to, not the person using it, and it can be inaccurate or out of date.
A signed-in account also sees the extended facts about an address: postal code, coordinates with the radius within which they are accurate, time zone, autonomous system, organization, domain, connection type and the network the address belongs to — for up to 3 new addresses a day, or 50 with paid access, which today only the service's owner grants to an account. An address our server already holds a fresh answer for does not count.
3. We run our own server
When you look up an address, your browser sends the request to our own server. That server necessarily sees the public IP address the request arrives from: seeing it is how it can tell you what your address is.
We say this plainly because it is the one thing you cannot check from the outside. The lookup does not travel from your browser straight to some third party. It comes to us first.
4. What we record about a lookup
We record every lookup, successful or not, in our service journal. The record contains the address that was looked up — the one you typed, or your own when you check it — exactly as it is.
Only the owner of the service reads the journal, and only until a record is deleted; the hosting provider named below operates the machine it lives on and has no reason to open it. We do not call these records anonymous or pseudonymous: the address is in them as it is, and whoever reads the journal reads the addresses.
A record holds the time of the lookup, the address, what was found, and whether the lookup succeeded. It holds no name, no email address and no account, also when you look up while signed in: only what you save is tied to your account, as the section on what you save to your account describes. The application's own event log is a different matter: the address never reaches it.
Journal records are deleted automatically 90 days after the lookup.
5. What we keep about looked-up networks
What is known about an address now comes from datasets held on our own server, so answering a lookup leaves nothing new to keep: we no longer add anything to this knowledge base.
What is still in it was kept while the service asked an outside provider about each address: the country, region, city, coordinates, time zone, network operator and the classifications, together with that provider's complete answer as it came, which can also carry the address's host name and postal code — filed under that address itself, in readable form.
The knowledge base holds nothing about who asked: no time of your lookup, no link to the journal, no account — only when the answer about that address was first and last obtained. And the address you check as your own is never written there: nothing you do on this website keeps what we learn about your own address anywhere beyond the journal entry described above.
An entry that no newer answer has refreshed for 365 days is deleted automatically. Nothing refreshes them any more, so the last of them disappears 365 days after the service stopped asking an outside provider.
The address you look up usually belongs to someone else: the operator of that network. What we kept about it came from that provider, not from them, and we had no way to inform them one by one — the address is all we know. This policy is that notice: the rights listed below apply to them just as they apply to you, at the same contact address.
6. What we keep from MaxMind's paid answers
There is a third store on our server. The IP Locator mobile app offers paid features, and when they are used — or when a signed-in account looks up an address on this website — our server obtains a fuller answer about the address from MaxMind's web service. Every such answer costs money, so we keep it for a while rather than ask twice.
Each answer is filed under the address it concerns, exactly as it is. The app and this website look up the user's own address too, so this store holds the own addresses of signed-in visitors and of people using the app's paid features. An entry holds what MaxMind answered — country, region, city, coordinates, time zone and network operator, with the complete answer as it came — and when it was first and last obtained. It holds nothing about who asked: no time of a lookup, no purchase, no account, no link to the journal.
Without signing in, this website only reads that store: a lookup made here causes no paid query and writes nothing to it, so nothing you do on this site without an account puts your address there. Signed in, a lookup made here is answered by MaxMind's web service when the store holds no fresh entry, and the answer is kept the same way; the address you look up, or your own on the home page, then goes to MaxMind, as described under international transfers. This happens for at most 3 new addresses per day (UTC) for an account, and 50 for an account with paid access, which today only the service's owner grants; beyond that, a lookup is answered without the extended facts and nothing goes to MaxMind. Our server counts the day's new addresses in its memory alone and stores the count nowhere. Which addresses the app sends to MaxMind, and on what terms, is described in the app's privacy policy.
An entry that no newer answer has refreshed for 30 days is deleted automatically.
7. Technical logs
Like any service on the web, our servers keep technical logs of the requests they handle: the web server that every request to this website, its API and the sign-in service passes through, and this website's own server. The web server in front of everything records the IP address a request came from, the time, which of our services it went to and your browser's user-agent string, but never the path requested, so neither the address of a lookup nor a link from the sign-in service's messages reaches its log. This website's own server, which serves only its pages, also records the page requested and the page that referred you.
We use these logs only to run the service: to keep it available, to enforce request limits and to investigate abuse. We do not profile you with them, and we do not combine them with anything else.
The application's own event log is deliberately kept free of addresses. It records the shape of the request path rather than the address that was looked up. The application sends it to our log server, which runs on the same machine as the application itself.
Technical logs are kept no longer than those purposes require. This website's own server and the application itself discard their logs when the service is next deployed. The web server in front of it and the sign-in service keep only the most recent lines of theirs — older ones are overwritten as new ones arrive — and discard them when they are reinstalled. The application's event log and the sign-in service's reports of its own errors are kept on our log server for 30 days.
The sign-in service's messages — address confirmation and password reset — go out through our own mail server. For each message it records in its logs the recipient's address, the time and the receiving mail server's answer; the text of the message and the link in it do not reach those logs, and your IP address is not in the sign-in service's messages. The server holds the message itself only until it is delivered — if the receiving server is unavailable, for a few days of retries; once delivered, it is kept by your email provider under its own policy. If a message cannot be delivered, a notice of that comes back to the sender's service mailbox with the recipient's address and the message's headers, and some mail servers attach the message itself, link included. Replies to these messages arrive there too, with their own headers. A copy of everything that arrives in the service mailbox is forwarded to our support mailbox, where we read it. These records, everything that arrives in the service mailbox and the copies in the support mailbox are kept for no longer than 14 days and then deleted automatically.
8. Your account, if you create one
You can sign in to this website with an IP Locator account, run by LinnetLab's sign-in service. It is an account for IP Locator only: other LinnetLab products do not accept it. The account is optional, and you can delete it at any time.
The sign-in service is run by the same developer as this website, on our own server, at auth.linnetlab.com. The account it keeps holds your email address, your name if you gave one or Google passed it on, the language you registered in or chose later, your password in a form that cannot be read back if you set one, and, if you signed in with Google, the link to your Google account. When you register with an email address, we send a message to that address so that you can confirm it is yours.
If you sign in with Google, Google learns that you are signing in to our website and passes us your email address, your name and your Google account's identifier. Google also sends the address of your profile picture, which the sign-in service does not keep. What Google does with that is governed by Google's own privacy policy.
This website receives only what it needs to show you who is signed in — your name and email address — and the account's language, so that it can switch to it as soon as you sign in. It keeps the name and email address in the open page alone, never in your browser's storage; the language, if the site speaks it, becomes this browser's chosen language for the site, as if you had picked it yourself, and switching the site's language does not change the account's. Our lookup service receives none of it: it knows a signed-in visitor only by the identifier the sign-in service gives the account, by whether the account has paid access, and by how many new addresses it has sent to MaxMind today — a count kept in the server's memory alone — never by email address or name.
While you are signed in, the sign-in service keeps a record of your session — when it began, and the network address and browser it began from — until the session ends: after half an hour without activity and at most ten hours after it began, or, if you ticked “Remember me”, after two weeks without activity and at most thirty days. Signing out ends it at once. For that time the service also keeps session cookies on its own address, so that signing in works across pages and visits; the pages of this website set none. If you tick “Remember me”, it also sets a cookie there holding your email address, kept for up to a year so that its form can fill the address in for you; signing out, or signing in without ticking the box, removes it.
To stop passwords being guessed, the sign-in service counts failed attempts to sign in to an account and forgets them after twelve hours without another failure. It also writes every request it turns down — a sign-in, a registration or a password reset that did not go through — to its own technical log, with the address it came from and what was entered except the password: the email address and, for a registration, the name. It also records there each message it could not send: the account's identifier and email address, the address the request came from and the error, which may quote the mail server's answer. That log keeps only its most recent lines — older ones are overwritten as new ones arrive — and is discarded whenever the sign-in service is reinstalled. Separately, the sign-in service reports errors in its own work — for example, when it could not reach Google or hand a message to the mail server — to our log server, which runs on the same machine as the sign-in service, so that we learn of them straight away: the time, where the error occurred and its technical description. If the error concerned your account, the description may contain the account's identifier or email address. Requests it turns down are not sent there. The log server keeps these reports for 30 days and then deletes them automatically.
You change your details, link or unlink Google, and delete the account under “Manage account” in the account menu. Deleting the account removes it from the sign-in service at once; what happens to the lookups you saved to it is described in the next section.
9. What you save to your account
While you are signed in, Save under a lookup result saves it to your account: the address in full, the country, the city, the provider, your note if you wrote one, and when you saved it. Only what you save goes there: the lookup itself, even one made while signed in, is not linked to your account, neither there nor in the service journal. What you saved shows on the Lookup History page on any device you sign in on.
No other user of the service can see what you saved; apart from you, only the owner of the service can read it, as with the service journal. Each entry is kept until you delete it, for no longer than a year from when you saved it, and then deleted automatically.
You can delete entries one by one or all at once on that page; they are deleted from our server, not hidden. You write the note yourself, and it is kept as you wrote it; do not put more about yourself in it than you need to.
If you delete your account without deleting what you saved, nobody can reach those entries through the service any more, because no one can sign in to that account again, and they are deleted automatically no later than a year after they were saved. Delete them before deleting the account if you want them gone at once.
Lookups saved in this browser without signing in are a separate list. Signing in does not upload them: while you are signed in, Save saves to your account, and the list in the browser stays as it was.
10. What stays in your browser
Some things are stored by your browser, on your own device. Except for the details of a sign-in under way, described in the last item, and the chosen language, in which the site opens the sign-in service's pages, none of it is ever sent to us:
- lookups you saved with Save without signing in, up to fifty of them, each with the full address, what was found out about it, and your note if you wrote one; a lookup does not get here without Save
- the theme you chose, light or dark
- the language you chose — after you sign in, your account's language if the site speaks it, until you choose another
- how densely you asked for the list of lookups to be shown
- a mark that you signed in on this browser, so that the site can restore your sign-in when you come back; it holds no token and nothing about your account
- while you are signing in, the details the page needs to finish that sign-in when you come back: they go to the sign-in service once, to finish it, and are then removed; those of a sign-in you abandoned are removed the next time you open the site, half an hour later or more
What is saved in the browser belongs to this browser alone: it is never uploaded, whether or not you sign in. What you save to your account is something else: it is kept on our server, and only what you saved while signed in goes there, as described above.
You can delete everything above at any time by clearing this site's data in your browser settings. Nothing about the service stops working if you do; at most you are asked to sign in again.
11. What we do not do
- The pages of this website set no cookies. If you sign in, the sign-in service sets cookies on its own address: session cookies, so that signing in works, and, if you tick “Remember me”, one holding your email address, as described in the section on your account; a visitor who never signs in never contacts it.
- We use no analytics, no tracking pixels and no third-party script that follows you around the web.
- We show no advertising. There is no advertising identifier and no advertising SDK anywhere in this website.
- We sell nothing here and process no payments. We never see payment details, because we never ask for any.
- We do not sell personal data, and we do not share it for advertising.
12. Third-party services
Without signing in, the address you look up is not sent anywhere. What is known about it comes from datasets MaxMind publishes, which we download and keep on our own server, or from an answer MaxMind's web service gave earlier, kept as described above; this website asks MaxMind nothing then, so MaxMind does not learn which addresses are looked up here. Only a lookup made while signed in — within the daily allowance of new addresses — asks MaxMind's web service about the address, and MaxMind then learns that the address was looked up — nothing about who looked it up. This product includes GeoLite2 data created by MaxMind.
These outside parties are involved in running this website:
- our hosting provider, which operates the machines the website, the API and the sign-in service run on;
- Google, only if you choose to sign in with Google: it confirms who you are to the sign-in service and passes on your email address, your name, your Google account's identifier and the address of your profile picture, which the sign-in service does not keep, as described in the section on your account.
13. Legal bases for processing
Where the GDPR applies, we rely on two bases:
- Performing a service you asked for, Article 6(1)(b). We process the address of a lookup you requested so that we can answer it, and, if you create an account, its details and what you save to it, so that you can sign in and see what you saved.
- Our legitimate interests, Article 6(1)(f). We keep technical logs and the service journal so the service stays available, request limits work and abuse can be investigated. The knowledge base about looked-up networks is no longer added to and is emptying as its entries expire. We have weighed this against your interests: the journal holds the address of a lookup but no name or email address, and it is deleted after 90 days; the knowledge base holds addresses people looked up but nothing about who looked them up and never your own; the store of MaxMind's paid answers holds addresses looked up while signed in on this website or through the app's paid features, but nothing about who looked them up, and is deleted after 30 days; and the logs are not used to profile anyone.
14. How long we keep things
- Service journal: 90 days from the lookup, then deleted automatically. Its records are not linked to any account.
- Lookups and notes saved to your account: until you delete them, for no longer than a year from when they were saved, then deleted automatically.
- Your account: until you delete it, which removes it at once.
- Your sign-in session: until you sign out, and at most ten hours, or thirty days with “Remember me”.
- Knowledge base about networks: 365 days from the last answer obtained for an address, then deleted automatically.
- Paid answers from MaxMind: 30 days from the last answer obtained for an address, then deleted automatically. The day's count of new addresses an account sent there: in the server's memory only, until the next day (UTC) or a restart, never stored.
- Technical logs: no longer than running and protecting the service requires. This website's own server and the application itself discard their logs when the service is next deployed; the web server in front of it and the sign-in service keep only their most recent lines and discard them when they are reinstalled. The application's event log and the sign-in service's reports of its own errors on our log server: 30 days, then deleted automatically.
- The mail server's records of the sign-in service's messages and everything that arrives in its service mailbox, notices of messages not delivered and replies included, and the copies of that mail in the support mailbox: no longer than 14 days, then deleted automatically.
- Data in your browser, including the lookups and notes saved there: until you delete it, on the Lookup History page or by clearing the site's data in the browser. We cannot delete it for you, because we cannot see it.
- Backup copies of our databases, kept only for restoring them, can hold journal entries (in copies taken before the journal stopped linking lookups to accounts, together with that link), lookups and notes saved to accounts, knowledge-base and paid-answer entries, a deleted account and the sign-in service's records of sessions, beyond the periods above: the nightly copies are deleted after 14 days, and the copies of the lookup service's database taken before each deployment are pruned at the next deployment, which keeps the three most recent and none older than 30 days.
- Server snapshots and copies: before work on the server we sometimes take a full snapshot of it by hand at our hosting provider, only to put the server back if the work goes wrong. Our hosting provider also makes a copy of the server's whole disk for us every day, to put the server back after a failure, and keeps only the latest: each new one replaces the one before. A snapshot and the copy hold everything that was on the server at that moment, the databases, their backup copies and the mail included, so any of the data in this list that is stored on the server can stay in them beyond its period — in the daily copy until the next one, usually no longer than a day. A snapshot is deleted at most 14 days after it is taken.
15. International transfers
Answering a lookup without signing in involves no outside party: the address you look up is not sent anywhere, and the data it is matched against is already on our server. A lookup made while signed in — on this website, up to 3 new addresses a day, or 50 for an account the service's owner has given paid access, cached addresses excepted — or through the mobile app's paid features sends the looked-up address to MaxMind, Inc. in the United States, which answers it under its data processing agreement with us and the European Commission's standard contractual clauses; MaxMind receives the address and nothing about who looked it up. The app's privacy policy describes the app's side of that transfer.
If you choose to sign in with Google, Google handles that sign-in under its own privacy policy and may process the data involved in the United States. From Google we receive your email address, your name and your Google account's identifier, which is the link described in the section on your account. Google also sends the address of your profile picture, which the sign-in service does not keep.
16. Your rights
If the GDPR applies to you, you have the right to:
- ask what personal data we hold about you
- have inaccurate data corrected
- have your data erased
- have our processing of it restricted
- receive your data in a portable form
- object to processing we base on legitimate interests
- complain to the data protection supervisory authority of the country you live in
Two notes on what this means in practice. The data in your browser is yours alone: we hold no copy of it and have no way to reach it, which is why you remove it yourself, as described above. Our own journal we can search by address if you tell us yours, and erase the records that carry it. A journal record cannot tell us who someone is: it holds an address, not a person. If you have an account, you see, change and delete it yourself under “Manage account”, and delete what you saved to it yourself on the Lookup History page; we will do either for you on request.
To exercise any of these rights, write to us at the address below.
17. Applicable law and supervision
Because the developer is established in Ireland, this service falls under Irish law and under the GDPR directly — not only when you happen to be reading from the European Union, but as a matter of where it is run from.
The supervisory authority for the developer is the Irish Data Protection Commission. You can complain to it, and you can equally complain to the data protection authority of the country you live in. Choosing one does not cost you the other.
18. Children
This website is not directed at children, and we do not knowingly collect personal data from children.
19. Security
Traffic between your browser and our servers is encrypted in transit. The journal holds addresses as they are, so what protects it is where it lives rather than how it is written: on our own server, readable only by the owner of the service, and emptied of every record after 90 days. When you are signed in, the token that proves it lives in the open page alone, never in your browser's storage, and is short-lived and renewed while you use the site. No method of storage or transmission is ever completely secure, which is why the server keeps only what it needs and for no longer than it needs it.
20. Contact
For any question about this policy, or to exercise the rights set out above, write to us:
21. Changes to this policy
We may update this policy. When we do, the date at the top of this page changes with it. A change that matters will be described here rather than made quietly.