Privacy Policy

Last updated: October 21, 2026

Brand Media, Inc. operates IPLocation.net. This Privacy Policy covers our websites and related services, including www.iplocation.net, tools.iplocation.net, api.iplocation.net, hosted applications, account features, and IP Lookup and Tools for iOS and Android. Some sections apply only when you use the feature described.

Mobile release status: The current mobile build provides IP lookups and network tools without an account. Mobile advertising, paid Pro checkout, purchase restoration, saved history/favorites, report exports, and side-by-side comparisons are planned features, not active data practices merely because they appear in a preview. We will update this policy and provide required notices and choices before introducing new collection or uses.

1. Information We Collect

• Contact and account information: information you provide through accounts, support, forms, or newsletters, such as your name, email, company, profile settings, and correspondence. Do not submit passwords or confidential information in tool inputs or support messages.
• Connection and technical information: public IPv4/IPv6 address, approximate IP-based location, ISP, ASN, browser or app platform, app version, request headers, timestamps, and operational/security diagnostics. IP-based location is an estimate, not GPS location or a verified street address.
• Tool inputs: IP addresses, domains, URLs, email headers, and other values you submit. Inputs may identify you or another person. Only submit information you are authorized to use.
• Mobile installation and session information: the app stores a randomly generated installation identifier on your device and sends it with platform and app version to our API. Our mobile session database stores a keyed hash of that identifier, a hash of the session token, permitted access scopes, and session timestamps. Short-lived access tokens are held in app memory. Network infrastructure and security logs may separately record public IP addresses and request information.
• Payments: website order, invoice, plan, and payment-status records when you buy a service. When mobile Pro purchases become available, Apple or Google will process payment. Verification may involve the store, product and transaction identifiers, purchase tokens or signed transaction evidence, dates, and purchase/refund status. These are purchase records, not your payment-card details.
• Cookies and similar technologies: website sessions, preferences, analytics, and advertising technologies as described below. Mobile app preferences use device storage rather than browser cookies.
• Connected Google services: only the Google data needed for a feature you authorize, as described in Sections 5 and 6.

2. Mobile Network Information and Local Processing

The My IP screen contacts api.iplocation.net separately over IPv4 and IPv6 where available. The server receives the public address used for each connection. The app also reads private/local interface addresses on the device, including interfaces added by a VPN where exposed by the operating system. The current app displays those private addresses locally and does not send the interface list or private addresses to our API automatically. If you explicitly submit an address to a lookup tool, that input is transmitted for the requested lookup.

The mobile app does not access your contacts, photos, or advertising identifier. The optional Device Location tool requests a single foreground location fix only after an explanation and your operating system's permission. Depending on your device settings, operating system location services may use GPS, Wi-Fi, or cellular information under their own privacy settings and practices. Approximate location permission is respected; precise location is not required to use the rest of the app. The app keeps coordinates, reported accuracy, and location timestamps in screen memory; it does not send them to our API, lookup providers, or advertising providers, or save them as history. The result is cleared when the app enters the background or you select Clear. Selecting Copy writes coordinates to the operating system clipboard. Open in Maps separately asks you to confirm sharing coordinates with Apple Maps on iOS or Google Maps on Android, whose privacy practices then apply. Clear removes the in-app result, not copies already placed on the clipboard or shared with Maps, and does not revoke operating-system permission. You can change permission in device settings. There is no background location tracking or reverse geocoding in this feature. Subnet calculations run locally. The basic DNS lookup uses the device's configured resolver. Advanced DNS and reverse DNS (PTR) queries are sent directly from your device to the selected Google Public DNS or Cloudflare DNS-over-HTTPS service. That resolver receives the query name or reverse IP query and your public IP address; its privacy policy and request-retention practices apply. Simulators and VPNs may report virtual or shared interfaces. Device permissions or network restrictions may limit the information available.

Other device-based diagnostics: WHOIS/RDAP queries go directly from your device through RDAP.org to the responsible registration service. RDAP.org and the registry receive the queried domain, IP address, or ASN and your public IP address. HTTP header and SSL/TLS certificate checks directly contact the site you enter; that site receives your public IP and relevant request or connection information. These tools support HTTPS/TLS on port 443. The header checker does not send stored browser cookies or app session credentials; it may use GET when HEAD is unsupported. Certificate inspection may retrieve an untrusted certificate solely to display its details and report failed validation.

Inputs and results for these device-based diagnostic tools are held in the current screen's memory, are not sent to api.iplocation.net, and are not automatically saved as history or shared with other people. The external resolver, registry, or destination site may keep its own records under its policies. The selected resolver and query source are identified within each tool before you run a check.

3. How We Use Information

We use information to deliver requested results, operate and secure services, prevent abuse, enforce usage limits, manage accounts and purchases where offered, respond to support, measure website performance, debug problems, and meet legal obligations. We do not require a mobile account for the current basic tools. Where privacy laws require a lawful basis, we rely as appropriate on providing a requested service, legitimate interests in security and operation, legal obligations, or consent. You may withdraw consent without affecting earlier lawful processing.

4. Lookup Providers and Other Recipients

Our API sends the IP address being looked up to the selected geolocation provider to obtain results. The supported mobile providers currently include IP2Location.io, IPinfo, DB-IP, IPAPI.co, IPapi.is, ipapi.com, IPData, IPGeolocation.io, and Ipregistry; available providers depend on configuration. Opening an additional provider requests that provider's result. The queried address can be your public IP or another address you enter. Providers receive requests from our servers; merely offering a comparison does not require us to send them your mobile installation identifier. These providers process requests under their own applicable terms and privacy policies.

We also disclose information as needed to hosting, network/CDN, database, analytics, advertising, email, payment, security, and support providers. A provider may receive connection information directly when your device requests a hosted resource. For example, country flags load from cdn.iplocation.net. We may disclose information to comply with law, protect rights or safety, investigate fraud, or complete a business transfer subject to applicable safeguards. Provider-held copies may have different retention periods.

5. Google Search Console API Data

Some IPLocation.net developer or site-audit features may allow you to connect your Google account so that we can access Google Search Console data for properties you are authorized to view. We use OAuth 2.0 to request permission from Google before accessing this data.

When available, our Google Search Console integration is intended to help users view, audit, diagnose, or improve their own verified websites and related IPLocation.net tools. Depending on the feature you use and the permission you approve, we may request the following scope:

• https://www.googleapis.com/auth/webmasters.readonly - read-only access to Search Console properties and reports.

We may access Search Console property lists, verified site URLs, search analytics metrics such as clicks, impressions, click-through rate, average position, query/page/device/country/date dimensions, sitemap information, and URL inspection results when the connected feature requires it.

We use Google Search Console data only to provide or improve user-facing features that are visible in IPLocation.net, such as selecting a verified property, showing search performance, auditing URLs, checking indexing status, reviewing sitemap data, or helping you diagnose SEO and site visibility issues. We do not transfer Google user data to third parties except as necessary to provide the feature you requested, comply with law, protect security, or complete a merger, acquisition, or sale of assets after required notice or consent.

We do not allow employees, contractors, or service providers to read Google user data unless it is necessary to provide support you request, investigate abuse or security issues, comply with law, or operate and improve the authorized feature in an aggregated or de-identified form. Our use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

6. OAuth Tokens And Revocation

When you authorize a Google-connected feature, Google may provide access tokens and refresh tokens. We store tokens securely and use them only to access the Google APIs and scopes you approved. You can revoke access at any time from your Google Account permissions page or by contacting us. After revocation, IPLocation.net will no longer be able to retrieve new Google Search Console data for that connection.

7. Storage, Security, and International Processing

We use HTTPS, access controls, credential protections, and other reasonable safeguards. No system is completely secure. Our infrastructure and service providers may process information outside your state or country. Where required, appropriate transfer safeguards and applicable rights apply; contact us for details relevant to your information.

8. Retention and Deletion

• Mobile sessions: access tokens normally expire after 15 minutes. Expiration stops access but does not itself erase the database record. Session records are eligible for our maintenance pruning process after they have been expired for at least seven days; actual removal depends on maintenance execution.
• Lookup caches: mobile comparison results are normally cached for five minutes to reduce repeated provider requests. Cache expiry is separate from security logs and provider records and can vary with configuration.
• Operational, account, and support records: retained for the period needed to provide the service, investigate abuse, resolve the request or dispute, and meet legal obligations. The period depends on the record's purpose, sensitivity, account status, and applicable requirements.
• Purchase records, once enabled: retained as needed to verify continuing Pro access, restore purchases, handle refunds/disputes, and meet accounting or legal obligations. Deleting app data does not cancel or erase store-held purchase records.
• Device storage: clearing app data or uninstalling normally removes app-held preferences, subject to operating-system backup and restore settings. Any future saved history/favorites feature will explain whether data stays on-device or is synchronized and provide applicable deletion controls. Sharing/exporting a report creates copies outside our control.
• Google data: retained only as needed for the connected feature unless you disconnect or request deletion sooner, subject to applicable legal exceptions. Backups may retain restricted copies until their normal replacement cycle.

To request deletion or ask about retention, use our privacy rights request form or email [email protected]. We may need proportionate information to locate your records and verify the request. We may retain information required for security, transactions, disputes, or law and will explain applicable exceptions.

9. Website Advertising, Cookies, and Mobile Advertising

Our websites display advertising and use analytics and similar technologies. Advertising partners may receive IP address, browser/device information, page context, cookie or other identifiers, and ad interactions to deliver, measure, secure, or personalize advertising where permitted. Their use and your choices depend on the partner, region, and consent settings. Browser cookie controls do not necessarily change mobile SDK settings.

We do not sell personal information for money. Certain disclosures for targeted advertising may qualify as a sale or sharing under applicable privacy laws even without payment. Where applicable, you may opt out through available privacy/consent controls or our privacy rights request form. We honor applicable browser opt-out preference signals where required by law. Our advertising disclosures do not authorize use of connected Google user data for advertising.

Mobile advertising is not active in the current build. Before enabling an ad SDK, we will identify the relevant partners and data practices here and provide required consent and privacy controls. If an implementation involves tracking that requires Apple's App Tracking Transparency permission, we will request that permission before tracking. Pro is intended to remove in-app advertisements; it does not eliminate network requests needed for lookups, security, or purchase verification.

10. Your Choices and Rights

Depending on where you live, you may have rights to access, correct, delete, or obtain a portable copy of your information, object to or restrict processing, withdraw consent, or opt out of sale/sharing or targeted advertising. We will not unlawfully discriminate against you for exercising a right. You may use an authorized agent where permitted and may appeal a denied request where applicable by replying to our response. You may also complain to your local data-protection authority.

Use the privacy rights request form or contact us below. You may unsubscribe from marketing emails using their unsubscribe link and disconnect Google access through your Google Account permissions. Where a service permits account creation, contact us or use that service's available deletion controls; the current mobile app does not create a user account. Store purchases are managed through Apple or Google.

11. Children's Privacy

Our services are not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided personal information, contact us so we can investigate and take appropriate action. Additional local age or consent requirements may apply.

12. Changes and Contact

We will update the date above when this policy changes and provide additional notice or consent where required for material changes. New features do not override permissions or privacy choices required by law.

For questions or privacy requests, contact Brand Media, Inc. at [email protected], our Contact Us page, or our privacy rights request form.