Privacy policy
Effective October 4, 2026. Send reader, legal, or privacy enquiries to [email protected].
Who is responsible
The company identified below is responsible for this website and the personal data described here. For privacy questions, email [email protected] or write to the registered address shown.
Search and shared comparisons
County search runs in your browser against a dataset downloaded from this website. Text typed into the search field is processed locally. The comparison selectors and unit conversion also run in your browser. These tools do not create accounts, set cookies, or write to browser local storage.
Opening a URL with search or comparison parameters sends that URL to the website’s hosting infrastructure. Shared comparison URLs contain county GEOIDs and a unit; search links can contain a query. Those parameters may appear in infrastructure request logs. Do not include personal information in shared URLs. Optional analytics is disabled in this version. If enabled after a processing review, its configuration removes query parameters and fragments from visited URLs and from referring URLs before sending a page-view event.
Purposes and legal bases
We process the request information necessary to deliver pages and downloads and to protect the website from errors and abuse. The legal basis is our legitimate interest in operating a reliable, secure reference publication, under Article 6(1)(f) of the GDPR. Request information can include IP addresses, timestamps, requested URLs, and browser information.
We use limited page-view analytics to understand which articles and features readers use and to diagnose problems. This serves our legitimate interest in maintaining and improving the publication. The site does not use analytics for advertising profiles or automated decisions about individual readers. You may object to this processing by contacting us; the tracker also respects the browser’s Do Not Track setting.
If you email us, we process your address, message, and attachments to answer your enquiry or investigate a correction, based on our legitimate interest in reader support and editorial accuracy. Information needed to comply with a specific legal obligation is processed under Article 6(1)(c). Please avoid sending identity documents or other sensitive records.
Analytics data
The site uses Umami at stats.admk.com. Page-view events include the page path and title, the originating website for an external referral or the path for an internal referral, screen size, and language. The service can derive general browser, device, and country information from the request. It receives connection information needed to accept that request.
The tracker is restricted to the publication’s production domains. It does not set analytics cookies, receive search/comparison parameters or URL fragments through our page-view payloads, or receive the text typed into the county search field. We use the statistics to assess pages and features in aggregate. Browser blocking of the analytics script does not prevent access to county data.
Recipients and external services
Access to personal information is limited to the publisher and the service providers needed to host and secure the website, deliver and store correspondence, and operate the Umami installation. Such infrastructure and email providers may process request records or messages to provide their services. We may disclose information where a specific legal obligation requires it.
County outlines and datasets are served by this website. Following a Census, OpenStreetMap, Creative Commons, or other external link sends a request to that service, whose own privacy information applies. External maps are not embedded automatically.
Retention criteria
The retention criterion for request and security records is whether they remain necessary to diagnose a delivery problem, investigate an abuse or security incident, or meet an applicable legal requirement. Records should be deleted or anonymized when those purposes end; a resolved routine request does not justify indefinite retention.
Analytics records should be retained only while needed to evaluate the relevant publication period, compare the use of pages, or investigate a feature problem. Information that no longer serves those purposes should be deleted or reduced to aggregate statistics.
Correspondence should be retained while an enquiry or correction is open and for any further period needed to document the resulting editorial correction, resolve a dispute, or meet an applicable legal requirement. Unnecessary attachments should be removed.
These criteria apply to the publisher’s processing. Infrastructure providers can maintain separate security or legally required records. Contact us to request the retention and processing-location information applicable to your enquiry, or to ask that correspondence be deleted.
Your rights and requests
Where applicable, you may request access, correction, erasure, restriction, or portability of personal information, and object to processing based on legitimate interests. Contact [email protected] and describe the information or correspondence concerned. We may need enough information to identify the request, but you should not send identity documents unless needed and requested.
You may complain to the Spanish Data Protection Agency (AEPD) or another competent data protection authority. Providing an email address or a message is voluntary, though we need a reply address to respond. We do not use the website’s data to make automated decisions with legal or similarly significant effects.
Advertising
Advertising is disabled in this version of the publication, and no Google advertising scripts are loaded. Before enabling it, we must publish and verify the applicable consent messages and update the provider, retention, and international-transfer disclosures to match the actual configuration.
Changes
This policy is updated when the publication’s processing changes. The effective date identifies this version. Publisher information and correction and contact instructions are available separately.