Skip to content

Terms of Service

Last updated: November 13, 2026

1. Acceptance of Terms

By accessing or using My IP Help (“the Service”), you agree to be bound by these Terms of Service. If you do not agree to these terms, do not use the Service. We may update these terms at any time, and your continued use of the Service after changes are posted constitutes acceptance of the updated terms.

2. Description of Service

My IP Help provides free and paid IP address tools including IP geolocation lookup, bulk IP lookup, blacklist checking, an IP data API, and related network intelligence features. The Service is provided “as is” and is intended for informational purposes only.

3. Acceptable Use

You agree not to use the Service to:

  • Stalk, harass, or track individuals using IP geolocation data
  • Conduct any illegal activity or violate any applicable laws or regulations
  • Attempt to circumvent rate limits, access controls, or security measures
  • Scrape, crawl, or automatically extract data from the Service beyond normal use
  • Interfere with or disrupt the Service or its infrastructure
  • Resell, redistribute, or sublicense data obtained from the Service without authorization

We reserve the right to suspend or terminate access for users who violate these terms.

4. Accounts

Some features require creating an account. You are responsible for maintaining the confidentiality of your account credentials and for all activity that occurs under your account. You must provide accurate information when creating an account and notify us immediately of any unauthorized use.

5. Purchases & Refunds

Bulk IP reports are one-time purchases. Pricing is displayed at the time of purchase and depends on the number of IP addresses in the report. Purchased reports are accessible for 30 days.

Because reports are generated and delivered immediately, refunds are generally not available once a report has been generated. If you experience a technical issue that prevents you from accessing your report, contact us at contact page and we will work to resolve the issue.

API subscriptions are covered in Section 6: they are billed monthly and can be canceled at any time. Partial billing periods and unused lookups are not refunded, except where the law requires it; billing errors are refunded.

6. API

This section applies to the IP data API run by My IP Help (myiphelp.com): the endpoints under /api/v1/ipdata/, our MCP server at /mcp/v1 (which lets AI assistants call the API), and the API keys, plans and usage you manage under Account > API. The MCP server is part of the API: its tools make API requests with your key, so they share your plan’s lookups, request rate, bulk size and fields, and everything in this section applies to them. The rest of these Terms apply to the API as well. Where this section and another section differ on API use, this section applies.

Plans and limits

PlanPrice (USD)Lookups per monthRequests per key: burst, then per minuteIPs per bulk requestAPI keys
StarterFree1,00030, then 10 per minute201
Pro$29 per month100,000180, then 60 per minute1003
Business$79 per month500,000600, then 200 per minute50010
Enterprise$199 per month2,000,0001,500, then 500 per minute1,00025
  • Request rate. Each key can send up to its plan’s burst of requests at once. Unused capacity refills at the plan’s per-minute rate. For example, a Starter key can send 30 requests at once and then 10 a minute, and a Starter key that has used its whole burst has all 30 requests again after 3 minutes without requests.
  • What counts as a lookup. Each lookup of an IP address that returns data counts as one lookup, including a lookup of your own address. Each IP address in a bulk request that returns data counts as one lookup; private, reserved and unknown addresses in it do not. A request that returns an error, such as an invalid or private IP address or an address with no data, does not count. A bulk request counts as one request toward your request rate. Through the MCP server, a bulk_lookup call is split into bulk requests of up to your plan’s bulk size, and each one counts as one request. A bulk request with more addresses than your month has left is refused whole (HTTP 429, QUOTA_EXCEEDED) and nothing in it is counted.
  • Your lookup month. Your monthly lookups reset at the start of each lookup month. On Starter, the lookup month is the calendar month. On a paid plan, it starts each month on the day of the month your subscription started, counting the free trial. This can differ from your billing period, which starts when the trial ends.
  • Reaching a limit. When you reach your monthly lookups, the API returns an error (HTTP 429, QUOTA_EXCEEDED) until your next lookup month starts or you move to a larger plan. If you move to a smaller plan after using more lookups than it allows, you get the same error until your next lookup month. We do not charge for extra lookups and there is no overage billing. If you send requests with one key faster than your plan’s request rate allows, the API returns HTTP 429 (RATE_LIMITED) with a Retry-After header. The X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset headers show your monthly lookups, not the request rate.
  • Fields by plan. Starter returns location, network and the risk score with its main reason. Pro adds postal code, security flags (VPN, proxy, Tor, datacenter, verified bot and blocklist listings), cloud provider, country details, IP allocation, the summary and the full breakdown of the risk score (every reason behind it, with its points). Business and Enterprise add country sanctions and risk indicators. Fields your plan does not include are left out of the response.
  • Billing period. Paid plans are billed monthly. Annual billing is not offered.

We may change plans, prices, limits and the fields each plan includes. If we raise the price of a paid plan you are subscribed to, or lower its limits (lookups per month, the request rate or burst, IP addresses per bulk request or the number of API keys), we will email you at least 30 days before the change. The change takes effect at your first renewal after that notice period. Changes to fields are covered under “Availability and changes to the API” below.

Free trial, billing and cancellation

  • Free trial. Pro, Business and Enterprise start with a 5-day free trial. Each account gets one free trial: if you have already had one on any paid plan, a new subscription starts without a trial and is charged right away. A payment card is needed to start the trial. If you do not cancel before the trial ends, the subscription begins and your card is charged for the first month. If you cancel during the trial, you keep the plan until the trial ends and are not charged.
  • Payments. Paid plans are monthly subscriptions. Stripe processes the payments, and we do not receive or store your full card number. The subscription renews each month until you cancel it. Invoices are available under Account > Billing.
  • Changing plans. You can switch between paid plans at any time, and the new plan applies right away. Moving to a larger plan adds a prorated charge for the rest of the billing period to your next invoice. Moving to a smaller plan adds a prorated credit to your next invoice. Credits are used against later invoices and are not paid out.
  • Canceling. You can cancel at any time from Account > Billing. You keep your paid plan until the end of the billing period you have paid for, and you can resume the subscription until then. After that, your account moves to Starter, with Starter’s limits and fields.
  • Failed payments. If a renewal payment fails, your account gets Starter’s limits and fields until the payment goes through or the subscription ends.
  • Refunds. You can test the API on Starter and during the free trial before you pay, so we do not refund part of a billing period or unused lookups, except where the law requires it. If you were charged twice or charged the wrong amount, contact us and we will refund the error.

API keys

  • Each key starts with mih_live_ and returns real data on every plan, including Starter. A key is shown once. We store only a hash of it, so we cannot show it to you again. If you lose a key, revoke it and create a new one.
  • You can restrict a key to a list of IP addresses. Requests from any other address are refused.
  • Keep your keys secret and use them only on servers run by you or by hosting providers working for you, or in an AI assistant’s MCP settings on your own device. Do not put them in web pages or apps that other people can inspect. You are responsible for all use of your keys. If a key may have leaked, revoke it under Account > API right away.
  • Your keys are for you and the people who work for you. Do not share them with anyone else, or sell or give away access to the API through them.

Acceptable use of the API

The Acceptable Use rules in Section 3 apply to the API. In addition, you agree not to:

  • Use API data to identify or locate a specific person, household or street address, or to track or profile individuals
  • Use API data as a factor in decisions about a person’s eligibility for credit, insurance, employment or a government license or benefit
  • Make decisions with legal or similarly serious effects on a person based only on a risk score or flag, without a way for that person to be reviewed by a human
  • Get around your plan’s limits, for example by opening several free accounts, spreading traffic across accounts or starting repeated free trials
  • Query the API systematically to copy, rebuild or publish the underlying databases or lists
  • Resell API results, or offer them to others as your own IP data, geolocation or threat-data product or API

You may store API results in your own systems, such as logs, fraud reviews and security records. You may also show API results to your own users and use them inside your own products and services, with the credits listed below. That is the authorization Section 3 refers to. You may not sell or license the results as data in their own right.

Data sources and attribution

API results combine third-party data with our own processing. Several of those sources set conditions that pass on to you when you use their data. If you show API results to other people or include them in a product or service, you must keep these credits with them:

  • MaxMind GeoLite2 (location and network data). Credit: “Free IP geolocation data provided by MaxMind, creator of GeoIP®.” or “This product includes free IP geolocation data provided by MaxMind, creator of GeoIP®.” Where: wherever your users can see the data (pages, dashboards, alerts), in any report or post that relied on it, and in the documentation of a product or service you distribute it with. Restrictions: MaxMind’s terms forbid using the data to identify or locate a specific person, household or street address, and for the decisions about credit, insurance, employment and government licenses listed above.
  • DB-IP Lite (location data, CC BY 4.0): a link to DB-IP on pages that show the results, for example “IP Geolocation by DB-IP“.
  • Spamhaus DROP (blocklist listings): where you show a DROP listing, keep the credit “© The Spamhaus Project” with it. Do not use the Spamhaus name in marketing, promotional or other commercial materials, or suggest that Spamhaus endorses your product.
  • IP2Proxy LITE (proxy detection, from IP2Location): where you show the proxy signal, credit IP2Location in its required wording: “[your product] uses the IP2Proxy LITE database for proxy and VPN detection“.
  • Country details and indicators: currency, languages, capital, calling code and other country details from the mledoze/countries dataset (ODbL 1.0), GDP per capita and internet use from the World Bank (CC BY 4.0), and the Corruption Perceptions Index from Transparency International (CC BY-ND 4.0). Credit the source when you show these values, and do not present a changed CPI score as Transparency International’s.

Lookup responses carry the credits of the sources behind each answer in meta.attribution and in an X-Attribution header: MaxMind and DB-IP always, Spamhaus when the answer includes a Spamhaus DROP match, and IP2Proxy LITE when its proxy signal is in the answer. MCP tool results carry the same credits in attribution and _meta.attribution. If you or your AI assistant show MCP results to other people, you must show these credits with them. The risk score and security flags also draw on the Tor Project’s exit list, Spamhaus DROP, IP2Proxy LITE, public proxy lists, X4BNet, IPtoASN, Apple’s iCloud Private Relay ranges and the IP ranges that bot operators publish. API results do not use lists that contain DShield data (FireHOL levels 1 and 2, and IPsum).

Accuracy

Section 7 (Data Accuracy Disclaimer) applies to every API result.

IP geolocation is approximate. The country is the most dependable part: in our 2026 test of 1,000,000 random IPv4 addresses, MaxMind GeoLite2 and DB-IP Lite named the same country for 96.2% of them. That figure measures how often the two databases agree, not how often either is correct. Region and city results are less reliable, and VPNs, proxies, mobile networks and corporate gateways can place an address far from the person using it.

The risk score and security flags are automated estimates built from public lists. They can be wrong in both directions: a listed address may be safe, and an unlisted one may not be. The sanctions fields describe the country an IP address is located in, from a list of sanctioned countries we maintain. They are not a screening of any person or organization and are not enough on their own for sanctions compliance.

Availability and changes to the API

We do not offer a service level agreement or an uptime guarantee for any plan, free or paid. The API may be slow or unavailable at times, for example during maintenance, data updates or problems with our hosting or data providers.

We may add fields and endpoints at any time without notice, so your code should ignore fields it does not recognize. Before a change that would break existing requests to /api/v1/ipdata/, such as removing or renaming a field or endpoint, we will give at least 30 days’ notice in the API documentation and by email to holders of active API keys. We may make such a change with shorter notice, or none, when it is needed urgently for security or legal reasons.

Usage data we keep

For each API key, we keep its name, the first characters of the key, a hash of the full key, any IP allowlist you set, and when the key was last used. These records are kept while your account exists and are deleted with it. We also count your lookups per key per day so we can apply your plan’s limits and show your usage, and for each API request counted toward your usage we keep a record of its time, the key’s ID and the number of lookups, with no IP addresses. We keep the daily counts as billing history with no time limit and each request’s record for 400 days. Both currently stay after your account is closed, linked only to internal account and key IDs. We have decided to erase them, including their archived copy, when an account is closed. Our platform cannot yet remove one account’s usage records, so we will start doing this once it can, and update these Terms then. Deleted records can remain in our backups for up to four weeks; see our Privacy Policy. To close your account, contact us.

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. 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. Neither the failed-request entries nor the daily failure counts are linked to your key or account. The individual entries of these statistics and of the usage records above are also kept in a compressed internal archive for up to 400 days, used only to rebuild them if their stored copy is damaged.

Lookup results are cached by IP address for up to a week to keep the API fast, and the cache is not linked to your account. Our hosting and CDN providers’ logs, our application logs (rotated daily and kept for up to 30 days) and our error reports may contain the request URL and the IP address you called from. See our Privacy Policy for how those are handled.

Suspension and ending API access

We may revoke API keys, suspend API access or close an account if you break these Terms, do not pay, or send traffic that harms the Service or other users. Where it is reasonable, we will tell you first and give you a chance to fix the problem. You can stop using the API at any time by canceling your subscription and revoking your keys.

Liability

Sections 9 (Limitation of Liability) and 10 (Disclaimer of Warranties) apply in full to the API, including the limit on our total liability.

Questions about the API, your plan or a key that may have leaked can be sent through our contact page.

7. Data Accuracy Disclaimer

IP geolocation and network data are derived from third-party databases and are approximate by nature. We do not guarantee the accuracy, completeness, or reliability of any data provided through the Service. Geolocation results represent the approximate location associated with an IP address, not the precise physical location of a device or person.

You should not rely on this data for life-safety, legal proceedings, law enforcement, or any purpose requiring exact precision. See our Data Sources & Accuracy page for information about data sources and known limitations.

8. Intellectual Property

The Service, including its design, text, graphics, and code, is owned by My IP Help and protected by applicable intellectual property laws. IP geolocation data is sourced from third-party providers including MaxMind and DB-IP, and is subject to their respective licenses.

9. Limitation of Liability

To the maximum extent permitted by law, My IP Help and its operators shall not be liable for any indirect, incidental, special, consequential, or punitive damages, including but not limited to loss of profits, data, or business opportunities, arising from your use of or inability to use the Service.

Our total liability for any claim arising from the Service shall not exceed the amount you paid to us in the twelve (12) months preceding the claim.

10. Disclaimer of Warranties

The Service is provided “as is” and “as available” without warranties of any kind, whether express or implied, including but not limited to implied warranties of merchantability, fitness for a particular purpose, and non-infringement. We do not warrant that the Service will be uninterrupted, error-free, or secure.

11. Third-Party Data & Services

The Service incorporates data from third-party sources. We are not responsible for the accuracy or availability of third-party data. Use of third-party data is subject to each provider’s terms and licenses. The Service may also link to third-party websites, which are not under our control.

12. Termination

We may suspend or terminate your access to the Service at any time, with or without notice, for conduct that we believe violates these Terms or is harmful to other users, us, or third parties. Upon termination, your right to use the Service ceases immediately.

13. Governing Law

These Terms shall be governed by and construed in accordance with applicable laws, without regard to conflict of law principles. Any disputes arising from these Terms or the Service shall be resolved in the appropriate courts of the jurisdiction in which My IP Help operates.

14. Contact

If you have questions about these Terms, contact us at contact page.