Privacy Policy

Last updated: May 7, 2026

1. What We Collect

IP Network Metadata: IPDebrief collects and displays publicly available network metadata about IP addresses, including:

• RDAP/WHOIS registration data (organization, network name, CIDR block, abuse contacts)
• DNS records (PTR hostnames, forward confirmation)
• Geolocation data (country, region, city — derived from public geolocation databases)
• Open port and service detection results
• TLS certificate metadata (subject, issuer, SANs — public certificate transparency data)
• Threat intelligence indicators from publicly available feeds
• Network role classification (cloud, CDN, VPN, hosting, residential, mobile)

All of this data is publicly available network infrastructure metadata. We do not collect, store, or process personal data such as names, email addresses, browsing history, or device identifiers of individuals visiting this site.

2. IP Addresses Are Not Personal Data

An IP address identifies a network endpoint, not an individual. IP addresses are routinely shared (NAT), reassigned by ISPs, and used by multiple people simultaneously. The information displayed on IPDebrief describes network infrastructure, not people.

3. Data Sources

All data is collected from publicly accessible sources that permit commercial use, including RDAP registries, public DNS, certificate transparency logs, and open threat intelligence feeds. We maintain compliance records for every data source we ingest.

4. Cookies & Tracking

IPDebrief does not use cookies, tracking pixels, analytics scripts, or any form of user tracking. We do not use advertising. There are no third-party scripts loaded on any page.

5. Data Retention

Network observations are retained indefinitely as historical records. Geolocation coordinates for residential and mobile IP addresses are redacted from public display.

6. Data Review Requests

If you believe information displayed about a network you control is inaccurate, or if you have concerns about data displayed on this platform, contact us at [email protected]. We will review all requests promptly.

7. API Usage

API requests are rate-limited and logged for abuse prevention. We log the requesting IP address and request timestamp. We do not require registration for the free tier and do not collect personal information from API users.

8. Security

All data is stored in PostgreSQL with encrypted connections. Administrative access requires mutual TLS (mTLS) client certificate authentication. There are no shared passwords or API keys.

9. Changes

We may update this policy as needed. Material changes will be noted with an updated revision date at the top of this page.

10. Contact

For privacy-related inquiries: [email protected]