Privacy Policy

1. Scope and controller

This policy applies to WhatIsMyIP.live, its public pages and tools, developer API, embeddable IP widget, account dashboards, browser extensions, and any future official mobile or desktop apps that link to this policy. Privacy enquiries and rights requests can be submitted through the contact page.

2. Technical data processed automatically

When a service is requested, servers normally receive the public IP address, date and time, requested URL, HTTP method, referrer when supplied, user-agent, language, security headers, response status, duration and a request identifier. Limited logs are used to deliver pages, prevent abuse, diagnose errors, protect accounts and keep the service reliable.

3. IP, DNS, WHOIS and network lookups

Values you enter—such as an IP address, domain, hostname, ASN or network prefix—are processed to return the requested result. Successful explicit lookups may be cached or stored as public technical report pages, history, evidence or aggregate network data. An IP address can indicate an approximate country or city, but it does not by itself prove a person’s identity or precise home address.

4. Accounts, API keys and device authentication

If you create an account, the service may process your name, email address, password hash, verification records, security events, API keys, usage totals, plan information and support messages. Browser or app alerts may use a random revocable device token. Tokens are authentication information; they are not passwords and can be revoked from the account or service.

5. Browser extension, widgets and future apps

The official browser extension uses first-party access to WhatIsMyIP.live to observe the current public IPv4 or IPv6 address, approximate country or city, ISP and optional proxy or VPN status, and to provide IP-change alerts. It may use browser storage, alarms and notifications. It does not request browsing history, website content, clipboard, camera, microphone or precise GPS access. Future apps will follow this policy and will request additional permissions only when a clearly described feature needs them.

6. Cookies and local storage

Essential cookies or local storage may support security, CSRF protection, language, theme, sessions, consent choices, saved tool preferences and IP-history features. Non-essential analytics or advertising storage should be used only when allowed by the consent configuration and applicable law. Blocking essential storage may prevent login or form features from working.

7. Analytics, performance and advertising

The service may measure page groups, referrals, device class, language, approximate country, performance timings and tool usage in aggregate or pseudonymous form. Known crawlers, APIs, staff pages and sensitive routes are excluded where practical. Advertising and analytics providers may set their own identifiers only when enabled; their processing is governed by their policies and your consent choices.

8. Comments, corrections, contact and user content

When you submit a comment, IP-location correction, contact request or investigation feedback, the submitted text and related technical anti-abuse data may be stored for moderation and response. Approved comments can become public. Pending, rejected, spam or repetitive comments are not intended for public display, and links in public comments are treated as user-generated and nofollowed.

9. Payments and developer services

Paid API or subscription features may require billing details. Payment card information is normally handled by the selected payment provider rather than stored directly by WhatIsMyIP.live. The service may retain transaction references, plan, status, invoice information and limited fraud-prevention records needed to manage the account and comply with law.

10. Sources, processors and disclosure

WhatIsMyIP.live relies mainly on locally processed public or open network datasets, caches and first-party intelligence. Some functions may contact authoritative registries, DNS or RDAP services, hosting or security providers, email providers, payment processors, analytics or advertising services. Data is disclosed only as needed to operate, secure, support or legally protect the service; personal data is not sold.

11. Retention and public technical records

Retention depends on purpose. Security and error evidence may be kept long enough to investigate incidents; account and billing records may be kept while the account is active and as legally required; expired tokens and old operational samples are pruned. Public IP, DNS, WHOIS, reputation or network pages may remain available while they are technically useful, but inaccurate records can be corrected and low-quality or private-address pages may be excluded from search indexing.

12. Legal bases and your choices

Depending on location and feature, processing may rely on contract, legitimate interests in operating and securing the service, consent for optional storage or notifications, and legal obligations. You may ask for access, correction, deletion, restriction or objection where applicable, withdraw consent, disable notifications, clear local storage, revoke device tokens or close an account. Some technical logs or public network facts may need to be retained for security, legal or integrity reasons.

13. Security, transfers, children and changes

Reasonable technical and organisational safeguards are used, including encrypted transport, access controls, hashed credentials, rate limits, auditing and protected administrative tools, but no internet system can guarantee absolute security. Providers may process data in other countries with appropriate safeguards. The service is not directed to children under 13. Material policy changes will be published here with a new update date.

Contact us about privacy or a data correction