Privacy
What Beta Directory collects, why it is collected, and the choices available to visitors and listed website owners.
- Published by
- Beta Directory
- Updated
- August 27, 2026
Scope
This notice covers the Beta Directory website and its domain-profile collection workflow. It does not cover a listed website or an external source you open from a profile. Those services publish their own privacy terms.
Public website records
The directory stores information connected to public domains rather than building private visitor profiles. Records can include public DNS and RDAP responses, outgoing page links, requested network hosts, IP and ASN observations, HTTP and TLS results, visible technology signals, popularity positions or ranges, screenshots, citations, and observation times. Some registry responses can contain public contact data supplied by a registrant, registrar, or registry.
The purpose is to publish a dated, understandable record, support corrections, and avoid repeatedly requesting unchanged information from upstream services. Data is not collected to score individuals or sell behavioral advertising.
Visitor data
You can browse without an account. The site stores a light or dark theme preference in local browser storage. Hosting and security infrastructure processes request data such as IP address, user agent, requested URL, timestamp, network information, and security signals to deliver pages, enforce rate limits, prevent abuse, and diagnose failures.
Beta Directory does not currently use third-party advertising cookies, sell personal information, or build visitor advertising profiles. If analytics or optional cookies are introduced, this notice and any required consent controls will be updated first.
Service providers
Cloudflare provides hosting, database, object storage, DNS, public domain and network data, and security services. Local Playwright captures public page images before upload. Local Codex workflows assist with English editorial preparation and faithful translations. External destinations apply their own privacy policies.
External links and favicons
Profiles link to official sources and links found on a public page. Opening one sends your request to that external service. Small favicons can be requested from Google’s favicon service to help identify a destination; that request can disclose your IP address, browser information, and the requested favicon URL to Google. External editorial links use a nofollow relationship, while the primary “Visit website” link includes a Beta Directory source parameter.
Retention and security
Stored observations make pages fast, reduce repeated collection, provide historical context, and support corrections. Retention varies by record type and operational need. New refreshes generally create a newer observation rather than making an old timestamp appear current. Operational request logs are retained according to hosting and security needs.
Access to collection endpoints is authenticated, and secrets are not placed in public page data. No Internet service can promise absolute security. If we learn of a material incident affecting personal information, we will respond according to applicable obligations.
International processing and legal grounds
Cloud infrastructure can process data in more than one country. Depending on applicable law, processing is based on operating the requested service, legitimate interests in publishing and securing a public directory, consent where required, and compliance with legal obligations. Rights differ by location.
Your choices and rights
You may request access to, correction of, or removal of personal information appearing in a profile. You may also object to or request restriction of processing where applicable. Include the domain, exact field, your relationship to the information, country or region, and supporting evidence. We may need to verify identity and authority before changing a record.
Some information can be retained for security, legal obligations, exercising or defending claims, or documenting a resolved dispute. You may also have the right to complain to a local data-protection authority.
Children
Beta Directory is a general reference service and is not directed to children. We do not knowingly request account information from children. Contact us if you believe a child’s personal information appears in a record and should be reviewed.
Changes and contact
This notice will receive a new effective date when collection or processing changes materially. Privacy questions and requests can be sent to contact@beta.directory.
