An Indefinite Integral Evidence. Questions. Everything.
--:--:--

Data handling, source credits, privacy posture, and public-dataset obligations for Hedegreen Research.

Privacy posture

Hedegreen Research is built as a public working system, not a surveillance product. The site should not collect personal data just because it can.

  • No advertising tracker is intentionally installed as part of the public V2 site.
  • No user account system is part of the public site.
  • No newsletter signup or hidden intake funnel is part of the public site.
  • Some local tools may store state in the browser so the tool can work for the visitor. That state should stay local unless a tool explicitly says otherwise.
  • Normal hosting, browser, network, and third-party platform logs may still exist outside this site code. That is infrastructure reality, not an editorial claim of personal tracking.

Public data use

Hedegreen Research uses public datasets, official statistics, open geographic data, archived documents, public APIs, and public-safe manifests across articles, TID objects, preview apps, and data doors.

Data used here is not automatically a conclusion. It is material for testing, comparison, correction, and visible method. This page lists the recurring public data families currently exposed on public or preview surfaces. It is not a full bibliography of every single article source.

Current public data families

  • European language-access data: the public EU languages page, Eurobarometer 100.1 / ZA8778 through GESIS and the European Commission / European Parliament chain, Special Eurobarometer 540, and Eurostat population tables are used in the public 24 Doors language-access instrument and its source manifests.
  • Denmark politics and elections: Danmarks Statistik / Statistikbanken municipality and trend data, the official VALG public exports on data.valg.dk, and limited secondary public cross-checks such as Straubinger/folketingsvalg support the public Denmark politics surface.
  • Sweden politics and elections: Valmyndigheten municipality election exports and Statistics Sweden factor tables support the public Sweden politics surface.
  • Netherlands public preview: Kiesraad / data.overheid.nl Tweede Kamer municipality results and CBS StatLine municipality indicators support the public-preview Dutch politics surface.
  • Belgium public preview: the official Belgian election results API from IBZ and selected Statbel municipality indicators support the public-preview Belgium politics surface.
  • Maps, places, and geographic lookup: OpenStreetMap contributors, related map-tile providers such as CARTO, and public map-query layers such as Overpass are used where live map reads or place context are part of the public method. The standalone nearest-gravhøj tool also uses a local filtered extract from the official Danish Fund og Fortidsminder dataset from Slots- og Kulturstyrelsen / Kulturarv.
  • Eurovision and contest data: public Eurovision archive data via eurovisionapi.runasp.net, official eurovision.com scoreboards where the archive lags, and Eurovisionworld result / odds pages are used in the Eurovision public tools. The Other Scoreboard host-context layer also uses Open-Meteo Historical Weather API for a narrow weather context field.
  • Space-weather live feeds: the live Space Weather panel reads public NOAA SWPC JSON feeds for alerts, planetary Kp, solar-wind plasma, solar-wind magnetic field, and GOES X-ray readings. The current live panel uses NOAA, not NASA, as its upstream public signal.
  • External public API surfaces run beside Hedegreen Research: the public Windowsill TID door is a client of the separate Windowsill API. That surface belongs in this data map because it is public, but its detailed plant, climate, and source-hierarchy documentation lives with the API and its public repository rather than only inside this site repo.
  • Article-specific archives and documents: one-off government portals, official PDFs, public repositories, Zenodo records, scans, archived webpages, and manually checked source files may support individual articles or data rooms. Those should be credited on the page they support or in the linked source manifest, not hidden behind a generic claim that the data came from nowhere.

Credits and licenses

  • OpenStreetMap data, where used, should be credited as OpenStreetMap contributors and handled under the applicable OpenStreetMap license terms.
  • Danmarks Statistik data, where used, should be credited according to Danmarks Statistiks kildeangivelse.
  • Statistics Sweden, Valmyndigheten, Eurostat, GESIS, Statbel, CBS StatLine, Kiesraad, IBZ, NOAA SWPC, Eurovisionworld, and other public providers should be credited near the work they support and handled under their stated reuse terms.
  • Preview surfaces should keep their preview boundary visible. Public availability does not automatically mean the method is finished, the wording is mature, or the scope is broad enough for a larger claim.

Handling rule

The working rule is simple: if a public source materially helps make the work possible, the reader should be able to see that source path. If a tool stores, transforms, compares, or displays data, the public surface should not pretend the data came from nowhere.

The second rule is scope honesty: a preview dataset should stay a preview dataset, a bridge layer should stay a bridge layer, and a public API should not be mistaken for a proof machine.

Corrections

If a source credit, data description, privacy statement, surface label, or attribution is wrong or incomplete, it belongs in the corrections flow. The correction is part of the record, not a private embarrassment.