iOS App Privacy Policy
Last updated: 2026-10-27
This policy covers the IP Locator app for iOS. It says what the app keeps on your device, what leaves it, who else is involved, and what our server does with what reaches it.
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 the app and answers at the contact address below.
This policy covers the IP Locator app for iOS. The app for Android is built from the same code and has a policy of its own, which reads the same except where the platforms differ. The IP Locator website is a separate product with its own privacy policy.
The app has no user accounts. There is nothing to sign up for, and it never asks for your name, your email address or any other contact detail.
2. What the app does
The app shows the public IP address your connection is seen with and what is known about it. Our server sends the app the country, city and network provider; an indication of whether the address looks like a VPN, a proxy, a Tor exit or another anonymizing network; an approximate location of the address — region, postal code and coordinates with their accuracy radius — and its time zone; and the autonomous system and network block it belongs to. With the paid features it also sends the internet service provider, the organization the address is registered to, its domain and the connection type. Only part of this appears on the screen.
It only ever asks about your own address. There is no field for typing someone else's in, and the app has no way to look one up — unlike the website, which does.
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.
3. What stays on your device
The app keeps the following on your device and sends none of it to us:
- lookups you chose to save — the full address, the country, city and provider that were found, and the time you saved it
- the note you attached to a saved lookup, if you wrote one — free text, and whatever you put there stays on the device
- your chosen appearance and language
- a count of how many manual refreshes you have used today, so the free daily limit can work
Nothing is saved on its own. A lookup is written only when you press save; refreshing the screen writes nothing.
You delete a saved lookup by swiping it away, with a moment to undo. There is no single button that erases everything: to remove all of it, clear the app's data in system settings or uninstall the app.
4. Backups
The app's database is part of the device backup. If you back your iPhone or iPad up to iCloud or to a computer, your saved lookups — full addresses and your notes — are in that backup.
Your appearance and language settings are not. You can exclude the app from backups in system settings.
5. Purchases
The app offers one optional purchase that unlocks the paid features for good. There is no subscription and nothing recurring. Payment is handled by Apple; we never see your card or your payment details, because they never reach the app.
To know whether you have bought it, the app uses RevenueCat. RevenueCat gives your installation a random identifier that is tied to nothing about you — not a name, not an email address, not an account — and we never send it anything that identifies you. It receives your purchase history from the store, along with what the store tells it about the device and country. It also records whether you have granted permission to track you across other apps; that is the answer only, never an advertising identifier, and the app never asks the question.
Purchases can be restored on a new device from the App Store. That restores the entitlement, not your saved lookups: those live only on the device they were saved on.
If you have bought the paid features, the app may send that RevenueCat identifier to our server along with its lookups, so that the server can tell your purchase from a free installation. Our server then asks RevenueCat whether the purchase is active and remembers the answer in its memory for up to a day. The identifier is written nowhere on the server — not in the service journal, not in any other store, not in the event log — and it leaves the server only in that question to RevenueCat.
The paid features also change where the answer about your address comes from. With them, our server sends the address the app looked up — your own — to the web service of MaxMind, Inc., and answers you from what MaxMind returns. MaxMind is in the United States, and the transfer is governed by MaxMind's data processing addendum and the standard contractual clauses it incorporates. MaxMind receives the address and nothing else about you: not the RevenueCat identifier, not the device. Without the paid features the address goes nowhere: it is answered from data held on our own server.
6. What the app does not do
- It contains no analytics, no crash reporting and no tracking library of any kind, and it keeps no diagnostic log of its own.
- It shows no advertising. There is no advertising identifier and no advertising SDK in it.
- It has no accounts, no registration and no sign-in.
- It does not ask for permission to track you across other apps and websites, and collects no advertising identifier.
7. What the app asks the system for
The app asks for no permission at run time — no location, no camera, no contacts, no files, no notifications. Nothing ever interrupts you with a request, because it needs nothing that would require one.
Its bundle carries a usage description for Face ID, required by a library the app is built with but does not use; the app never asks for Face ID. What an app has actually requested, iOS lists in Settings under the app — for this app that list stays empty.
8. What our server sees and keeps
When the app looks up your address, it asks 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 record every lookup in our service journal, and the record contains your address as it is — the one the app looked up — together with the time and the result. Only the owner of the service reads the journal; the hosting provider named below operates the machine it lives on. The address never reaches the application's own event log; that log is discarded on our server when the service is next deployed, and its copy is kept for 30 days on our log server, which runs on the same machine. Journal records are deleted automatically 90 days after the lookup.
Our web server also keeps ordinary technical logs of the requests it handles, which can contain the IP address a request came from, the time and which of our services it went to, but not the path requested. They are used to run and protect the service, not to profile anyone. The web server keeps only the most recent lines of its log — older ones are overwritten as new ones arrive — and discards it when it is reinstalled.
We also keep a knowledge base of what an outside data provider told us about networks. It is no longer added to — lookups are answered from datasets held on our own server — and its entries are deleted as they expire. Nothing the app does ever wrote to it: it holds only addresses that someone typed in on the website, and the app cannot type one in.
With the paid features there is a third store. When our server obtains an answer about your address from MaxMind's web service — see the purchases section — it keeps that answer under the address itself, your own, so that the same address is not paid for twice: anyone who looks it up within 30 days, through the app or on the website, is answered from that copy. The entry holds what MaxMind answered and when it was first and last obtained, and nothing about who asked: no identifier, no purchase, no time of your lookup. Without the paid features the server only reads this store and never adds to it. An entry not refreshed for 30 days is deleted automatically.
9. Third-party services
Without the paid features, the address the app looks up is not sent to any outside party: what is known about it comes from datasets MaxMind publishes, which we keep on our own server, or from an answer already kept as described above, and MaxMind never learns which addresses are looked up. With the paid features, our server sends the address to MaxMind's web service, as described under purchases. This product includes GeoLite2 data created by MaxMind.
Four outside parties are involved:
- RevenueCat, as described under purchases, tells the app — and our server, when it checks a purchase — whether you have bought the paid features.
- Google Play or the App Store, depending on where you got the app, handle the purchase itself and the delivery of updates.
- MaxMind, Inc., when you use the paid features: our server sends it the address the app looked up and receives what MaxMind knows about it. MaxMind is in the United States; the transfer is governed by MaxMind's data processing addendum and the standard contractual clauses it incorporates.
- our hosting provider, which operates the machines the API runs on.
10. 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 — with the paid features, by sending it to MaxMind for the fuller answer you paid for — and purchase data so that you get what you paid for.
- Our legitimate interests, Article 6(1)(f). We keep the service journal and technical logs so the service stays available, request limits work and abuse can be investigated. The knowledge base about 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 nothing that names a person, it is deleted after 90 days; the store of MaxMind's paid answers holds addresses but nothing about who looked them up, and is deleted after 30 days, and the logs are not used to profile anyone.
11. How long things are kept
- Service journal: 90 days from the lookup, then deleted automatically.
- Paid answers from MaxMind: 30 days from the last answer obtained for an address, then deleted automatically.
- Technical logs: no longer than running and protecting the service requires; the web server keeps only the most recent lines of its log and discards it when it is reinstalled; the application's event log is discarded on our server when the service is next deployed, and its copy on our log server after 30 days, automatically.
- Everything on your device: until you delete it, clear the app's data or uninstall the app. We cannot delete it for you, because we cannot see it.
- Backup copies of the database, kept only for restoring it, can hold journal, knowledge-base and paid-answer entries beyond the periods above: the nightly copies are deleted after 14 days, and the copies taken before each deployment are pruned at the next deployment, which keeps the three most recent and none older than 30 days.
- Purchase checks: the answer, together with the RevenueCat identifier it concerns and the day's count of paid queries made with it, stays in our server's memory for up to a day and is written to no journal, store or log.
- 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 database and its backup copies included, so journal, knowledge-base and paid-answer entries, the application's event log and the lines of the web server's log can stay in them beyond their periods — 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.
12. International transfers
RevenueCat is based in the United States, so the purchase data described above reaches it outside the European Economic Area. That transfer is governed by RevenueCat's own terms and safeguards, set out in the privacy policy linked in this document. Without the paid features, the address you look up is transferred nowhere: it is matched against data held on our own server. With the paid features, our server sends it to MaxMind, Inc., also in the United States, under MaxMind's data processing addendum and the standard contractual clauses it incorporates; the address travels alone, with nothing that identifies you.
13. 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
In practice the app holds almost nothing about you that we can reach. What is on the device is yours alone: we have no copy of it and no way to see it, which is why you remove it yourself. Our journal we can search by address if you tell us yours, and erase the records that carry it; what it cannot tell us is who someone is, because a record holds an address, not a person.
For anything held by RevenueCat or by the store you bought the app from, their own policies and controls apply. To exercise any right against us, write to the address below.
14. 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.
15. Children
The app is not directed at children, and we do not knowingly collect personal data from children.
16. Security
Traffic between the app 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. No method of storage or transmission is ever completely secure, which is why the app keeps what it keeps on your device rather than on ours.
17. Contact
For any question about this policy, or to exercise the rights set out above, write to us:
18. Changes to this policy
We may update this policy. When we do, the date at the top of this page changes with it, and a change that matters will be described here rather than made quietly.