1. Overview
MyIPHelp provides IP address lookup and network intelligence tools. We are committed to protecting your privacy. This policy explains what data we collect, how we use it, and your rights regarding that data.
2. Information We Collect
Your IP Address
When you visit the homepage, your public IP address is used to display your current geolocation. Your IP address is also logged as part of standard server and application logs for security monitoring, rate limiting, and abuse prevention. Our visitor statistics and Google Analytics also use it to find an approximate location. Our visitor statistics also use it to make a daily visit code (see Visitor Statistics below).
IP Addresses You Look Up
The addresses and domain names you look up on our pages are logged. Our traffic log records each request’s path with your IP address (see Application Logs below). A lookup sends what you looked up in the request’s path, for example /api/geoip/lookup/8.8.8.8 or a free tool’s page address, so the log shows it. The log is kept for 30 days.
A lookup that fails (an HTTP 4xx or 5xx response) is also recorded in our error statistics with its path, but any IP address in the path is replaced by a placeholder before it is stored, so an IP address you looked up is not kept there (a domain name you looked up can be). Our visitor statistics (below) record page paths with IP addresses replaced the same way. Google Analytics records the full page address, including any address you looked up (see section 5). Lookup results are cached so repeat lookups are fast: the cache holds geolocation and network data about the address looked up, not who looked it up.
Visitor Statistics
Separately from Google, the site counts page views itself. For each page view your browser sends our server the page’s path (without its query string; any IP address in it is replaced by a placeholder before it is stored), the referring page’s address (of which only the site is kept), any campaign (utm) tags, your screen width and your browser’s language. When you leave the page it sends the time spent and how far you scrolled, and for some views page-speed measurements.
Your browser also sends events on our tools (for example the type of lookup and the country of the address looked up), clicks on links to other sites, and downloads of our sample report.
The server keeps those details together with your browser family, device type, and the country, region, city and network it finds for your IP address in our own geolocation databases. It does not keep your IP address, your browser’s user agent or the full referring URL. Signed-in staff and known bots are not counted.
To count visits it uses a code made from your IP address and browser with a random key. Each day’s key is deleted when the next day’s is made. After that day, a visit cannot be traced back to your address, and visits on different days cannot be linked. We also use Google Analytics, described in section 5.
Account Information
If you create an account to purchase bulk reports, we collect your name, email address, and payment information. Payment processing is handled by third-party providers — we do not store your credit card details.
Bulk Reports
When you submit IP addresses for a bulk report, the list and resulting report are stored on our servers for 30 days so you can access and re-export your report. After this period, reports are automatically deleted.
Application Logs
Our application logs record request information including IP address, browser user agent, the referring page’s address, your browser’s language, pages visited, timestamps, response times, approximate geolocation (country, city), and IP classification (residential, datacenter, VPN, or Tor). The addresses checked with some of our tools, such as the IP Blacklist Check, are also written to these logs. These logs are used for security monitoring, rate limit enforcement, bot detection, and debugging. Traffic logs are retained for 30 days. Other application logs are rotated daily and retained for up to 30 days.
3. Cookies
We use the following types of cookies:
- Essential cookies: Required for the site to function: a session cookie and a CSRF protection cookie on the pages that need them (such as the bulk lookup, checkout and your account), and sign-in cookies when you sign in. Rate limits are applied by IP address (or by account when you are signed in, and by key for the API), not by cookie.
- Analytics cookies: Google Analytics sets two cookies:
_gatells visitors apart with a random identifier, and_ga_<ID>keeps the state of your session. Each lasts up to two years, as described in Google’s cookie usage page.
We do not use advertising cookies. Our own visitor statistics set no cookies and store nothing in your browser. We do not show a cookie banner: Google Analytics loads on every page for every visitor. Section 5 explains how to opt out.
4. How We Use Your Data
We use the information we collect to:
- Provide and operate the IP lookup, bulk report, and blacklist checking services
- Process payments for bulk reports
- Enforce rate limits and prevent abuse
- Detect and mitigate automated bot traffic
- Monitor and improve site performance and security
- Measure how the site and its tools are used
- Respond to support requests
We do not sell, rent, or share your personal information with third parties for marketing purposes.
5. Third-Party Services
We use the following third-party services:
- Payment processing: Payments are handled by a third-party processor. Your payment details are sent directly to them and are not stored on our servers.
- CAPTCHA: We use Cloudflare Turnstile to prevent automated abuse. This service may collect limited data as described in Cloudflare’s Privacy Policy.
- Error monitoring: We use Sentry for application error tracking. When an error occurs, limited technical context (such as the request URL and stack trace) may be sent to Sentry for debugging purposes.
- Hosting: The Service is hosted on infrastructure that may log standard server access information.
- Google Analytics: We use Google Analytics 4, loaded through Google Tag Manager, to understand how the site is used. It records the pages you view, by their full URL, including any address you looked up. It also records the referring page, your device, browser and screen, and an approximate location that Google derives from your IP address. Events are recorded too: events on our tools, such as the type of lookup and the country of the address looked up, and Google’s automatic events for scrolling, clicks on links to other sites, file downloads, form interactions, video plays and searches on the site.
- How Google handles it: Google Analytics 4 does not log or store IP addresses, according to Google. Google signals (Google’s feature that links visits to signed-in Google accounts) is off. Google processes the data under its Privacy Policy. Google may process this data in the United States and other countries.
Opting out of Google Analytics: Install the Google Analytics opt-out browser add-on, or use a content blocker that blocks www.googletagmanager.com; either stops data being sent to Google Analytics. Blocking the _ga cookies in your browser settings stops Google from telling your visits apart, but page views are still sent (deleting the cookies only resets the identifier). The site works the same without Google Analytics.
6. Data Retention
- Lookup cache: Data about the addresses looked up, not about who looked them up: location, network and blocklist results for up to one day, registry (RDAP) data for up to one week (MAC address vendor data, which is not about IP addresses, for up to 30 days).
- Traffic logs (website pages): Retained for 30 days, then automatically deleted. API requests are covered under “API usage” below.
- API usage: For each API request counted toward your usage, we keep a record of its time, the API key’s ID and the number of lookups, with no IP addresses, for 400 days. We also keep daily lookup counts for each API key, with no IP addresses, as billing history with no time limit. Both currently stay after your account is closed, linked only to internal account and key IDs (see “Account data” below). Separately, our traffic statistics count each API request by endpoint, response status and time, without the IP address looked up and without linking the request to your key or account. Each request’s entry is kept for 30 days; after that, we keep only daily totals per endpoint, with no time limit. Lookups made through our MCP server (
/mcp/v1), which lets AI assistants use the API with your key, are API requests and are counted the same way, under the MCP server’s endpoint. The addresses they look up are sent in the request body, never in the URL. See section 6 of our Terms of Service for details. - Failed API requests: If a request fails (an HTTP 4xx or 5xx response), we record its path, status, time, response time, whether our bot detection judged it to come from a person or a bot, and the referring site, if any. Any IP address in the path is replaced by a placeholder before it is stored, so the address looked up is not kept in these records. We keep each failed request’s entry for 30 days and a daily count of failures per path with no time limit. These are not linked to your key or account.
- Error statistics (failed requests on website pages): Each failed request’s path is kept for 30 days, without your IP address; after that, only a daily count per path, with no time limit. Any IP address in a path, such as one you looked up, is replaced by a placeholder before it is stored. Other values in a path, such as a domain name, can be kept as they are.
- Our visitor statistics: Each page view (path, source, device and place, with the day’s visit code) is kept for 90 days; after that, only daily totals (per page, source, place (country, region, city), network, device, browser, screen, language, campaign and event), with no time limit and no visit codes.
- Google Analytics: Event-level data is kept for two months and user-level data until 14 months after your last visit, in our Analytics property, then deleted by Google; aggregated reports (totals with no identifiers) are kept.
- Application logs: Rotated daily and retained for up to 30 days, then automatically deleted.
- Statistics archive: The individual entries behind our traffic statistics (request counts, with no IP addresses), error statistics, visitor statistics and API usage records are also kept in a compressed internal archive for up to 400 days. Our traffic logs and application logs are not archived. The archive is used only to rebuild those statistics if their stored copy is damaged. It holds the same details as the entries described above: IP addresses in paths are replaced by a placeholder, and visitor statistics entries keep the day’s visit code, which cannot be traced back to an address after that day.
- Backups: Our backups contain copies of the records in this section, including account data. Daily database backups are kept for 14 days and weekly file backups for up to four weeks, then deleted, so a deleted record can remain in a backup until that backup is deleted.
- Bulk reports: Stored for 30 days, then automatically deleted.
- Account data: Retained while your account is active. You may request account deletion at any time. The API usage records described under “API usage” are currently kept after deletion, linked only to internal IDs. We have decided to erase them, including their copy in our statistics archive, when an account is deleted. Our platform cannot yet remove one account’s usage records, so we will start doing this once it can, and update this policy then.
7. Your Rights
You have the right to:
- Access the personal data we hold about you
- Request correction of inaccurate data
- Request deletion of your account and associated data (for now, except the API usage records; see “Account data” above)
- Object to processing of your data
To exercise any of these rights, contact us through our contact page.
8. Children’s Privacy
The Service is not directed at children under the age of 13. We do not knowingly collect personal information from children. If you believe a child has provided us with personal data, please contact us and we will delete it.
9. Changes to This Policy
We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated “Last updated” date. Your continued use of the Service after changes are posted constitutes acceptance of the updated policy.
10. Contact
If you have questions about this Privacy Policy, contact us through our contact page.