Privacy Policy

This section applies to Domain Details - RDAP, WHOIS & Marketplace Search for Chrome (item ID ceoknmdcolcpjnadklohkhjgoghnafmm) and the equivalent Domain Details extensions for Edge, Firefox, Safari, and other supported browsers.

8.1 Activation and Permissions

The extension activates only after you open its toolbar popup or choose its context-menu command. It does not run an always-on content script. Its permissions are used as follows:

• activeTab: read the active tab URL after you open the extension so it can identify a domain candidate
• scripting: read limited page metadata such as a canonical URL, Open Graph URL, heading, or title only when a marketplace URL does not identify the offered domain
• contextMenus: provide an explicit right-click domain lookup command
• storage: save preferences, identifiers, a short-lived access token, and observed lookup summaries in browser-managed extension storage

8.2 Data Collection

Depending on the feature you choose, the extension collects or processes:

• Requested domain or search term: the registrable domain detected from the active tab, selected through the context menu, or entered manually, but only when you request a registration or marketplace lookup
• Limited page metadata: canonical URL, Open Graph URL, heading, and title may be read locally to identify a domain on a marketplace page; the raw metadata is not sent to Domain Details or analytics
• Lookup results: public RDAP/WHOIS registration data and marketplace result data needed to display the requested response
• Local history: the domain, lookup time, lookup method, availability, and changed summary fields such as registrar, dates, status, nameservers, and DNSSEC
• Pseudonymous technical identifiers: a random installation analytics ID when analytics are enabled, a separate random request/rate-limit ID, and a short-lived signed gateway token
• Optional usage analytics: browser and extension version, feature used, general detection method, success or failure, coarse result counts, duration, and analytics preference changes
• Network and security metadata: service infrastructure and processors may temporarily process IP address, user agent, request time, and Cloudflare request identifiers for delivery, security, rate limiting, and troubleshooting

8.3 How We Handle and Use Extension Data

• A registration lookup sends the requested domain over HTTPS in a POST body to ext.domaindetails.com. The Worker sends that domain to the relevant public RDAP service or WHOIS server and returns the response to the extension.
• A marketplace search sends the requested domain over HTTPS to api.domaindetails.com. Our service queries supported marketplace providers and returns the result summary.
• The random request ID and signed gateway token are used to assign request capacity, prevent abuse, and keep extension traffic separate from general public traffic. They are not linked to a Domain Details account.
• If analytics are enabled, allowlisted events are sent to PostHog EU through our first-party proxy at f.domaindetails.com to measure feature reliability and improve the extension.

8.4 Storage and Retention

• On your device: browser-managed extension storage keeps up to 20 changed summary snapshots per domain, analytics preference and onboarding state, the pseudonymous identifiers, and any unexpired gateway token. Domain history remains until you clear it for that domain or remove the extension; removing the extension deletes its browser-managed storage.
• Registration lookups: the ext.domaindetails.com Worker has no KV, D1, analytics dataset, or application database and does not store lookup results. Its rate-limit state is ephemeral. Infrastructure security logs may be retained temporarily by Cloudflare under its operational retention practices.
• Marketplace searches: Domain Details stores the requested domain, TLD, result summary, timestamp, traffic classification, and a pseudonymous hashed client classification in its application database for service analytics, reliability, and abuse prevention. These records are not linked to a Domain Details account and are retained only while needed for those purposes, after which they are deleted or aggregated.
• Usage analytics: PostHog stores the allowlisted event data under our configured analytics retention controls. Turning analytics off stops future extension events; it does not automatically delete events already received.

8.5 Data Sharing

We disclose extension data only as needed to provide, secure, and improve the requested features:

• Cloudflare processes requests, security metadata, and rate-limit state for our first-party endpoints.
• Public RDAP operators and WHOIS servers receive the requested domain to provide registration data.
• Supported marketplace providers receive the requested domain as necessary to search their listings.
• PostHog receives the allowlisted pseudonymous usage events only when analytics are enabled.

We do not sell extension data, use it for targeted advertising, or disclose it to data brokers. Service providers process data on our behalf or as necessary to answer the lookup you requested.

8.6 Data We Do Not Collect or Share

The extension does not collect your complete browsing history, run on every page in the background, or transmit complete source-page URLs, page titles, page contents, raw locally observed history, authentication information, financial information, personal communications, or precise location. Extension analytics never include searched domains, marketplace provider names, raw WHOIS/RDAP data, registration contact data, or Domain Details account identifiers. PostHog person profiles are disabled for extension events.

8.7 Your Controls

Before any optional analytics event is sent, the first-run screen presents the analytics choice. It is enabled by default on supported stores, but you can turn it off before continuing or later in the popup's Privacy control. You can clear locally observed history for each domain in the popup. To request access to or deletion of server-held data where applicable, email privacy@domaindetails.com; include the relevant domain, approximate request date, and browser extension so we can locate the record without asking for unrelated information.